[Checkins] SVN: zf.zscp/trunk/src/zf/zscp/doc/ added some references
Daniel Meier
daniel.meier at perse.ch
Tue Apr 11 06:13:27 EDT 2006
Log message for revision 66844:
added some references
Changed:
U zf.zscp/trunk/src/zf/zscp/doc/benefits.pt
U zf.zscp/trunk/src/zf/zscp/doc/configure.zcml
U zf.zscp/trunk/src/zf/zscp/doc/regulations.pt
U zf.zscp/trunk/src/zf/zscp/doc/regulations_page02.pt
U zf.zscp/trunk/src/zf/zscp/doc/regulations_page03.pt
U zf.zscp/trunk/src/zf/zscp/doc/regulations_page04.pt
U zf.zscp/trunk/src/zf/zscp/doc/regulations_page05.pt
U zf.zscp/trunk/src/zf/zscp/doc/regulations_page06.pt
U zf.zscp/trunk/src/zf/zscp/doc/regulations_page07.pt
U zf.zscp/trunk/src/zf/zscp/doc/regulations_page08.pt
A zf.zscp/trunk/src/zf/zscp/doc/regulations_page09.pt
D zf.zscp/trunk/src/zf/zscp/doc/regulations_qa.pt
U zf.zscp/trunk/src/zf/zscp/doc/repository.pt
U zf.zscp/trunk/src/zf/zscp/doc/repository_page02.pt
U zf.zscp/trunk/src/zf/zscp/doc/repository_page03.pt
U zf.zscp/trunk/src/zf/zscp/doc/repository_page04.pt
U zf.zscp/trunk/src/zf/zscp/doc/repository_page05.pt
U zf.zscp/trunk/src/zf/zscp/doc/repository_page06.pt
U zf.zscp/trunk/src/zf/zscp/doc/repository_page07.pt
U zf.zscp/trunk/src/zf/zscp/doc/repository_page08.pt
A zf.zscp/trunk/src/zf/zscp/doc/repository_page09.pt
D zf.zscp/trunk/src/zf/zscp/doc/repository_qa.pt
-=-
Modified: zf.zscp/trunk/src/zf/zscp/doc/benefits.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/benefits.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/benefits.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -20,7 +20,7 @@
of packages in the core. However, this process does not extend to third party
code, let alone code outside of the zope.org repository. On the other hand,
Plone also uses the collective for core packages without any control over
- the process or quality. This proposal will define a process for ensuring the
+ the process or quality. This proposal will define a <a href="@@regulations.html">process</a> for ensuring the
quality of packages and for upstream movement: in other words, the way a
third-party package could become a core package.</p>
<h3 class="itemTwo itemHeading">Repository Unification</h3>
@@ -29,14 +29,14 @@
are hard to make; the overhead is large. If one finds something wrong with the
code, one either has to write a mail or create a bug report. And that often
requires one to sign up to yet another mailing list or create a user account
- for yet another web site. Thus, this proposal suggests a common repository
- for all generically useful Zope 3 add-on packages.</p>
+ for yet another web site. Thus, this proposal suggests a <a href="@@repository.html">
+ common repository</a> for all generically useful Zope 3 add-on packages.</p>
<h3 class="itemThree itemHeading">Quality Packages</h3>
<p>There is a natural desire for any developer to know what they are getting into
when they are using a certain package, a baseline of quality that can be
expected. While the Zope 3 community has some ideas of what that baseline is
for the core, it is not well defined and applied uniformly. This proposal
- defines clear quality guidelines.</p>
+ defines <a href="@@regulations_page04.html">clear quality guidelines</a>.</p>
<h3 class="itemFour itemHeading">Clear Dependency Declarations</h3>
<p>One of the greatest frustrations in the Zope community, especially in Plone,
is the complex non-closed tree of dependencies of packages. While this
@@ -47,7 +47,7 @@
<p>The Zope community at large uses mainly two licenses, the ZPL and the GPL.
(Yes, other licenses are also used.) Dealing with multiple licenses is a
pain, especially for Zope's consumers. This proposal discusses the
- current situation and proposes a resolution.</p>
+ current situation and proposes a <a href="@@repository_page07.html">resolution</a>.</p>
<h3 class="itemSix itemHeading">Marketing Effect</h3>
<p>People commonly say, Zope does anti-marketing. And that is probably true.
While a proposal like that cannot address this issue globally, it can at
Modified: zf.zscp/trunk/src/zf/zscp/doc/configure.zcml
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/configure.zcml 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/configure.zcml 2006-04-11 10:13:25 UTC (rev 66844)
@@ -125,9 +125,9 @@
<browser:page
for="*"
- name="regulations_qa.html"
+ name="regulations_page09.html"
permission="zope.Public"
- template="regulations_qa.pt"
+ template="regulations_page09.pt"
layer="zf.zscp.skin.IZSCPLayer"
/>
@@ -197,9 +197,9 @@
<browser:page
for="*"
- name="repository_qa.html"
+ name="repository_page09.html"
permission="zope.Public"
- template="repository_qa.pt"
+ template="repository_page09.pt"
layer="zf.zscp.skin.IZSCPLayer"
/>
Modified: zf.zscp/trunk/src/zf/zscp/doc/regulations.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -1,9 +1,15 @@
<html metal:use-macro="context/@@standard_macros/view" i18n:domain="zf.zscp">
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
-
- <div id="documentFirstHeading">Regulations (1of 8) The Zope Software
- Certification Program and the Common Repository</div>
+
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (1 of 9)
+ <!--
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations_page02.html"></a></b>
+ -->
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page02.html"></a></b>
+ </div>
+
<h3 class="itemOne itemHeading">Zope Community Process</h3>
<p>This section describes the process for Zope-related software to receive
quality certification.</p>
@@ -27,8 +33,9 @@
Software Certification Program (ZSCP) is (a) to clearly define the levels
of software quality using a metric system and (b) to communicate this
information to our users, customers, and prospective customers.</p>
- <a href="@@regulations_page02.html">Next Page: ...</a>
+ <div class="itemNavRightArrow"><a href="@@regulations_page02.html">Next Page: Audience</a></div>
+
</div>
</body>
</html>
\ No newline at end of file
Modified: zf.zscp/trunk/src/zf/zscp/doc/regulations_page02.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_page02.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_page02.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -2,7 +2,12 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Regulations (2 of 8)</div>
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (2 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page03.html"></a></b>
+ </div>
+
<h3 class="itemTwo itemHeading">Audience</h3>
<p>The audience for the Zope Software Certification Program (ZSCP) is
@@ -35,8 +40,10 @@
guidelines of what to expect of his/her developers in terms of software
quality. Again, the support of the Zope Foundation is reassuring to him that
the program is legitimate.</p>
- <a href="@@regulations_page03.html">Next Page: ...</a>
+ <div class="itemNavLeftArrow"><a href="@@regulations.html">Previous Page: Zope Community Process</a></div>
+ <div class="itemNavRightArrow"><a href="@@regulations_page03.html">Next Page: Certification Levels</a></div>
+
</div>
</body>
</html>
\ No newline at end of file
Modified: zf.zscp/trunk/src/zf/zscp/doc/regulations_page03.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_page03.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_page03.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -2,7 +2,12 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Regulations (3 of 8)</div>
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (3 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations_page02.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page04.html"></a></b>
+ </div>
+
<h3 class="itemThree itemHeading">Certification Levels</h3>
<h4><a id="certification-levels" name="certification-levels">2.3.
@@ -79,7 +84,9 @@
Certified" in informal or promotional material.</p>
</li>
</ul>
- <a href="@@regulations_page04.html">Next Page: ...</a>
+
+ <div class="itemNavLeftArrow"><a href="@@regulations_page02.html">Previous Page: Audience</a></div>
+ <div class="itemNavRightArrow"><a href="@@regulations_page04.html">Next Page: Quality Metrics</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/regulations_page04.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_page04.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_page04.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -2,7 +2,12 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Regulations (4 of 8)</div>
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (4 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations_page03.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page05.html"></a></b>
+ </div>
+
<h3 class="itemFour itemHeading">Quality Metrics</h3>
<p>The certification is meaningless without the precise definition of tasks
that have to be accomplished for each certification level. This section
@@ -496,8 +501,10 @@
<p>In addition to the fulfillment of the requirements listed in 2.4.24, the data
migration scripts <em>must</em> be tested against production-grade data
of at least 2 projects using the package.</p>
- <a href="@@regulations_page05.html">Next Page: ...</a>
-
+
+ <div class="itemNavLeftArrow"><a href="@@regulations_page03.html">Previous Page: Certification Levels</a></div>
+ <div class="itemNavRightArrow"><a href="@@regulations_page05.html">Next Page: Package Meta-Information</a></div>
+
</div>
</body>
</html>
\ No newline at end of file
Modified: zf.zscp/trunk/src/zf/zscp/doc/regulations_page05.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_page05.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_page05.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -2,7 +2,12 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Regulations (5 of 8)</div>
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (5 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations_page04.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page06.html"></a></b>
+ </div>
+
<h3 class="itemFive itemHeading">Package Meta-Information</h3>
<p>In order to quickly provide a developer with contextual information about a
given package, it is necessary to clearly define the meta-data that
@@ -155,7 +160,9 @@
<p>(Text Line, single, required)</p>
<p>This is the version number of this package meta-data.</p>
<p>Example: 1.1</p>
- <a href="@@regulations_page06.html">Next Page: ...</a>
+
+ <div class="itemNavLeftArrow"><a href="@@regulations_page04.html">Previous Page: Quality Metrics</a></div>
+ <div class="itemNavRightArrow"><a href="@@regulations_page06.html">Next Page: Package Certification Data</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/regulations_page06.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_page06.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_page06.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -3,7 +3,12 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Regulations (6 of 8)</div>
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (6 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations_page05.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page07.html"></a></b>
+ </div>
+
<h3 class="itemSix itemHeading">Package Certification
Data</h3>
@@ -72,8 +77,10 @@
certification to be granted.</dd>
</dl>
</div>
- <a href="@@regulations_page07.html">Next Page: ...</a>
-
+
+ <div class="itemNavLeftArrow"><a href="@@regulations_page05.html">Previous Page: Package Meta-Information</a></div>
+ <div class="itemNavRightArrow"><a href="@@regulations_page07.html">Next Page: Package Release Data</a></div>
+
</div>
</body>
</html>
\ No newline at end of file
Modified: zf.zscp/trunk/src/zf/zscp/doc/regulations_page07.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_page07.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_page07.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -3,7 +3,12 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Regulations (7 of 8)</div>
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (7 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations_page06.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page08.html"></a></b>
+ </div>
+
<h3 class="itemSeven itemHeading">Package Release Data</h3>
<p>Finally, all the releases of certified packages <em>must</em> be tracked.
This section describes the data that must be recorded for each release. The
@@ -99,7 +104,8 @@
></p>
</div>
- <a href="@@regulations_page08.html">Next Page: ...</a>
+ <div class="itemNavLeftArrow"><a href="@@regulations_page06.html">Previous Page: Package Certification Data</a></div>
+ <div class="itemNavRightArrow"><a href="@@regulations_page08.html">Next Page: The Process</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/regulations_page08.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_page08.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_page08.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -3,8 +3,12 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Regulations (8 of 8)</div>
-
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (8 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations_page07.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page09.html"></a></b>
+ </div>
+
<h3 class="itemEight itemHeading">The Process</h3>
<p>The main purpose of this section is to define the workflow that a package
@@ -68,6 +72,10 @@
them with ways to measure it. The certification is a way of saying
"thank you". And for the community it is overall better to have as
many certified packages as possible.</p>
- </div>
+
+ <div class="itemNavLeftArrow"><a href="@@regulations_page07.html">Previous Page: Package Release Data</a></div>
+ <div class="itemNavRightArrow"><a href="@@regulations_page09.html">Next Page: Questions and Answers</a></div>
+
+ </div>
</body>
</html>
\ No newline at end of file
Added: zf.zscp/trunk/src/zf/zscp/doc/regulations_page09.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_page09.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_page09.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -0,0 +1,74 @@
+<html metal:use-macro="context/@@standard_macros/view"
+ i18n:domain="zf.zscp">
+ <body>
+ <div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
+
+ <div id="documentFirstHeading">Regulations for the Zope Software
+ Certification Program (9 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@regulations_page08.html"></a></b>
+ <!--
+ <b class="itemNavRightArrow" align="right" ><a href="@@regulations_page09.html"></a></b>
+ -->
+ </div>
+
+ <h3 class="itemNine itemHeading">Questions and Answers</h3>
+ <p>Does this proposal imply that all certified packages <em>must</em> live in the
+ Common Repository?</p>
+ <p>No, absolutely not! The ZSCP is completely disconnected from the Common
+ Repository. The common repsoitory is merely a place where it will be easy for
+ packages to undergo certification, since it will provide the necessary tools to
+ automatically check for the fullfillment of the requirements.</p>
+ <p>Why would you want your package in the Common Repository?</p>
+ <p>Placing your package in the Common Repository (like the collective in other
+ communities) will ensure a certain exposure of the code to others. If your
+ package will be certified, then other people will dedicate time to keep up the
+ compatibility and quality of the package. Further, you can use the
+ certification as a way to market your software and your skills. It is also
+ <em>your</em> personal way you can contribute back to the community.</p>
+ <p>Is the proposal too formal? Is the entry bar too high?</p>
+ <p>Some people might argue that the process is too formal and that the demotion clause
+ for certified packages will cause no packages being certified. I do not think
+ that will be the case. There will always be a set of packages that many people will
+ rely on (such as RDB adapters, LDAP adapter, authentication plugins) and where
+ the community has a vested interest in maintaining them. Also, I think there is a
+ general desire in the wider Zope community to have quality packages; this
+ proposal provides a roadmap for developers to produce those high-quality
+ packages.</p>
+ <p>How does this fit into the Cubed effort?</p>
+ <p>First a definition of "Cubed": Cubed is an effort by the Plone
+ developers to develop generic Zope 3 components that are primarily applicable
+ to Plone (integrated via Five for now), but are also usable by a wider audience.
+ The ultimate goal is to eventually provide a migration path of Plone from the Zope
+ 2 to the Zope 3 platform.</p>
+
+ <p>Will the Zope Foundation and/or the Zope core developers have the bandwidth to
+ process certification requests in a timely manner?</p>
+ <p>One big goal of the quality metrics section is to identify a set of quantifiable
+ items that can be easily verified using an automated process. Thus the overhead
+ for the core developers should be minimized. Also, an efficient Web site for the
+ process should allow certification managers to quickly provide the
+ certification. Overall, certifying a package should become as common of a task
+ as making releases or even writing documentation.</p>
+ <p>For such a process it seems to be useful to have an issue tracker, special mailing
+ lists and/or an advanced buildbot setup. Why are those technologies not
+ addressed in the proposal?</p>
+ <p>This proposal is <em>not</em> about technical solutions. It is about defining a
+ process and laying the implementation of this process via a community
+ repository. The purpose of the proposal is to establish an initial set of
+ guidelines/rules and not to discuss the technical implementation.</p>
+ <p>Why are dependencies not addressed in more detail?</p>
+ <p>Currently, we simply do not have any system in place that could sensibly handle
+ version requirements. However, several systems are currently being built. The
+ goal of this proposal is not to invent yet another version dependency system.
+ Thus the issue is deferred until the Zope community decides on a system to
+ use.</p>
+ <p>Are we going to certify core packages that are also seperate projects?</p>
+ <p>Yes, I imagine that it will be generally easier to certify those packages. Also,
+ having them certified separately makes it easier to amrket their
+ certification.</p>
+
+ <div class="itemNavRightArrow"><a href="@@regulations_page08.html">Previous Page: The Process</a></div>
+
+ </div>
+ </body>
+</html>
\ No newline at end of file
Property changes on: zf.zscp/trunk/src/zf/zscp/doc/regulations_page09.pt
___________________________________________________________________
Name: svn:keywords
+ Id
Name: svn:eol-style
+ native
Deleted: zf.zscp/trunk/src/zf/zscp/doc/regulations_qa.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_qa.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_qa.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -1,65 +0,0 @@
-<html metal:use-macro="context/@@standard_macros/view"
- i18n:domain="zf.zscp">
- <body>
- <div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
-
- <div id="documentFirstHeading">Regulations: Questions and Answers</div>
- <p>Does this proposal imply that all certified packages <em>must</em> live in the
- Common Repository?</p>
- <p>No, absolutely not! The ZSCP is completely disconnected from the Common
- Repository. The common repsoitory is merely a place where it will be easy for
- packages to undergo certification, since it will provide the necessary tools to
- automatically check for the fullfillment of the requirements.</p>
- <p>Why would you want your package in the Common Repository?</p>
- <p>Placing your package in the Common Repository (like the collective in other
- communities) will ensure a certain exposure of the code to others. If your
- package will be certified, then other people will dedicate time to keep up the
- compatibility and quality of the package. Further, you can use the
- certification as a way to market your software and your skills. It is also
- <em>your</em> personal way you can contribute back to the community.</p>
- <p>Is the proposal too formal? Is the entry bar too high?</p>
- <p>Some people might argue that the process is too formal and that the demotion clause
- for certified packages will cause no packages being certified. I do not think
- that will be the case. There will always be a set of packages that many people will
- rely on (such as RDB adapters, LDAP adapter, authentication plugins) and where
- the community has a vested interest in maintaining them. Also, I think there is a
- general desire in the wider Zope community to have quality packages; this
- proposal provides a roadmap for developers to produce those high-quality
- packages.</p>
- <p>How does this fit into the Cubed effort?</p>
- <p>First a definition of "Cubed": Cubed is an effort by the Plone
- developers to develop generic Zope 3 components that are primarily applicable
- to Plone (integrated via Five for now), but are also usable by a wider audience.
- The ultimate goal is to eventually provide a migration path of Plone from the Zope
- 2 to the Zope 3 platform.</p>
-
- <p>Will the Zope Foundation and/or the Zope core developers have the bandwidth to
- process certification requests in a timely manner?</p>
- <p>One big goal of the quality metrics section is to identify a set of quantifiable
- items that can be easily verified using an automated process. Thus the overhead
- for the core developers should be minimized. Also, an efficient Web site for the
- process should allow certification managers to quickly provide the
- certification. Overall, certifying a package should become as common of a task
- as making releases or even writing documentation.</p>
- <p>For such a process it seems to be useful to have an issue tracker, special mailing
- lists and/or an advanced buildbot setup. Why are those technologies not
- addressed in the proposal?</p>
- <p>This proposal is <em>not</em> about technical solutions. It is about defining a
- process and laying the implementation of this process via a community
- repository. The purpose of the proposal is to establish an initial set of
- guidelines/rules and not to discuss the technical implementation.</p>
- <p>Why are dependencies not addressed in more detail?</p>
- <p>Currently, we simply do not have any system in place that could sensibly handle
- version requirements. However, several systems are currently being built. The
- goal of this proposal is not to invent yet another version dependency system.
- Thus the issue is deferred until the Zope community decides on a system to
- use.</p>
- <p>Are we going to certify core packages that are also seperate projects?</p>
- <p>Yes, I imagine that it will be generally easier to certify those packages. Also,
- having them certified separately makes it easier to amrket their
- certification.</p>
-
- </div>
- </body>
-
-</html>
\ No newline at end of file
Modified: zf.zscp/trunk/src/zf/zscp/doc/repository.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -2,8 +2,14 @@
i18n:domain="zf.zscp">
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
-
- <div id="documentFirstHeading">Layout of the Common Repository (1 of 8)</div>
+
+ <div id="documentFirstHeading">The Common Repository Layout (1 of 9)
+ <!--
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository_page02.html"></a></b>
+ -->
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page02.html"></a></b>
+ </div>
+
<p>This section describes <em>one</em> open community-repository that
implements the ZSCP process.</p>
<h3 class="itemOne itemHeading">Definition</h3>
@@ -26,9 +32,9 @@
<p>Unless otherwise stated, certified packages will automatically be released
with every new Zope release. This, on the other hand, will greatly simplify the
dependency tree for Common Repository based packages.</p>
+
+ <div class="itemNavRightArrow"><a href="@@repository_page02.html">Next Page: Layout</a></div>
- <a href="@@repository_page02.html">Next Page: Layout</a>
-
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/repository_page02.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_page02.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_page02.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -3,8 +3,11 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
+ <div id="documentFirstHeading">The Common Repository Layout (2 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page03.html"></a></b>
+ </div>
- <div id="documentFirstHeading">Layout of the Common Repository (2 of 8)</div>
<h3 class="itemTwo itemHeading">Layout</h3>
<p>Packages in the Common Repository <em>must</em> have the following
@@ -114,8 +117,9 @@
have a license that can be changed by the Zope Foundation and developers have
signed contributor agreements, packages can be easily moved into the Zope 3
and Python core.</p>
-
- <a href="@@repository_page03.html">Next Page: ...</a>
+
+ <div class="itemNavLeftArrow"><a href="@@repository.html">Previous Page: Definition</a></div>
+ <div class="itemNavRightArrow"><a href="@@repository_page03.html">Next Page: Package Publication, Certification, and Release Data</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/repository_page03.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_page03.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_page03.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -2,8 +2,11 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Layout of the Common Repository (3 of
- 8)</div>
+ <div id="documentFirstHeading">The Common Repository Layout (3 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository_page02.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page04.html"></a></b>
+ </div>
+
<h3 class="itemThree itemHeading">Package Publication,
Certification, and Release Data</h3>
@@ -111,7 +114,9 @@
...
</releases>
</pre>
- <a href="@@repository_page04.html">Next Page: ...</a>
+
+ <div class="itemNavLeftArrow"><a href="@@repository_page02.html">Previous Page: Layout</a></div>
+ <div class="itemNavRightArrow"><a href="@@repository_page04.html">Next Page: Quality Assurance</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/repository_page04.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_page04.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_page04.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -2,8 +2,11 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Layout of the Common Repository (4 of
- 8)</div>
+ <div id="documentFirstHeading">The Common Repository Layout (4 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository_page03.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page05.html"></a></b>
+ </div>
+
<h3 class="itemFour itemHeading">Quality Assurance</h3>
<p>The goal of the Common Repository and its supporting software stack is to
@@ -122,7 +125,9 @@
simply needs to be documented.</p>
<p>Status: - The documentation to writing those type of tests needs to be
written.</p>
- <a href="@@repository_page05.html">Next Page: ...</a>
+
+ <div class="itemNavLeftArrow"><a href="@@repository_page03.html">Previous Page: Package Publication, Certification, and Release Data</a></div>
+ <div class="itemNavRightArrow"><a href="@@repository_page05.html">Next Page: Coding Style Guidelines</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/repository_page05.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_page05.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_page05.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -2,8 +2,11 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Layout of the Common Repository (5 of
- 8)</div>
+ <div id="documentFirstHeading">The Common Repository Layout (5 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository_page04.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page06.html"></a></b>
+ </div>
+
<h3 class="itemFive itemHeading">Coding Style Guidelines</h3>
<p>In general the Zope 3 coding style guidelines apply.</p>
<blockquote> <a class="reference"
@@ -65,7 +68,9 @@
dependencies must be listed as a Python path. There is one
dependency per line.</p>
</li>
- </ul> <a href="@@repository_page06.html">Next Page: ...</a>
+
+ <div class="itemNavLeftArrow"><a href="@@repository_page04.html">Previous Page: Quality Assurance</a></div>
+ <div class="itemNavRightArrow"><a href="@@repository_page06.html">Next Page: Releases</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/repository_page06.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_page06.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_page06.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -3,8 +3,11 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Layout of the Common Repository (6 of
- 8)</div>
+ <div id="documentFirstHeading">The Common Repository Layout (6 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository_page05.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page07.html"></a></b>
+ </div>
+
<h3 class="itemSix itemHeading">Releases</h3>
<p>By default, packages in the Common Repository will adopt the same release
schedule as Zope. The Zope development team releases two major releases a
@@ -15,7 +18,9 @@
libraries and programs at the same time.</p>
<p>However, packages may also choose their own release schedule. In this case
dependencies must be carefully stated in the release data file.</p>
- <a href="@@repository_page07.html">Next Page: ...</a>
+
+ <div class="itemNavLeftArrow"><a href="@@repository_page05.html">Previous Page: Coding Style Guidelines</a></div>
+ <div class="itemNavRightArrow"><a href="@@repository_page07.html">Next Page: License</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/repository_page07.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_page07.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_page07.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -3,8 +3,11 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Layout of the
- Common Repository (7 of 8)</div>
+ <div id="documentFirstHeading">The Common Repository Layout (7 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository_page06.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page08.html"></a></b>
+ </div>
+
<h3 class="itemSeven itemHeading">License</h3>
<p>The license of the repository is probably the most sensitive issue. The Plone
community has stated several times the need to protect their core values
@@ -32,7 +35,8 @@
very demanding at first sight, it is simply a necessary measure to protect
the Zope community legally.</p>
- <a href="@@repository_page08.html">Next Page: ...</a>
+ <div class="itemNavLeftArrow"><a href="@@repository_page06.html">Previous Page: Releases</a></div>
+ <div class="itemNavRightArrow"><a href="@@repository_page08.html">Next Page: An Example</a></div>
</div>
</body>
Modified: zf.zscp/trunk/src/zf/zscp/doc/repository_page08.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_page08.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_page08.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -3,8 +3,10 @@
<body>
<div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
- <div id="documentFirstHeading">Layout of the
- Common Repository (8 of 8)</div>
+ <div id="documentFirstHeading">The Common Repository Layout (8 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository_page07.html"></a></b>
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page09.html"></a></b>
+ </div>
<h3 class="itemEight itemHeading">An Example</h3>
<p>(informal voice)</p>
@@ -34,7 +36,10 @@
it, the package will receive the Level 3 certification. While this process
may take a year or longer to complete, it ensures that the API of the search
package is truly useful and provides benefit to the intended audience.</p>
-
+
+ <div class="itemNavLeftArrow"><a href="@@repository_page07.html">Previous Page: License</a></div>
+ <div class="itemNavRightArrow"><a href="@@repository_page09.html">Next Page: Questions and Answers</a></div>
+
</div>
</body>
</html>
\ No newline at end of file
Added: zf.zscp/trunk/src/zf/zscp/doc/repository_page09.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_page09.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_page09.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -0,0 +1,27 @@
+<html metal:use-macro="context/@@standard_macros/view"
+ i18n:domain="zf.zscp">
+ <body>
+ <div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
+
+ <div id="documentFirstHeading">The Common Repository Layout (9 of 9)
+ <b class="itemNavLeftArrow" align="right" ><a href="@@repository_page08.html"></a></b>
+ <!--
+ <b class="itemNavRightArrow" align="right" ><a href="@@repository_page09.html"></a></b>
+ -->
+ </div>
+
+ <h3>Questions and Answers</h3>
+ <p>Will the repository present a full-functioning application, like a
+ CMS?</p>
+ <p>No, the purpose of the repository is to be a <em>collection of
+ components</em> that is useful for a wider variety of applications.
+ Applications should be developed, maintained and governed outside this
+ repository. For example, Plone is developed by the Plone Foundation on
+ plone.org and the Tiks CMS by Projekt01 on tiks.org. However, those
+ applications may apply for certification.</p>
+
+ <div class="itemNavLeftArrow"><a href="@@repository_page08.html">Previous Page: An Example</a></div>
+
+ </div>
+ </body>
+</html>
\ No newline at end of file
Property changes on: zf.zscp/trunk/src/zf/zscp/doc/repository_page09.pt
___________________________________________________________________
Name: svn:keywords
+ Id
Name: svn:eol-style
+ native
Deleted: zf.zscp/trunk/src/zf/zscp/doc/repository_qa.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_qa.pt 2006-04-11 10:04:19 UTC (rev 66843)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_qa.pt 2006-04-11 10:13:25 UTC (rev 66844)
@@ -1,20 +0,0 @@
-<html metal:use-macro="context/@@standard_macros/view"
- i18n:domain="zf.zscp">
- <body>
- <div metal:fill-slot="body" tal:define="global pageversion string: 0.8">
-
- <div id="documentFirstHeading">Layout of the Common Repository: FAQ</div>
-
- <h3>Questions and Answers</h3>
- <p>Will the repository present a full-functioning application, like a
- CMS?</p>
- <p>No, the purpose of the repository is to be a <em>collection of
- components</em> that is useful for a wider variety of applications.
- Applications should be developed, maintained and governed outside this
- repository. For example, Plone is developed by the Plone Foundation on
- plone.org and the Tiks CMS by Projekt01 on tiks.org. However, those
- applications may apply for certification.</p>
-
- </div>
- </body>
-</html>
\ No newline at end of file
More information about the Checkins
mailing list