Re: [OSCOM] Sandro steps back

On Sep 8, 2006, at 8:38 AM, Chalu Kim wrote:

> Paul Everitt wrote:
>
> snip
>>
>> At this stage, we should probably constrain feedback to "I cannot   
>> accept that election process" instead of "Maybe it would be  
>> better  if".  It's not easy, at this stage, to tell when a  
>> discussion ends  and how to convert open discussion into policy.
>>
>>
>
> As I mentioned, what is important to me is the make-up of the  
> decision making body to steer OSCOM to open up and to find newer  
> audience because I don't find it neutral or far-reaching.

> If I get this right, members and board decides policies and projects?

At this stage, nobody knows.  Everything is in limbo.  Some have  
advocated that we get a clean slate of members and board before  
tackling new policies and projects.  I agree with that group of  
people.  I'm trying to solve that and facilitate getting the new  
blood in place.

Having long-range decisions now about new projects and policies,  
before the new blood replaces the old blood, is a concern shared by a  
few folks here.

> If so, one needs to field "ideas" during the ideas stage. They need  
> to be discussed. Also, this seems myopic or tunnel vision when  
> topics are generated by the same demographics like developers.

That is the correct long-term way to do things, yes.  But there seems  
to be a feeling that the existing board is the root problem.  As  
such, I'm trying to get that problem solved ASAP.

Others can solve different problems using different processes.   
That's what OSCOM-the-community is about.  I'm not trying whatsoever  
to interfere with that.  I'm simply trying to get OSCOM-the-legal- 
entity into new hands, following the crappy rules in the crappy  
bylaws.  They can then be the ones that facilitate the new bylaws,  
new culture, new ways to reach consensus, new ways to act, decide how  
to spend the money, whatever.

This in no way impacts your "What is our vision" thread and  
collaborative discussion.  They are two separate things.

--Paul