On Thu, 22 Mar 2001, Ted Husted wrote:
> So, I've got an application that I'm working on that I'd like to check
> into the sandbox CVS, so I can share it with some other Jakartians.
>
For sandbox, I don't think we need any hard and fast rules. It's an
experimental playground, after all.
For the commons CVS repository, we do need to work out the nitty gritty
details on directory structures, CVS usage, and such.
> Is the idea that I should create a branch for this, so it doesn't get
> mixed in with other people's project?
>
In sandbox, there are no releases, right? Therefore, no need for
branches. Even if there were multiple "projects" in the same CVS
repository, branches won't typically be required because people will be
building from specific subdirectories anyway.
> Would I be able to create a branch for "husted" and then put other
> branches under it?
>
> Or, should I create a "husted-gavel" branch for this application at the
> root?
>
> My only experience with CVS is here, and then only with file structures
> others had already defined.
>
> Second question, all Committers are entitled to access by default. But
> can we also vote-in a "developer" if we wanted to work on some sandbox
> code (before our colleague made committer status)?
>
Doing so would require the person to have an account on the server, and
therefore have pretty significant access. I'd think the rules are clear
-- existing CVS committers on any Jakarta subproject have access.
> -- Ted Husted, Husted dot Com, Fairport NY USA.
> -- Custom Software ~ Technical Services.
> -- Tel 716 737-3463.
> -- http://www.husted.com/about/struts/
>
Craig
