>>>>> "Mark" == Mark J Nelson <Mark.J.Nelson at sun.com> writes:
Mark> mjn-03 In the "How to get started with Mercurial" section, the Mark> first paragraph (about the Mercurial website) should include a Mark> recommendation to read the book, which is described on the Mark> Mercurial website as "the unofficial manual." bos's (excellent) book is quite big. Our web page should definitely mention it, and probably encourage people to poke through it and get a feel for what's there. But let's *not* encourage people to read the entire book to get started. There's just too much there. Mark> mjn-08 This page needs to describe the conditions under which you Mark> would choose to use the mq extension, and then link to a Mark> separate page with more information on mq. Hmm, I'm not so sure about that. Most of the time when I read about someone who has trashed his repo, he's been using MQ. The XVM team needs to know about MQ since they're using it, but they presumably already have the documentation and links that they need. So I'd rather not mention MQ until it becomes clear that we need to. Mark> mjn-09 This page needs to tell a user how to get on the Mark> notification list for a repository (the equivalent of editing Mark> the old Teamware Codemgr_wsdata/notification file.) Well, we can tell them how to get on the notifiation list for onnv-gate. But the general case is a little tricky. We have a convention for using the name foo-notify, and people can add themselves to foo-notify using Mailman. But the SCM console lets the notification alias for foo-gate be any email address, and the notification alias is only visible to project leaders. I guess we can document the expected normal case, and tell people to ask a project leader if they can't find the notification list in Mailman. Do we want to also encourage project leaders to document the notification alias when they document the existence of a project repo? mike
