#601: What Organization Design Makes Sense: asking developers to review the
Goals (ticket #598) and Mission Statement (ticket #600) and suggest an
organizational design that fits.
------------------------------------------+---------------------------------
Reporter: p0g0 | Owner: mrenzmann
Type: task | Status: new
Priority: major | Milestone: MadWifi non-profit
Component: non-profit organization | Version: trunk
Resolution: | Keywords: non-profit
organization design
Patch_attached: 0 |
------------------------------------------+---------------------------------
Comment (by dyqith):
My 2 cents:
For this project there are clearly a few things for a Project Member to
do:
1. Bug fixes
1. New/Refine Features
1. User Support (i.e. Documentation and wiki)
Clearly, when a person has put enough time and effort into this project
should become a Project Member (i.e. submitting bug fixes or features and
adding to wiki, user support)
As to how to decide on who becomes a member, probably we can do group
decisions (voting when one member brings it up, or someone requests for
access, etc)
Probably we need a clause where when a Project Member adds in malicious
code, he/she gets banned from access permanently.
I'm thinking off the top of my head, so I may not make much sense :)
--
Ticket URL: <http://madwifi.org/ticket/601>
MadWifi <http://madwifi.org/>
Multiband Atheros Driver for Wireless Fidelity
