Mark J. Nelson wrote: > I'm planning to do a KTD on Mercurial on Monday, January 12. BJ hasn't > sent an announcement because I need to give him an abstract. > > Which leads me to ask y'all: what topics are most useful for our > communities right now? Possibilities include:
At this point I think people still are in the process of learning how to use mercurial. I'd focus on everyday interactions and how common but more complex teamware activities translate to mercurial. I'd defer discussion about mercurial internals or how pieces of specialized infrastructure are implemented to a separate KTD or at most a separate section late in this one. This is both to prioritize the important information, and to limit confusion between what is common usage of mercurual and what are specific solutions that needed to be created only for things like the gate itself. > - Mercurial internals: how hg tracks changes, how to debug internal > data, how the internal model is reflected in the way we manage repositories I probably wouldn't go to deep into Mercurial internals, and I certainly wouldn't spend a lot of time discussing how to debug its internal data. It would be interesting, but I don't think that's what people need right now. > - merging: how it differs from Teamware, tools, setup, best practices > (possible tie-in to internals) Very important. Merging has changed considerably. It would be good to highlight when merges can take place (e.g. you can merge incoming changesets with un-committed changes, which might come as a surprise), and how (e.g. automerging and how one figures out the status of merges in their workspace). > - gate management: onnv-gate infrastructure, gate/clone arrangement, > hooks, divergent snapshots, best practices, tools Useful background. I'd focus on the gate/clone arrangement, the effect of the gate's hooks, and best practices for gate consumers. Those parts of the gate infrastructure that would be considered best practices should be communicated in "project gate management", and the rest I'd defer to an internals or case study discussion. > - project gate management: as relates to above, best practices, managing > synchronization from either clone or snapshot Very important. Setting up a project gate, notification lists, etc. is a lot more complicated than it was. The easy answer is "make an opensolaris project", but that's not always appropriate. Dave
