Steve, Here's a few comments...
- You may want to be less hard on Teamware and remove: slide 1: "teamware is dead, long live mercurial" slide 11: "made Teamware suck less" Some people may take offense Slide 3: - I would list specific reasons why we are changing to Mercurial and not just leave it to the reader (even though you may talk about it) This is a HUGH impact on Sun developers and they need to know why they have to change in clear terms. This will also help people who can't make the meeting. You may need to add a slide. Slide 4: - We need to plug training into the equation. We won't be successful unless people know how to use the new tools. Slide 5. - Can you add a slide showing the SFW gate conversion, since it is less complicated than the ON gate and more standard? - Why don't we have an external clone? Is the readable clone/writable gate not needed anymore? - if we pull from the internal clone, and we can't do partial bringovers, then do a push to the external gate won't there be issues with usr/closed? - it's weird having a "clone" that has more then the gate Also, It would be good to have one place we can point people where all the new commands are listed (workspace and gatekeeper). Right now they are spread out or not listed. Cheers, Jim Stephen Lau wrote: > Here's what I have so far if people want to start reviewing it. I'll > continue to work on them this morning - but thought I might as well send > out what I have. > > Feedback appreciated. > > and many many thanks to Mike for his work on the outline - that made it > considerably easier to work on this. > > one thing that just came to mind before I leave home to head into the > office is that we should mention gPyFm explicitly somewhere. > > cheers, > steve
