View source for Standing Resolution to Codify the Staff Collective

{{CollectivePhasedOut}}

''(This is a proposed standing resolution from the new bylaws project. It would not go into the bylaws (at least at this time) but would rather be acted upon by the board in conjunction with the [[New Bylaws Project]].)''

'''To start off, we're just pulling a proposed ammendment to the bylaws and putting it here. This is unfinished.'''

:We could address this issue in a contract with the staff collective, or as board policy. Those are the two general approaches I've heard suggested. [[User:Rfs|RfS]] 18:07, 29 Jul 2005 (PDT)

==ARTICLE VI. Staff Collective (proposed)==
:Thoughts: Function is to  Membership is composed of staff members hired into collective positions. Meetings are currently weekly, but we've talked about monthly or biweekly staff collective meetings and might want to move to that model in the future, especially if we grow larger and more stuff is accomplished in standing committees. Standing committees are committees set up by the staff collective to make sure that all areas of function inside FG are being covered. Standing committee meetings are generally open to volunteers as well as staff. Staff collective meetings and HR related committee meetings are generally open to only collective member, unless by invite (they potentially deal with staff discipline issues, etc.) Staff collective has been given a general budget to work with for salaries and benefits but gets to prioritize how that is spent. At one time we talked about the board giving "agent of corporation" status to staff members (so they could sign documents and such) and the board would have the ability to withdraw that if necessary. Staff collective however, is in charge of hiring and firing its own (and interns). Council is in charge of prioritizing new positions and job descriptions. In practice, the staff recommends much of this. [[User:Rfs|RfS]] 14:15, 11 Jul 2005 (PDT)
:: I suspect we don't need to include things like meeting schedule, stading committees, or salaries and benefits. Seems like it's enough to say that the staff collective exists, is a collective, is in charge of hiring/discipline/firing, and answers to council. --[[User:ideath|ideath]] 11:56, 19 Jul 2005 (PDT)

===Section 1. Function===

The function of the Free Geek Staff ("Staff") is to provide for the day to day day to day administration of FG, implementation of policies set by Council and Board, and maintenance of its own membership.

:  We also talk about the Council providing for the administration of FG between Board meetings.  I actually think the Staff collective wording is right, so do we need to tweak the wording found in the Council section.--[[User:Jkane|Jkane]] 09:29, 18 Jul 2005 (PDT)
:: I don't know the correct terminology, but the Council sets policy (so does the Board), and the staff implements it. The implementation part is probably "to manage" or "to administer". The "provide for" clause implies that the Council doesn't actually (normally) do it, but rather delegate it?  [[User:Rfs|RfS]] 09:03, 19 Jul 2005 (PDT)

===Section 2. Membership===

The Free Geek staff collective is responsible for hiring and discipline of its membership, and other Free Geek staff (e.g., paid interns).

:Definition to be provided by Ideath and Oso, unless Richard gets to it first. Thanks, Richard! --[[User:Ideath|Ideath]] 18:04, 13 Jul 2005 (PDT)


[[Category: Bylaws]]