David,
Actually, when I get a lengthy e-mail, the last thing I want to do is read
it. I get enough of those, and they are likely to be shelved for when I
have time to deal with it. Sometime between now and when hell freezes over.
You want a response to your e-mail? Keep the scroll bars deactivated.
A nicely formatted page with a TOC that tells me what I can learn from it,
that I can add to Favorites, and refer to when needed; that's useful.
Also, a web page can be corrected. The first set of instructions on the web
page for how to setup CVS with ssh were wrong. They were corrected after a
new Committer went through them, found that they were wrong, found what
worked, and reported the problem.
By the way, this does not strike me as an infrastructure problem, so much as
an ASF Community thing. The infrastructure guys have enough to do with
keeping the plant running. The documents should live in either Incubator
(to be provided to PMCs), or on the main apache site.
--- Noel
-----Original Message-----
From: David Reid [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 13, 2003 5:35
To: community@apache.org
Subject: Re: Suggestion...
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]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
