Changes between Version 10 and Version 11 of roles_and_leadership_committee


Ignore:
Timestamp:
Oct 2, 2007, 3:26:08 PM (18 years ago)
Author:
Jamie McClelland
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • roles_and_leadership_committee

    v10 v11  
    11Members: Amanda, Alfredo, Nat, Ana, dkg, Josue, Jamie, Mark, Jon
    2 
    3 
    4 === Titles Brainstorm ===
    5 
    6  * member
    7  * co-director
    8  * member of leadership council
    9  * help with support queue
    10 
    112
    123=== Roles Brainstorm ===
    134
    14 What do we want people to do? What do you want to do?
     5What do we want people to do? What do you want to do? What roles need to get done but might be hard to fill?
    156
    167 * pay money
    178 * use web and email hosting services
    189 * use backup services
    19  * promote and participate in political conversations about the organic internet;
     10 * promote and participate in political conversations about the organic internet
    2011 * participate in community of users of technology
    2112 * participate in community/ provide mutual aid to other technology assistance providers
    … …  
    2718 * be responsible for server maintenance (monitor security lists; implement kernel upgrades)
    2819 * help maintain servers (pitch in when asked, rather than be accountable over time)
    29  * provide feedback on political direction of organization (eg. leadership council)
     20 * provide feedback on political direction of organization (eg. advisory council)
    3021 * provide feedback on technical direction of organization
    3122 * lead trainings
    3223 * build social and economic justice movements
    33  * be available as a consultant to members who need tech assistance
     24 * be available as a consultant to members who need tech assistance
     25 * bookkeeping and related activities
     26 * accounting and related activities
    3427
    35 === How to support brainstorm ===
     28=== Structure ===
    3629
    37 We won't be able to provide the infrastructure (technical or social) to support all the roles people can and want to play. What structures (loosely defined) can we set up that will support the ones we think are the most important for May First/People link? List below a description and pitch for structures to facilitate people playing the roles above.
     30Below is an attempt to describe the transition from the current structure to the next structure. It's not a depiction of an ideal power structure. Instead it's more of a real depiction based on where we are now.
    3831
    39  * Tech team - whether you're a tech genius or someone who knows how to explain things in plain English, we could use your help on everything from helping out on the support system to building new servers. All communication for the tech teams happens at https://support.mayfirst.org. To get notified of new tickets and events, configured your RSS reader to pick up new tickets or subscribe to the support-team email list here...
     32 * Co-directors - The co-directors make decisions for the organization based on input from the advisory committee. Co-directors are not formally chosen, but emerge based on amount of work provided to the organization.
    4033
    41  * Member team - interested in learning about our other members? Want to meet more people doing similar work? The member team coordinates member office visits, member events and trainings.
     34 * Advisory Committee - composed of the co-directos and members committed to the statement of unity (http://mayfirst.org/unity) and interested in contributing to the advisory and direction of the organization.
    4235
    43  * Consortium - are you interested in picking up new tech projects? Join the consortium to help build a solid network of individuals and groups doing tech work for the movement.
    44  
    45  * Leadership team - if you have been working as a member for a while and you are interested in stepping up your commitment, we need your help developing the direction and leadership of the organization.
     36 * Teams - Teams are informal groups of members who want to give labor to the organization with varying degrees of commitment.
    4637
    47 === Leadership Council Brainstorm ===
     38=== Teams ===
    4839
    49  * 10 - 15 members drawn from May First/People Link membership
    50  * Meets in person 2 - 3 times per year
    51  * Participate in email list
    52  * Members are periodically consulted by phone
    53  * What are the expectations of the members?
    54  * How is consensus reached?
    55  * What power does this group have
    56  * How is this group selected
     40 * Tech team - whether you're a tech genius or someone who knows how to explain things in plain English, we could use your help on everything from helping out on the support system to building new servers. See the tech team wiki for suggestions on how to get involved or contact the tech team intake person.
     41
     42 * Member team - interested in learning about our other members? Want to meet more people doing similar work? The member team coordinates member office visits, member events and trainings. See the member team wiki page for suggestions on how to get involved or contact the member team intake person.
     43
     44 * Consortium team - do you do web development, design, or other Internet related work? The consortium team helps members by doing free or paid gigs for them. See the consortium wiki page for suggestions on how to get involved or contact the consortium intake person.
     45
     46=== Advisory Committee ===
     47
     48'''How many members are on the Advisory committee?'''
     49
     50Approximately 10 - 15 members drawn from May First/People Link membership
     51
     52'''How often does it meet?'''
     53
     54The advisory committee meets in person 2 - 3 times per year, exchanges 5 - 10 messages per week via an email list, and individual members are periodically polled by phone.
     55
     56'''What are the expectations of the members?'''
     57
     58The members of the advisory committee include the co directors. Members are expected to participate in the meetings as described above. Members are expected to operate based on the statement of unity (http://mayfirst.org/unity). Members are expected to work together in good faith with the goal of building consensus when differences emerge.
     59
     60'''What are the expectations of the co-directors?'''
     61
     62The co-directors are expected to make decisions and take actions for the organization based on the concerns and issues raised by the advisory committee.
     63
     64'''How is consensus reached?'''
     65
     66Sometimes it is reached, sometimes it is not reached. The advisory committee is not a formal decision making body, so consensus is not required, although it is the goal.
     67
     68'''How is this group selected'''
     69
     70The co-directors will propose candidates to the existing leadership/roles committee and will invite members to participate based on the feedback and suggestions.
     71
     72'''What power does this group have'''
     73
     74The relationship between the co-directors and the advisory committee will depend on how each party lives up to their expectations. If each party lives up to their expections, it will be a powerful body. If one party or the other does not live up to their expections, we'll have to try something else.
     75
     76'''What's the time frame for this advisory committee?'''
     77
     78The advisory committee should re-evaluate itself after 6 months so we don't keep something alive that is clearly not working. If it does work during the first 6 months, it should nonetheless be considered a transitional model with a one year lifetime. One of the charges of the advisory committee should be to determine the next leadership model for the organization.