[Checkins] SVN: zf.zscp/trunk/src/zf/zscp/doc/ removed unsed files

Daniel Meier daniel.meier at perse.ch
Tue Apr 11 06:17:05 EDT 2006


Log message for revision 66846:
  removed unsed files
  

Changed:
  D   zf.zscp/trunk/src/zf/zscp/doc/packages_search.pt
  D   zf.zscp/trunk/src/zf/zscp/doc/packages_tips.pt
  D   zf.zscp/trunk/src/zf/zscp/doc/regulations_intro.pt
  D   zf.zscp/trunk/src/zf/zscp/doc/repository_intro.pt

-=-
Deleted: zf.zscp/trunk/src/zf/zscp/doc/packages_search.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/packages_search.pt	2006-04-11 10:14:09 UTC (rev 66845)
+++ zf.zscp/trunk/src/zf/zscp/doc/packages_search.pt	2006-04-11 10:17:04 UTC (rev 66846)
@@ -1,11 +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">Package Search</div>
-	  
-  </div>
-  </body>
-
-</html>
\ No newline at end of file

Deleted: zf.zscp/trunk/src/zf/zscp/doc/packages_tips.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/packages_tips.pt	2006-04-11 10:14:09 UTC (rev 66845)
+++ zf.zscp/trunk/src/zf/zscp/doc/packages_tips.pt	2006-04-11 10:17:04 UTC (rev 66846)
@@ -1,11 +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">Package Search Tips</div> 
-	  	  	  
-  </div>
-  </body>
-
-</html>
\ No newline at end of file

Deleted: zf.zscp/trunk/src/zf/zscp/doc/regulations_intro.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/regulations_intro.pt	2006-04-11 10:14:09 UTC (rev 66845)
+++ zf.zscp/trunk/src/zf/zscp/doc/regulations_intro.pt	2006-04-11 10:17:04 UTC (rev 66846)
@@ -1,34 +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 (1of 8) The Zope Software
-				Certification Program and the Common Repository</div>
-			<h3 class="itemOne itemHeading">Zope Community Process</h3>
-			<p>This section describes the process for Zope-related software to receive
-				quality certification.</p>
-			
-			<p>Historically, the Zope community had no development process. This was in
-				part because the development of Zope 2 was controlled by Digital Creations
-				(now Zope Corporation) and testing-automation tools were not available at
-				that time. Also, Zope 2 lacked the necessary documentation. All this lead to
-				an accepted misuse of the API and often low quality software.</p>
-			<p>With the advent of Zope 3, procedures were set in place to ensure the quality
-				and documentation of the code. Guided by eXtreme Programming practices,
-				sprints were organized to educate the Zope community about the project and
-				have high-productivity development time, proposals were introduced to
-				ensure the proper discussion of a feature before implementation, and tests
-				were required to ensure the overall quality of the code base. This
-				development process is called the Zope Community Process.</p>
-			<p>While the Zope Community Process provides an excellent method for
-				developing community-driven projects like Zope 3, it (a) does not show how
-				to produce simple high-quality packages, (b) measure the quality, and (c)
-				communicate the state of a package to outsiders. The goal of the Zope
-				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>
-	</body>
-</html>
\ No newline at end of file

Deleted: zf.zscp/trunk/src/zf/zscp/doc/repository_intro.pt
===================================================================
--- zf.zscp/trunk/src/zf/zscp/doc/repository_intro.pt	2006-04-11 10:14:09 UTC (rev 66845)
+++ zf.zscp/trunk/src/zf/zscp/doc/repository_intro.pt	2006-04-11 10:17:04 UTC (rev 66846)
@@ -1,35 +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 (1 of 8)</div>
-		<p>This section describes <em>one</em> open community-repository that
-			implements the ZSCP process.</p>
-		<h3 class="itemOne itemHeading">Definition</h3>
-		<p>The Common Repository is a Zope Foundation SVN repository for third-party Zope
-			packages, which are useful for a wide variety of applications, but that do not fit
-			into the Zope core distribution. Common examples for those packages include
-			advanced Javascript-based widgets, alternative templating systems,
-			specific content types, etc.</p>
-		<p>The existing <tt class="docutils literal">
-			<span class="pre">svn://svn.zope.org/repos/main</span></tt> will serve
-			as the Common Repository. Every package in the common repository <em>must</em>
-			conform at least to the layout as described in section 3.2. If a package wishes to
-			participate in the ZSCP, then it must also conform to the program's process. The
-			implementation details of the ZSCP process are provided in the sections
-			below.</p>
-		<p>The Common Repository is only <em>one</em> implementation of the ZSCP. While the
-			Common Repository implements the ZSCP guidelines and suggested automation
-			tools, the ZSCP process itself does <em>not</em> require the Common
-			Repository.</p>
-		<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>
-		
-		<a href="@@repository_page02.html">Next Page: Layout</a>
-		
-	</div>
-  </body>
-
-</html>
\ No newline at end of file



More information about the Checkins mailing list