Annotation of wikisrc/projects/project/cvs-migration.mdwn, revision 1.15
1.1 mspo 1: [[!template id=project
3: title="CVS Migration for NetBSD repos"
1.8 wiki 13:
1.15 ! schmonz 14: ### Background and description
1.8 wiki 16: NetBSD is one of the first projects to use internet-available source control.
17: It has been using CVS since the very beginning of the project (over 21 years)
18: and the repository is vast.
20: NetBSD also hosts the pkgsrc repository which has many small files, many
21: "imports" and other technical challenges associated with VCS.
23: NetBSD also has various small internal repositories (like this wiki).
1.9 wiki 25: During the last twenty years tooling has improved and popular developer culture
1.8 wiki 26: has shifted to new workflows.
28: The purpose of this project is to identify:
30: * existing 'workflows' in common use among developers
31: * (example): [[dholland/hgnb]]
32: * existing 'tooling' within NetBSD the organization
33: * how much memory/disk is required to host NetBSD?
34: * how are backups performed?
35: * can the tools be cross-build?
36: * security requirements like
37: * how do we validate commits?
38: * how do we ensure commits originated from developers?
39: * release engineering requirements such as
40: * how does a pullup request work?
41: * how do we ensure the correct files are included in the correct release branches?
42: * how do we checkout a release branch
43: * how do we look at the history of a release branch
44: * how do we get different revisions of a file on a branch
46: major parts of the technical work like "how to convert FROM CVS to git/hg/fossil"
47: has already been done, which is why we are able to now ask "how would the project
48: continue to function?"
50: ### Our decision matters
1.7 schmonz 51:
52: You're reading this because you care about the future of NetBSD and
53: you understand that good tools act as a force multiplier.
1.8 wiki 55: ### Our decision is not obvious
1.7 schmonz 56:
57: If it were, we'd have made it already (and wouldn't be disagreeing
58: so persistently about which one it needs to be ;-).
1.8 wiki 60: ### Our decision needs to be about the whole elephant
1.7 schmonz 61:
62: We all understand the basics of using source control. This level
63: of understanding is necessary but not sufficient to make an informed
64: decision about whether to migrate any or all of NetBSD's repositories
65: to another VCS, and if so which, or how.
67: Our choice of VCS carries implications not only about how developers
68: hack on NetBSD, but also about how non-developers contribute and
69: become developers, and how Project sysadmins keep our valuable code
70: secure. Therefore, any choice of VCS other than the default (sticking
71: with CVS for a while longer) necessarily implies that as a group,
72: we all need to learn how we're going to do what we expect to need
73: to do. Not all of this learning needs to happen before we can make
74: a reasonably confident decision for our Project. But if we want to
75: arrive at consensus, much of it does.
77: There is no available choice of VCS that entirely avoids tradeoffs
78: for us. Therefore, to choose intelligently, we must first consider
79: all the tradeoffs we can think of, then decide which ones we can
1.10 jnemeth 80: live with and which we can not.
1.7 schmonz 81:
1.8 wiki 82: ### Our decision needs to be made together
1.7 schmonz 83:
84: We're a community. The only way a complicated, interconnected set
85: of changes like this can be implemented is for us to arrive at rough
86: consensus that some particular VCS:
88: - is sufficiently well suited to our project's needs in theory,
89: - is sufficiently easily adapted to our needs in practice,
90: - has a sufficiently fail-safe migration plan,
91: - is worth the effort to switch, and
92: - has volunteers to do the work.
1.8 wiki 94: ### How you can help, right now
1.7 schmonz 95:
96: What are some considerations you think are important? Are they
97: listed here? If not, edit this page and add them.
1.15 ! schmonz 99: ### Some previously collected considerations
! 101: * [[mailing-lists/tech-repository]]
1.8 wiki 103: ### Considerations
1.7 schmonz 104:
1.8 wiki 105: Humans
1.7 schmonz 106:
1.8 wiki 107: * People who administer Project resources
1.10 jnemeth 108: * People who administer release branches
1.11 schmonz 109: * People who administer security updates
1.8 wiki 110: * People who can commit directly to NetBSD
111: * People who can't commit directly to NetBSD
1.7 schmonz 112:
1.12 wiki 113: Machines
115: * Some ports/machines are memory constraint or rather slow (by todays standards), a VCS different than CVS should be able to used on these machines as well.
116: (e.g. git has parameters to tune memory usage, and there exists git-cvsserver which allows a git repository to be accessed using a CVS client)
1.1 mspo 117:
1.13 wiki 118: Workflow / Commonly used actions
120: * Checkout the whole tree
121: * Checkout a partial tree (or subdirectory)
122: * Create a branch
123: * Merge a branch with the head/main branch
124: * Create a tag
125: * Commit local changes to a branch
126: * Commit local changes to the main branch
127: * Revert a commit
128: * Fix a commit message
129: * Create a diff between two versions of a file
1.1 mspo 130:
1.14 wiki 131: Tools
133: * Command line tool
134: * Web based source code browsing and maybe riffing (in the style of e.g. trac)
135: * Availability on different platforms (pkgsrc is not NetBSD only)
1.1 mspo 137: """
CVSweb for NetBSD wikisrc <wikimaster@NetBSD.org> software: FreeBSD-CVSweb