https://docs.google.com/document/edit?id=15ru0kwhqAbT8QAVC5Bs0KMeT06ZP5RNnIIbEbeDVQjo&hl=en

Lazy consensus lazily added.

On Mon, Sep 20, 2010 at 5:36 PM, Benson Margulies <bimargul...@gmail.com> wrote:
> Ross,
>
> I completely spaced that out. I'm quite familiar with it. I'll add it.
> This is exactly why I wanted to get a review.
>
> --benson
>
>
> On Mon, Sep 20, 2010 at 5:16 PM, Ross Gardler <rgard...@apache.org> wrote:
>> This is a fine post and I have no objections to it being published as is. 
>> However, in the projects I work on the concept of Lazy Consensus is 
>> critical. That is, for the majority of actions permission need not be sought 
>> since most actions can be reversed. Thus non objection means consensus.
>>
>> This is particularly powerful since it requires people to be active if they 
>> want to have a say in the project. That is, people can't just turn up at 
>> discussion phase and throw a spanner in the works (as happens in so many 
>> committee run endeavours).
>>
>> Of course this relies on people knowing when they should ask for input on 
>> proposed changes. For me this is why merit is critical. For me merit 
>> indicates someone has learned when to ask permission as opposed to when to 
>> ask for forgiveness.
>>
>> If your experience in projects is different from mine with respect to lazy 
>> consensus, or if you prefer not to add this detail, I'll follow up with a 
>> post along the above lines.
>>
>> Sent from my mobile device.
>>
>> On 20 Sep 2010, at 21:20, Benson Margulies <bimargul...@gmail.com> wrote:
>>
>>> I think I posted the link to a folder instead of a link to the doc.
>>>
>>> https://docs.google.com/document/edit?id=15ru0kwhqAbT8QAVC5Bs0KMeT06ZP5RNnIIbEbeDVQjo&hl=en
>>>
>>>>
>>>> https://docs.google.com/document/edit?id=15ru0kwhqAbT8QAVC5Bs0KMeT06ZP5RNnIIbEbeDVQjo&hl=en
>>>>
>>>> Care to read before I put it on the blog?
>>>>
>>>> On Mon, Aug 16, 2010 at 6:07 PM, Ross Gardler <rgard...@apache.org> wrote:
>>>>> On 16/08/2010 23:03, Benson Margulies wrote:
>>>>>>
>>>>>> I have a goofy blog at blogger. Is there some mechanism for having an ASF
>>>>>> blog?
>>>>>
>>>>> http://blogs.apache.org/comdev/
>>>>>
>>>>> If you post your content here we'll get it up there for you (we've not
>>>>> really worked out access rights to the blog yet so I'll not assume my own
>>>>> preference is universal at this point).
>>>>>
>>>>> Ross
>>>>>
>>>>>>
>>>>>> On Mon, Aug 16, 2010 at 6:00 PM, Ross Gardler<rgard...@apache.org>  
>>>>>> wrote:
>>>>>>
>>>>>>> On 16/08/2010 22:37, Benson Margulies wrote:
>>>>>>>
>>>>>>>> Recent discussions on various lists have led me to think about
>>>>>>>> 'Consensus
>>>>>>>> Process' as an area of possible effort for comdev. People are not born
>>>>>>>> knowing how to operate a consensus process, and some discussions 
>>>>>>>> suggest
>>>>>>>> to
>>>>>>>> me that the communities might benefit from something written down as a
>>>>>>>> aid
>>>>>>>> memoire or training device.
>>>>>>>>
>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>>
>>>>>>>  I'm sure that I could find some references on this subject, but I'm 
>>>>>>> more
>>>>>>>>
>>>>>>>> inclined to type up a somewhat personal introduction to consensus
>>>>>>>> process
>>>>>>>> and see if anyone thinks that it's worth further work and eventual
>>>>>>>> publication.
>>>>>>>>
>>>>>>>
>>>>>>> Starting with a personal blog post on the topic would be great.
>>>>>>>
>>>>>>> You may want to look at the content at
>>>>>>> http://www.oss-watch.ac.uk/resources/meritocraticGovernanceModel.xml - 
>>>>>>> in
>>>>>>> particular section 2.4
>>>>>>>
>>>>>>> This document discusses the mechanics of consensus and decision making 
>>>>>>> in
>>>>>>> a
>>>>>>> meritocratic project. However, it does not discuss the social aspects.
>>>>>>>
>>>>>>> It's always been my intention to bring that content here, but I've not
>>>>>>> found the time yet. It's currently CC-BY-SA, but I'm happy to make it
>>>>>>> available under an Apache Licence if it would compliment your work in 
>>>>>>> any
>>>>>>> way.
>>>>>>>
>>>>>>> Ross
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>
>

Reply via email to