Difference between revisions of "ReactOS Project Coordinator"
m (Formatting) |
BrentNewland (talk | contribs) (Categories) |
||
(One intermediate revision by one other user not shown) | |||
Line 1: | Line 1: | ||
− | == | + | == Assignee == |
− | [[Aleksey Bragin]] | + | Current: |
+ | * [[Aleksey Bragin]] | ||
+ | |||
+ | Previous: | ||
+ | * [[Jason Filby]] (1998-2005) | ||
+ | * [[Steven Edwards]] (2005-2006) | ||
+ | |||
+ | == Term == | ||
+ | |||
+ | One (1) year renewable. | ||
== Mandate == | == Mandate == | ||
Line 7: | Line 16: | ||
The Project Coordinator's (PC) job entails the following responsibilities: | The Project Coordinator's (PC) job entails the following responsibilities: | ||
* Mediate small disputes to remove the need to vote on every issue | * Mediate small disputes to remove the need to vote on every issue | ||
− | * Provide a contact point for | + | * Provide a contact point for Media and Third Party project relations |
* Provide quarterly status updates regarding all major activities of the project | * Provide quarterly status updates regarding all major activities of the project | ||
* Conduct regular meetings with the other Coordinators and developers in the ReactOS Project | * Conduct regular meetings with the other Coordinators and developers in the ReactOS Project | ||
− | |||
− | |||
− | |||
− | |||
== Details == | == Details == | ||
Line 21: | Line 26: | ||
The Coordinator is simply a figure head and does not have the power to dictate policy, if mediation cannot be reached on a conflicting issue then it is taken to a vote. No issue has to be brought to the Coordinator. All developers are free to start a vote without consulting the Coordinator. His role is an advisory one. | The Coordinator is simply a figure head and does not have the power to dictate policy, if mediation cannot be reached on a conflicting issue then it is taken to a vote. No issue has to be brought to the Coordinator. All developers are free to start a vote without consulting the Coordinator. His role is an advisory one. | ||
− | === Provide a contact point for | + | === Provide a contact point for Media and Third Party project relations === |
− | The Project Coordinator should advise and be advised of major news announcements and be free to provide interviews, and or conduct meetings on behalf of the project with any | + | The Project Coordinator should advise and be advised of major news announcements and be free to provide interviews, and or conduct meetings on behalf of the project with any third party such as other Free Software Projects, Businesses and Universities. |
The PC has the responsibility to keep track of these events and advise the community of new developments. | The PC has the responsibility to keep track of these events and advise the community of new developments. | ||
Line 30: | Line 35: | ||
=== Provide quarterly status updates regarding all major activities of the project === | === Provide quarterly status updates regarding all major activities of the project === | ||
− | The PC will provide reports as to the project status due on | + | The PC will provide reports as to the project status due on the first of January, April, July, and October. |
=== Conduct regular meetings with the other Coordinators and developers in the ReactOS Project === | === Conduct regular meetings with the other Coordinators and developers in the ReactOS Project === | ||
Line 39: | Line 44: | ||
{{Project positions}} | {{Project positions}} | ||
+ | [[Category:Community]] |
Revision as of 06:20, 2 March 2012
Contents
- 1 Assignee
- 2 Term
- 3 Mandate
- 4 Details
- 4.1 Mediate Small disputes to remove the need to vote on every issue
- 4.2 Provide a contact point for Media and Third Party project relations
- 4.3 Provide quarterly status updates regarding all major activities of the project
- 4.4 Conduct regular meetings with the other Coordinators and developers in the ReactOS Project
Assignee
Current:
Previous:
- Jason Filby (1998-2005)
- Steven Edwards (2005-2006)
Term
One (1) year renewable.
Mandate
The Project Coordinator's (PC) job entails the following responsibilities:
- Mediate small disputes to remove the need to vote on every issue
- Provide a contact point for Media and Third Party project relations
- Provide quarterly status updates regarding all major activities of the project
- Conduct regular meetings with the other Coordinators and developers in the ReactOS Project
Details
Mediate Small disputes to remove the need to vote on every issue
The Coordinator is simply a figure head and does not have the power to dictate policy, if mediation cannot be reached on a conflicting issue then it is taken to a vote. No issue has to be brought to the Coordinator. All developers are free to start a vote without consulting the Coordinator. His role is an advisory one.
Provide a contact point for Media and Third Party project relations
The Project Coordinator should advise and be advised of major news announcements and be free to provide interviews, and or conduct meetings on behalf of the project with any third party such as other Free Software Projects, Businesses and Universities. The PC has the responsibility to keep track of these events and advise the community of new developments.
All developers have the freedom to grant interviews, establish relationships with other projects and organizations.
Provide quarterly status updates regarding all major activities of the project
The PC will provide reports as to the project status due on the first of January, April, July, and October.
Conduct regular meetings with the other Coordinators and developers in the ReactOS Project
The PC will make a good faith effort to meet monthly via IRC, email exchange or VoIP with the various team coordinators to discuss any issues they feel may need to be addressed. The PC will also be obliged to be upon request conduct meetings with any other Coordinator or developer to address any issue.
For developers that are limited in Internet Access the PC will make a good faith effort to keep in touch with those developers on a limited basis and seek out and address their development needs and goals.
Project Coordinator: Aleksey Bragin | JIRA Maintainer: Amine Khaldi and Pierre Schweitzer | Release Engineers: Joachim Henze, Colin Finck and Ziliang Guo | Website Coordinators: Colin Finck, Ziliang Guo, Pierre Schweitzer et al.