Hi Michelle, welcome on board!
> 1. Migration information for gatekeepers of TeamWare hierarchies
> currently inside SWAN.
> 2. Migration information for project leaders with child gates currently
> inside SWAN.
> 3. Relocation information for gatekeepers of Hg repositories currently
> inside SWAN.
> 4. Training information for developers currently using TeamWare inside SWAN.
> -Access rules/roles for projects using Hg
> -Procedures for clone, pull, build
> -Procedures for lint, test, test putback, RTI, etc. equivalents
Since we're going to move the gate to Mercurial first, and then later
move the gate to opensolaris.org, I think the priorities should be
1. training information for developers using Teamware inside SWAN.
I'm listing this first because it will have the biggest effect on
people's day-to-day productivity. So the sooner we can refer people
to it, the sooner we can get feedback and start polishing it.
Ideally, this could be written so that it's applicable no matter where
the onnv gate is (on-SWAN or on opensolaris.org).
I think this includes your #2 ("migration information for project
leaders"). As you noted, the material is mostly the same. And people
will need to know how to reparent their workspaces anyway.
2. migration information (Teamware to Mercurial).
I'd be careful about using the term "gatekeeper" in this context.
Strictly speaking, anyone who has a personal bugfix workspace is the
gatekeeper for that workspace, but I'm not sure everyone realizes
that. I don't want people to read the 1-line description and
erroneously conclude that they don't need to look at it ("I'm not a
project gatekeeper").
As Steve noted, I've been working on a migration script. I have one
more thing to add to it. When that's done, I'll send you a pointer to
the man page.
3. relocation information (moving a Mercurial workspace from on-SWAN to
opensolaris.org).
Again, I'd be careful about using the term "gatekeeper".
The bullets that you listed for each of your 4 pieces look good to me.
We may need to build up the troubleshooting sections over time, as we
see what the initial volunteers run into.
mike
