-rw-r--r-- | docs/src/opie-policy/core/core.sgml | 39 |
1 files changed, 39 insertions, 0 deletions
diff --git a/docs/src/opie-policy/core/core.sgml b/docs/src/opie-policy/core/core.sgml index 9db4de1..edd1075 100644 --- a/docs/src/opie-policy/core/core.sgml +++ b/docs/src/opie-policy/core/core.sgml @@ -1,30 +1,69 @@ <chapter id="core"> <title>Core Opie Policies</title> <sect1 id="imagepolicy"><title>Image Policy</title> <para> This section outlines policies with regard to images in Opie. Specifically, concerns regarding the structure of the pics/ subdirectory are addressed. <itemizedlist><title>Primary Declarations</title> <listitem> <para> All generally <emphasis>useful</emphasis> images are to be inlined. </para> </listitem> <listitem> <para> All images which are used by more than one Opie core application are to be inlined. </para> </listitem> <listitem> <para> All images specific to one core application are to be moved into a pics/ subdirectory of the application's directory, and are to be packaged with the application. </para> </listitem> <listitem> <para> All other images are to be kept for compatibility reasons and are to be packaged in a opie-extrapics package. The opie-pics package will no longer exist, and no images will reside in the root of pics/. </para> </listitem> </itemizedlist> </para> </sect1> + <sect1 id="librarypolicy"><title>Qtopia Compatibility</title> + <para> + This section outlines the stance of Opie with regard to compatibility with Qtopia. Testing must be done on a regular basis to ensure that this is still the case. Our applications must work in a Qtopia environment, and vice versa. + <itemizedlist><title>Primary Declarations</title> + <listitem> + <para> + Binary compatibility is to be retained with Qtopia, in both directions. + </para> + </listitem> + <listitem> + <para> + The libqpe library is not to be altered in such a way that compatibility is broken. + </para> + </listitem> + <listitem> + <para> + Functions may be added to the library, as long as that does not affect compatibility, and as long as said functions are used ONLY internally. + </para> + </listitem> + <listitem> + <para> + Existing functions are not to be altered in an unexpected way. + </para> + </listitem> + </itemizedlist> + </para> + </sect1> + <sect1 id="corevsnoncore"><title>Core/NonCore</title> + <para> + This section outlines policies and guidelines with regard to the core/noncore seperation. + <itemizedlist><title>Primary Declarations</title> + <listitem> + <para> + NULL + </para> + </listitem> + </itemizedlist> + </para> + </sect1> </chapter> |