Difference between revisions of "Core Team Responsibilities"

Revision as of 19:53, 1 February 2011

There are responsibilities associated with being an active Funtoo Linux developer. These responsibilities are detailed below.

Metro

• Reliable automated builds are a priority of the Funtoo Linux project.

Active Funtoo Linux developers must use Metro to regularly build Funtoo Linux stages. Builds must happen at least once a week, and may be automated via cron job. Developers must be aware of any build failures that exist and communicate them to the rest of the team, and take steps to ensure they are resolved.

Install Testing

• A trouble-free installation experience is a priority of the Funtoo Linux project.

Active Funtoo Linux developers must perform a fresh install of Funtoo Linux from current stage3 at least once per calendar month. This install may be in a virtual machine, or to replace an existing install. During this install process, any bugs or anomalies must be documented on the Usability Testing page, reported to the rest of the team, and steps should be taken by the developer to address any problems found.

The Development Lead may assign "install weeks" to particular developers to ensure that Funtoo Linux installation is tested as frequently as possible.

Availability

• Excellent user support and timely resolution of problems is a priority of the Funtoo Linux project.

A Funtoo Developer maintains "active" status by being available for consecutive week-long periods to perform active development, fix bugs and participate in the #funtoo development channel, forums or funtoo-dev mailing list. A developer does not need to be available on a particular day, but must be available and active for at least 4 days per week.

Week-long absences are permitted as long as they are announced in advance to staff@funtoo.org so that adequate developer coverage for any particular week can be assured. Any absence longer than a week in duration should be announced in advance as well, but will result in the developer moving from the role of active developer and member of the core team to a Staff position in their absence.

Developers that are unavailable and move to a Staff role due to their absence may be reinstated as members of the Core Team when they are available, at the discretion of the Development Lead. However, there will be a limited number of "seats" available on the Core Team, and empty positions may be filled in your absence. The Development Leads may decide to expand the size of the Core Team, but this is not a requirement.

This policy exists to provide an incentive for Core Team members to remain continually active on the project. It also exists to allow for flexibility for those who may have intermittent availability -- we want to accommodate those people too, but it is easier for us to work with people who can make a consistent time commitment. This policy is also designed to accommodate certain realities of Free Software projects: often, we have a contributor who is active for several months and makes many valuable contributions to Funtoo Linux, but then they become inactive. If we keep this person as a Core Team member, they may prevent others who are available from actively contributing to Funtoo Linux. Therefore, having the Core Team be more dynamic in nature is designed to maximize opportunity for those to contribute to Funtoo Linux.