2,411
edits
Changes
Jump to navigation
Jump to search
mLine 116:
Line 116: − + Line 129:
Line 129: − + − + − + Line 143:
Line 143: − + Line 149:
Line 149: − + Line 177:
Line 177: − + Line 192:
Line 192: − + Line 203:
Line 203: − + Line 211:
Line 211: − + Line 227:
Line 227: − + Line 346:
Line 346: − +
Change level of heading
==Developers Group==
==Developers Group==
Overview
===Overview===
The developers group, supported by the Development Manager, can be split into four areas:
The developers group, supported by the Development Manager, can be split into four areas:
The Development Manager (DM) will strive to support the efforts of all groups.
The Development Manager (DM) will strive to support the efforts of all groups.
==Core Platform Developers==
===Core Platform Developers===
The Core Platform Developers are responsible for the development of the core packages that make up the SME Server and for alignment with any upstream releases upon which the server is based. The output of this group is a set of packages that can form a new release. One becomes a core developer by volunteering and demonstrating competence to the current developers.
The Core Platform Developers are responsible for the development of the core packages that make up the SME Server and for alignment with any upstream releases upon which the server is based. The output of this group is a set of packages that can form a new release. One becomes a core developer by volunteering and demonstrating competence to the current developers.
==Contrib Developers==
===Contrib Developers===
The Contrib Developers are responsible for packages that add functionality to an SME Server release. These packages are not part of the release, but some may be included in future releases. Others will always be maintained as separate packages. The output of this group is a set of "contribs", each of which may be composed of multiple packages. One becomes a contrib developer by either volunteering or developing and announcing a package.
The Contrib Developers are responsible for packages that add functionality to an SME Server release. These packages are not part of the release, but some may be included in future releases. Others will always be maintained as separate packages. The output of this group is a set of "contribs", each of which may be composed of multiple packages. One becomes a contrib developer by either volunteering or developing and announcing a package.
==Maintenance Team==
===Maintenance Team===
The Maintenance Team is responsible for releases after their release. The output of this team is a set of packages that should be applied to previous releases to maintain its functionality. The updates are not intended to extend the functionality of the release. The updates will include bug-fixes and security updates. One becomes a maintenance team member by volunteering.
The Maintenance Team is responsible for releases after their release. The output of this team is a set of packages that should be applied to previous releases to maintain its functionality. The updates are not intended to extend the functionality of the release. The updates will include bug-fixes and security updates. One becomes a maintenance team member by volunteering.
There is also a closed sub-team, the Security Team, that will review security issues. It is expected that there will be some overlap between the core platform developers group and security sub-team. This group is the only closed group in the organization for security purposes. One becomes a member of the Security Team by application to the Development Manager, and approval by the existing Security Team members. The Development Manager will be a member of the Security Team.
There is also a closed sub-team, the Security Team, that will review security issues. It is expected that there will be some overlap between the core platform developers group and security sub-team. This group is the only closed group in the organization for security purposes. One becomes a member of the Security Team by application to the Development Manager, and approval by the existing Security Team members. The Development Manager will be a member of the Security Team.
==Support Team==
===Support Team===
The purpose of the Support team is to help the other three teams as requested. The primary focus is on providing support services to developers, in any component category.
The purpose of the Support team is to help the other three teams as requested. The primary focus is on providing support services to developers, in any component category.
The Support team will be formed by the Development Manager.
The Support team will be formed by the Development Manager.
==Development Manager (DM)==
===[http://wiki.contribs.org/SME_Server:Constitution:Development_Manager_Requirements#Development_Manager_.28DM.29 Development Manager (DM)]===
This person will lead the volunteers in the support team. The DM is primarily a facilitator. The DM is an elected post, elected by the entire community, with a term of one year. The duties include:
This person will lead the volunteers in the support team. The DM is primarily a facilitator. The DM is an elected post, elected by the entire community, with a term of one year. The duties include:
The Communications Manager (CM) will strive to support the efforts of all groups.
The Communications Manager (CM) will strive to support the efforts of all groups.
==SME Documentation Team==
===[[:SME_Server:Constitution:Communications_Manager_Requirements#SME_Documentation_Team|SME Documentation Team]]===
The SME Documentation Team is responsible for all the documentation for SME Server and add-ons. This documentation should be available online and as downloadable files. The types of documentation include:
The SME Documentation Team is responsible for all the documentation for SME Server and add-ons. This documentation should be available online and as downloadable files. The types of documentation include:
Any tools used for the purposes of SME Documentation are the responsibility of this team.
Any tools used for the purposes of SME Documentation are the responsibility of this team.
== SME Translations Team ==
=== [[:SME_Server:Constitution:Communications_Manager_Requirements#SME_Translations_Team|SME Translations Team]] ===
The SME Translations Team is responsible for making documentation available in all the languages for which there are sufficient interest and resources. The translations should be available online and as downloadable files. The primary sources for translations will be:
The SME Translations Team is responsible for making documentation available in all the languages for which there are sufficient interest and resources. The translations should be available online and as downloadable files. The primary sources for translations will be:
Any tools used for the purposes of translation are the responsibility of this team.
Any tools used for the purposes of translation are the responsibility of this team.
== Web Site Team ==
=== [[:SME_Server:Constitution:Communications_Manager_Requirements#Web_Site_Team|Web Site Team]] ===
The Web Site team is responsible for all the features and activities on the community website(s). This team is led by the Web Administrator, who shall have the ability to create roles in the team to carry out the duties of the post (monitor mailing lists, create sub webs, assist with contrib projects, etc.).
The Web Site team is responsible for all the features and activities on the community website(s). This team is led by the Web Administrator, who shall have the ability to create roles in the team to carry out the duties of the post (monitor mailing lists, create sub webs, assist with contrib projects, etc.).
To guard against accident, at least three people will have full administrative access to the entire web site. This number will include any server administrators at the hosting provider that have the ability to grant full administrative access to the web site. Only one of these people, the Web Administrator, or delegate(s), will actively administer the site at any one time.
To guard against accident, at least three people will have full administrative access to the entire web site. This number will include any server administrators at the hosting provider that have the ability to grant full administrative access to the web site. Only one of these people, the Web Administrator, or delegate(s), will actively administer the site at any one time.
==Org Support Team==
===[[:SME_Server:Constitution:Communications_Manager_Requirements#Org_Support_Team|Org Support Team]]===
The Org Support Team is responsible for any documents concerning the community. This is not intended to include SME documentation.
The Org Support Team is responsible for any documents concerning the community. This is not intended to include SME documentation.
All policies, procedures, guidance documents, etc., shall be available to the public.
All policies, procedures, guidance documents, etc., shall be available to the public.
==Communications Manager (CM)==
===[http://wiki.contribs.org/SME_Server:Constitution:Communications_Manager_Requirements#Communications_Manager_.28CM.29 Communications Manager (CM)]===
This person will lead the volunteers in the communications group. The duties of this office include:
This person will lead the volunteers in the communications group. The duties of this office include:
Four weeks notice is requested if an office holder must step down from his or her position. If more than half of the term remains to be filled, an election will be scheduled to fill the post if candidates can be found. Otherwise a caretaker will be appointed by the rest of the Leadership Committee.
Four weeks notice is requested if an office holder must step down from his or her position. If more than half of the term remains to be filled, an election will be scheduled to fill the post if candidates can be found. Otherwise a caretaker will be appointed by the rest of the Leadership Committee.
==Delegated Posts==
===Delegated Posts===
The terms for delegated posts (Release Leaders, Translations Managers, etc.) are at the discretion of the respective manager and may be altered by that manager's successor in office. Four weeks notice is requested if a delegated post holder must step down from their position.
The terms for delegated posts (Release Leaders, Translations Managers, etc.) are at the discretion of the respective manager and may be altered by that manager's successor in office. Four weeks notice is requested if a delegated post holder must step down from their position.