I have a lot of sympathy with that view, and it should probably be on a web page somewhere as well, but in all honesty getting an email with instructions makes it much easier than simply telling people to visit a web page. While we'd all like to think people would follow the link to the page I think deep down we all know that not everyone will. Not everyone will read an email either but I think we'd get a better response with an email.
The belt & braces approach is always good. As I've not heard any objections I'll send an email to infrastructure. david > David, > > I agree that there should be an e-mail. But it should be short, and consist > of little more than a reference to the web site. All of this information > should be available on the web site for review and update. As that content > is enhanced, e-mail can go out to [EMAIL PROTECTED] > > > - forwarding instructions for the @apache.org email address > > - contacts for common problems > > - information about the committers list and the reason for it > > - information on opt-in lists such as licensing, community > > Also explain public_html, umask 002, using ssh with keys, pgp/gnupg, source > control, mirroring, and every other process issue that a Committer might > need to know during the course of their duties. > > --- Noel > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
