On 12/7/18 12:08 PM, Shane Curcuru wrote:
> Bertrand Delacretaz wrote on 12/7/18 10:14 AM:
>> Hi,
>>
>> On Fri, Dec 7, 2018 at 3:53 PM Jay Vyas <jayunit100.apa...@gmail.com> wrote:
>>> ...At the CNCF, I’ve noticed that almost all decisions are made in hangouts 
>>> and in GitHub issues, and proposals..
>>
>> I think this is exactly how Apache projects are supposed to operate:
> 
> Yes, absolutely! but one addition is important
> 
>> *all* discussions and decisions in public places unless there's a very
>> good reason for them to happen in private.
> ...snip...
> 
> s/public places/publicly accessible and archived places/
> 
> A key part of the Apache Way is the explicit use of archived
> communication methods and timeshifting final decisions - the minimum of
> 72 hours (or longer) for final decisions.
> 
> Anyway, the definitive statement of what should be public vs. private in
> project governance still sounds pretty good as-is:
> 
>   https://www.apache.org/dev/pmc.html#mailing-list-naming-policy
> 

It kinda feels like everyone is saying the same things in different ways.

We should always push everything possible to public, archived venues. My
*preference* is for this happening on the dev@ list, rather than
creating Yet Another Mailing List for public pmc discussions.

Our tradition is mailing lists because they are public, archived, and
universally accessible. Some of the other venues mentioned are not (one
or more of those things).

I have, over the last few days, seen several of our project communities
use their private list for discussions that were not, in anyway,
sensitive. I have called them out on this, but, in each case, my message
has been utterly ignored.

I guess my reason for that remark, and my question here, is to what
degree do we want to *compel* this behavior?

-- 
Rich Bowen - rbo...@rcbowen.com
http://rcbowen.com/
@rbowen

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Reply via email to