From Fedora Project Wiki
mNo edit summary
mNo edit summary
Line 11: Line 11:
'''The goal is to have this be one hour.''' Realistically, this is more like two hours. It will take a few minutes to read the materials needed to prepare for meetings/discussion. Steering the group should just take a bit of nuance :)  
'''The goal is to have this be one hour.''' Realistically, this is more like two hours. It will take a few minutes to read the materials needed to prepare for meetings/discussion. Steering the group should just take a bit of nuance :)  
There are plans to have elected leadership. No pressing need at the moment.
There are plans to have elected leadership. No pressing need at the moment.
== Structure ==
Events are held at members houses as well as hackerspaces. We do basic classes to help recruit our future geeks and contribs. We have group projects to help get anyone involved. Members bring personal projects that benefit from group brainstorming.
Group consensus decides direction. Tech decisions made by Dev Steering Board. 3 devs vote agenda for next meeting. A fourth alternate is available to keep an odd number (and continuity).
* [[User:Sexycatsinhats | Chris Whitehorn]]
* [http://www.shallowsky.com/ Akkana Peck]
*
* [[user:Rugebiker | Rubén Guerra Marín]] Alternate
There are plans to have elected leadership. No pressing need at the moment. Creating a formal mentoring and teaching process is a bigger priority. We do basic classes to help recruit our future geek


=== Include? ===
=== Include? ===


'''Right to dilute'''- the ability for the group to elect/appoint 2 members to form a Triumvirate of leadership.
'''Right to dilute'''- the ability for the group to elect/appoint 2 members to form a Triumvirate of leadership.

Revision as of 01:24, 3 June 2013

Duties

Providing dev skills to help with focus. Steering the group and it's projects. One hour a month.


  • Review the events and projects for the next month
  • Keep group projects growing tin a logical manner, as in steps needed.
  • Help fill in blanks
  • Coordinate with others on board
  • A meeting could be done in 20 minutes or less. More likely 10. MarkDude is NOT involved ;D Unless the board is giving him a todo list.
  • Right to dilute- the ability for the group to call for elections to form elect 2 members to form a Triumvirate.

The goal is to have this be one hour. Realistically, this is more like two hours. It will take a few minutes to read the materials needed to prepare for meetings/discussion. Steering the group should just take a bit of nuance :) There are plans to have elected leadership. No pressing need at the moment.

Structure

Events are held at members houses as well as hackerspaces. We do basic classes to help recruit our future geeks and contribs. We have group projects to help get anyone involved. Members bring personal projects that benefit from group brainstorming.

Group consensus decides direction. Tech decisions made by Dev Steering Board. 3 devs vote agenda for next meeting. A fourth alternate is available to keep an odd number (and continuity).


There are plans to have elected leadership. No pressing need at the moment. Creating a formal mentoring and teaching process is a bigger priority. We do basic classes to help recruit our future geek

Include?

Right to dilute- the ability for the group to elect/appoint 2 members to form a Triumvirate of leadership.