On Wed, Jan 4, 2012 at 6:04 PM, Simon Phipps <[email protected]> wrote:
>
> On 4 Jan 2012, at 22:59, Rob Weir wrote:
>
>> On Wed, Jan 4, 2012 at 5:23 PM, Dennis E. Hamilton <[email protected]> wrote:
>>> I personally find the absence of a list-name prefix, something simple like 
>>> [ooo-users], to be a problem.
>>>
>>> First, if folks BCC the list, it is a problem.  And when getting 
>>> cross-postings among lists that don't prefix, that is another problem.
>>>
>>> And there are some peculiar situations where a message is administratively 
>>> forwarded from one list to another where, as the recipient of one of those, 
>>> I have no idea what happened and why it is in my inbox (or spam folder) 
>>> instead of where my mail-arrival rules put things.
>>>
>>> On the other hand, there is no button to push to make prefixing work.  
>>> Sorry.
>>>
>>> As Andrea observes, it is possible to request that infrastructure make 
>>> whatever incantations are necessary to add a prefix for this list.
>>>
>>> I have not heard any objection.
>>>
>>> Applying the Apache lazy-consensus principles, I will wait at least 72 
>>> hours (until midnight UTC: 2012-01-07T24:00Z) for any objections to be 
>>> heard.  If the discussion has quieted and there is no substantive 
>>> objection, I'll turn in a request to add the prefix.
>>>
>>
>> Actually, you need to make that proposal on ooo-dev
>
> Since they are not affected, why would that be useful or necessary, Rob?
>

Your assumption is incorrect.  For example,  list moderators are
affected, although they are not required to actually subscribe to the
lists they moderate.

In any case, the PPMC makes lazy consensus proposals on ooo-dev.  That
is to ensure that there is a single well-known place where we can look
for proposals.

> S.
>
>
>
> ---------------------------------------------------------------------
> 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]

Reply via email to