-1 for permissions change for dev@
+1 for a clearer description

any native speaker volunteering?

--Manfred


On Thu, Sep 4, 2008 at 6:54 PM, Simon Lessard <[EMAIL PROTECTED]> wrote:
> -1
>
> However, it's true that Apache product users often consider themselves
> developer and thus post on the developer forum even when their question
> should really be on the user list. We could probably reduce such occurrences
> a little by adding a clearer explanation of the purpose of each list on the
> mailing page.
>
>
> Regards,
>
> ~ Simon
>
> On Thu, Sep 4, 2008 at 12:12 PM, Paul Spencer <[EMAIL PROTECTED]> wrote:
>>
>> Andrew,
>>
>> The dev@ mailing list is described on the Jakarts site[1] as:
>>  The "Developer" lists where you can send questions and comments about
>>  the actual software source code and general "development" types of
>>  questions.
>>
>> Making the developer list private is extreme and I would resist this
>> change.  Their are many productive discussion on the developer list that
>> include non-committers or non-pmc members.
>>
>> Are the posting to the developer list because the question is not answered
>> on the user list?  If so, then lets address this problem first.  If not,
>> then should the response to an user@ post on the dev@ list be something like
>> "You have posted this to the wrong list, please repost this on the user@
>> list"
>>
>> The dev@ mailing list is described on the Jakarts site[1] as:
>>  The "Developer" lists where you can send questions and comments about
>>  the actual software source code and general "development" types of
>>  questions.
>>
>> Making the developer list private is extreme.  Their are many discussion
>> on the developer list that include non-committers or non-pmc members.
>>
>>
>> Paul Spencer
>>
>> [1]http://jakarta.apache.org/site/mail.html
>>
>>
>> Andrew Robinson wrote:
>>>
>>> Is it possible to make dev@ a private mailing list, so only commiters
>>> and people that PMCs decide should have access to post are allowed to
>>> send emails to this list? That way we can reduce the accidental
>>> posting to dev@ instead of [EMAIL PROTECTED]
>>>
>>> -Andrew
>>>
>>
>
>

Reply via email to