FYI, I had 15 responses to the email I sent tools-discuss on 7/13asking
for help from Mercurial volunteers.
Everyone is willing to present but they need materials. I'm thinking
they could probably start by re-using the KTD materials after the 8/13
presentation.
The 'materials.txt' attachment contains pointers to some information
that is available. Michelle, I was thinking we should transfer the
table on Martin's blog entry to a web page and then ask people to send
updates as they work on their own transitions and accumulate more
information. I'm willing to set that up if that would help.
I also have a copy of the 'developing in ON' slideset. It has been
converted from FrameMaker and has had an initial attempt made to add
some Mercurial information to it. It's far from done, though. It it
would be useful, is anyone interested in working on it?
I remember a conversation where we were thinking these pages belong on
opensolaris.org. Does that make sense to everyone? Within the SCM
Migration Project?
Thanks.
Bonnie
michelle olson wrote:
> Hi Mike,
>
> Thanks for this feedback, much appreciated. It sounds from your mail
> about the KTD that we need some content pretty quickly, so I'll get
> rolling on drafts for review. I look forward to seeing the pointer to
> your script, so we can do some testing.
>
> Regards,
> Michelle
>
> Mike Kupfer wrote:
>
>>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
>>
>
> _______________________________________________
> scm-migration-dev mailing list
> scm-migration-dev at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/scm-migration-dev
-------------- next part --------------
A non-text attachment was scrubbed...
Name: materials.txt
Type: application/text
Size: 679 bytes
Desc: not available
URL:
<http://mail.opensolaris.org/pipermail/scm-migration-dev/attachments/20070726/7423646e/attachment.bin>
