(Rough Draft 0.4)
Contributing
There are four areas in which you may "belong" for contributing to Source Mage GNU/Linux:
- Unofficial Developer
- Official Developer
- Official Lead
- Official Team Lead
Being an Unofficial Developer is the easiest and least intensive, while the others become progressively more time consuming. Most Official Developers will start out as Unoffical Developers and then either ask or be asked by an Official Team Lead to join the team they feel they'd most enjoy/benefit.
All code developed by/for Source Mage GNU/Linux is licensed under the GPL.
Developer Duties
Here is a list of requirements/duties if you're thinking of contributing to Source Mage GNU/Linux and your status.
Unofficial Developer
Submit patches and/or bug reports to http://bugs.sourcemage.org
Recommended, but not required: Hang out in #sourcemage on irc.freenode.net
Have a read-only clone of our git repositories and ask developers to pull changes from you (See HowTo/AnonymousGit)
Official Developer
- Work under a Team Lead
- Vote for Team Leads
- Submit fixes through our Source Code Management (SCM) system
Attend announced developer meetings in #sourcemage-admin
Recommended, but not required: Hang out in #sourcemage on irc.freenode.net as well as your team's #sourcemage-<team> channel (e.g. #sourcemage-sorcery, all of them are listed in Contact_Us).
Official Lead (lead)
- Vote for Team Leads
- Submit fixes through our Source Code Management (SCM) system
- Communicate with other developers
Hang out in #sourcemage on irc.freenode.net as well as your team's #sourcemage-<team> channel (e.g. #sourcemage-sorcery, all of them are listed in Contact_Us) and #sourcemage-admin.
Attend announced developer meetings in #sourcemage-admin.
Official Team Lead (component lead)
- Vote for Team Leads
- Submit fixes through our Source Code Management (SCM) system
- Communicate with their team members
- Communicate with other Team Leads
- Subscribe to and read all SCM commits by all developers
http://scmweb.sourcemage.org/ is an alternative that may be easier to read than email.
Hang out in #sourcemage on irc.freenode.net as well as your team's #sourcemage-<team> channel (e.g. #sourcemage-sorcery, all of them are listed in Contact_Us) and #sourcemage-admin.
Attend announced developer meetings in #sourcemage-admin.
Project Lead
The Project Lead (PL) is responsible for the following:
- Maintain cohesion between the various Team Leads
- Schedule and preside over developer meetings
- Initiate and administer public votes for Source Mage GNU/Linux
- Promote Source Mage GNU/Linux to news organizations, magazines, and websites
Maintain the Sorcery_RoadMaps
- Forward appropriate Team announcements to the proper channels
- Maintain contacts with popular news sites that accept our
announcements (DistroWatch, OSNews, Slashdot, magazines, etc.)
- Announce team releases (Sorcery and Cauldron mainly) to news sites
- Work with the Tome Team to keep our website "schnazzy"
Sorcery Lead
- The Sorcery Lead (SL) will be responsible for the following:
Manage The_Sorcery_Team to produce timely and stable Sorcery releases
- Maintain Sorcery release tarballs and send out announcements as well as maintaining the following information
Freshmeat Sorcery branch
- Sorcery documentation
- The Project Lead will forward stable release announcements to various news sources
Maintain the Sorcery_RoadMaps
Sorcery ChangeLogs
Grimoire Lead
- The Grimoire Lead (GL) will be responsible for the following:
- Recruit capable users to fill in section guruships as well as general guruship
- Maintain grimoire documentation
Maintain a Roadmap
Grimoire Guru Handbook: GrimoireGurusHandbook NewGuruHandbook
Setup and maintain Prometheus
- Setup and maintain a system to system-test each "release" of the stable grimoire
- Organize groups to test grimoires, ISOs, Sorcery, and documentation accuracy
- Keep abreast of security issues and make sure Source Mage GNU/Linux is not vulnerable
- Subscribe to at least these mailing lists (security_[at]_sourcemage_[dot]_org is already subscribed to them)
(list of security sites here)
Cauldron Lead
- The Cauldron Lead will be responsible for the following:
- Maintain ISO releases and send out announcements as well as maintaining the following information
Freshmeat ISO x86 branch
Freshmeat ISO PPC branch
ISO ChangeLogs
Maintain the ISO RoadMap
Tome Lead
The Tome Lead will be responsible for the following:
- Maintain our websites, keep them up-to-date, and close security vulnerabilities
- Maintain documentation accuracy