From Fedora Project Wiki
< BAMF
m (→Structure) |
mNo edit summary |
||
| Line 17: | Line 17: | ||
* 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. | * 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. | ||
'''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. | ||
Revision as of 21:02, 12 May 2013
Structure
Group consensus decides direction. Tech decisions made by Dev Steering Board. 3 devs vote agenda for next meeting. A fourth is designated as an alternate and is available to keep an odd number as well as continuity.
- Chris Whitehorn
- Akkana Peck
- Rubén Guerra Marín Alternate
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.
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.