Re: Bylwas Revision: COMMITTEES

From: Nils Lohner <lohner(at)typhoon(dot)icd(dot)teradyne(dot)com>
To: Christoph Lameter <christoph(at)lameter(dot)com>
Cc: spi-general(at)lists(dot)spi-inc(dot)org
Subject: Re: Bylwas Revision: COMMITTEES
Date: 1999-04-01 18:30:44
Message-ID: 199904011830.NAA28979@typhoon.icd.teradyne.com
Views: Raw Message | Whole Thread | Download mbox
Thread:
Lists: spi-general

In message <Pine(dot)LNX(dot)4(dot)03(dot)9903300821400(dot)18796-100000(at)cyrix200(dot)lameter(dot)com>
, Chr
istoph Lameter writes:
>I would rather favor having individuals making those decisions. Committees
>are useful if you want to slow down any possible dangerous decisions or
>if power needs to be controller but Committees are not useful for day to
>day operations. I would like this to be as non-political as possible. So
>far we have had a pretty informal structure and it worked mostly.
>
>Could we make all of this as simple as possible? This looks more and more
>to me as if we are building a big administrative apparatus.
>

Yes, simplicity is definitely a goal, but you have to leave room for the
organization to grow and mature, so a certain complexity is needed.

>I would like to see a list of jobs for individuals within SPI and then a
>responsibility to the BOD.
>

Here I disagree a little (we had this discussion on IRC, I'm repeating
here for everyone elses benefit). It may be easier with individuals, but
I think you need a committee so that there is always someone else who can
also do the work. Off course the committees should be more or less
reactive, depending on what they are in charge of. This is left up to
their charters I think...

Nils.

>On Tue, 30 Mar 1999, Nils Lohner wrote:
>
>>
>>
>> This is the beginning of the discussion for the committee article of
the
>> bylaws. Here are some basic principles which I feel should apply to
the
>> committees.
>>
>> - they should take care of most of the day to day operation of SPI
>> [this takes the workload off the BOD]
>> - their rights and responsibilities should be completely described in
>> their charter
>> - they should be governed by the board of directors
>> [what does this really mean? I'm not sure yet... but that's who they
>> should 'report' to]
>> - the BOD should be able to issue charters (i.e. create committees)
>> [I'm thinking that if the consensus is that a new committee is
needed,
>> the BOD can issue a charter. The membership should definitely have
some
>> input here though. how? By helping write the charter.]
>>
>>
>> QUESTIONS:
>> ----------
>> - how are leaders appointed? I'd say by the BOD, possibly the
membership.
>> - how are members appointed? BOD? Leader? Membership?
>> - should non-contributing members be able to serve on committees?
>> [incidentally, that would automatically make them contributing
>> members...!!]
>> - what do we do if a committee is no longer necessary? disband it.
How?
>> BOD vote?
>>
>>
>> I'm sure there are other issues here that I'm not addressing... please
>> bring them up if you think of them! As I think you can see, this
>> discussion is one step closer to the voting discussion, as this will
bring
>> up a lot of issues regarding who controls what and why. I think that
when
>> we're done with this discussion, the voting discussion will be a lot
>> easier because the political infrastructure will be in place.
>>
>> Enjoy...
>> Nils.
>>
>>
>> --
>> Nils Lohner Software in the Public Interest,
Inc.
>> E-Mail: lohner(at)spi-inc(dot)org PO Box 1326
>> Board Of Directors <board(at)spi-inc(dot)org> Boston, Ma. 02117 USA
>>
>>
>>
>> --
>> To UNSUBSCRIBE, email to spi-general-request(at)lists(dot)spi-inc(dot)org
>> with a subject of "unsubscribe". Trouble? Contact
listmaster(at)lists(dot)spi-inc(dot)o
>rg
>>
>>
>>
>
>

Browse spi-general by date

  From Date Subject
Next Message bruce 1999-04-02 19:59:25 Re: [PROPOSAL] Open Source certification
Previous Message Marcelo E. Magallon 1999-04-01 00:04:56 Interesting bit on IDC's ``forecast''