History for FrontPage

??changed:
-
The Zope Public CVS Repository

  Contact: KenManheimer

  **NB: Most Zope related development, specifically CMF, Zope 3, Zope 2 versions 
        higher than
        the Zope 2.7 development branch, is now hosted in Subversion.
        Information on this can be found at http://dev.zope.org/Subversion/.**

  Our public CVS repository (see http://cvs.zope.org for a web view)
  provides read-only and selective write access to the source code for
  Zope's and related projects - !StandaloneZODB, and so
  forth.  Public CVS access and co-development with the community 
  are critical to Zope's evolution. 

  See CVSResources for pointers to CVS background information, and
  ZopeCVSFAQ for instructions on key CVS operations for use with our
  repository.

  - ReadOnlyAccess describes how to to hookup with the CVS
    repository to track changes.

  - RepositoryProjects describes the projects in the repository,
    including information about their focus, managers, and
    checkin-notice distribution maillists so you can follow the
    checkins for the projects.

  - See RepositoryOrganization for details about the structure and
    contents of our repository.

  - http://cvs.zope.org presents a web interface by which you can
    browse the repository - visit there for instructions.

  - There are many ways to contribute - see <a
    href="http://dev.zope.org/Resources/GettingInvolved.html">
    !GettingInvolved (non-wiki)</a>.

  Zope Corp. developers and selected members of the community have
  write access to the repository.

  - The Zope repository is now being opened to checkins from the 
  community.  ContributorIntroduction gives background information 
  on the approach.  ContributorFAQ summarizes questions and answers. 
  Finally, the <a href="../Contributor.pdf">Zope Contributor Agreement</a> is 
  the legal agreement that gets signed and returned.

  - WriteAccess contains the policies and procedures for write-access
    to the CVS repository (and it contains CommitterGuidelines,
    required reading for anyone with write access).

  - ZopeDevelopmentProcess provides details about the who, what, when
    and where of changing the Zope code. This is more detailed than 
    the CommitterGuidelines, and talks about exactly where changes 
    should go for features and bug fixes, relation to releases, etc.

  - BugDays describes the "bug day" process we use to ensure that issues 
    are addressed.

  For those of us administering the process:

   - CVSKeyDepositAdminNotes - Instructions for setting up CVS-write users, etc

  For those interested in our CVS provisions like remote-administered symlinks
  and (symlink-respectful) emailled checkin notifications, see:

   - CVSAddons

  - RecentChanges in this wiki