Diff for /wikisrc/projects/project/cvs-migration.mdwn between versions 1.6 and 1.7

version 1.6, 2014/12/17 20:54:48 version 1.7, 2014/12/18 00:45:51
Line 10  category="misc" Line 10  category="misc"
 difficulty="hard"  difficulty="hard"
   
 description="""  description="""
   # Our decision matters
   
   You're reading this because you care about the future of NetBSD and
   you understand that good tools act as a force multiplier.
   
   # Our decision is not obvious
   
   If it were, we'd have made it already (and wouldn't be disagreeing
   so persistently about which one it needs to be ;-).
   
   # Our decision needs to be about the whole elephant
   
   We all understand the basics of using source control. This level
   of understanding is necessary but not sufficient to make an informed
   decision about whether to migrate any or all of NetBSD's repositories
   to another VCS, and if so which, or how.
   
   Our choice of VCS carries implications not only about how developers
   hack on NetBSD, but also about how non-developers contribute and
   become developers, and how Project sysadmins keep our valuable code
   secure. Therefore, any choice of VCS other than the default (sticking
   with CVS for a while longer) necessarily implies that as a group,
   we all need to learn how we're going to do what we expect to need
   to do. Not all of this learning needs to happen before we can make
   a reasonably confident decision for our Project. But if we want to
   arrive at consensus, much of it does.
   
   There is no available choice of VCS that entirely avoids tradeoffs
   for us. Therefore, to choose intelligently, we must first consider
   all the tradeoffs we can think of, then decide which ones we can
   live with and which we cannot.
   
   # Our decision needs to be made together
   
   We're a community. The only way a complicated, interconnected set
   of changes like this can be implemented is for us to arrive at rough
   consensus that some particular VCS:
   
   - is sufficiently well suited to our project's needs in theory,
   - is sufficiently easily adapted to our needs in practice,
   - has a sufficiently fail-safe migration plan,
   - is worth the effort to switch, and
   - has volunteers to do the work.
   
   # How you can help, right now
   
   What are some considerations you think are important? Are they
   listed here? If not, edit this page and add them.
   
   # Considerations
   
   # Humans
   
   ## People who administer Project resources
   
   ## People who can commit directly to NetBSD
   
   ## People who can't commit directly to NetBSD
   
   # Other
   
 NetBSD is one of the first projects to use internet-available source control.  NetBSD is one of the first projects to use internet-available source control.
 It has been using CVS since the very beginning of the project (over 21 years)  It has been using CVS since the very beginning of the project (over 21 years)
 and the repository is vast.  and the repository is vast.
Line 25  has shifted to new workflows. Line 86  has shifted to new workflows.
 The purpose of this project is to identify:  The purpose of this project is to identify:
   
  * existing 'workflows' in common use among developers   * existing 'workflows' in common use among developers
     * (example): [users/dholland/hgnb](/users/dholland/hgnb)      * (example): [[dholland/hgnb]]
  * existing 'tooling' within NetBSD the organization   * existing 'tooling' within NetBSD the organization
     * how much memory/disk is required to host NetBSD?      * how much memory/disk is required to host NetBSD?
     * how are backups performed?      * how are backups performed?

Removed from v.1.6  
changed lines
  Added in v.1.7


CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb