Skip to content

Latest commit

 

History

History
69 lines (35 loc) · 3.48 KB

README_en.md

File metadata and controls

69 lines (35 loc) · 3.48 KB

geOrchestra Improvement Proposals

Principles

One of the PSC roles is to make decisions regarding project management. This can include:

  • community animation
  • communication
  • modifications to the codebase having a significant impact on a large share of the community, or affecting backwards compatibility, or affecting compatibility with third party products
  • how contribution to the codebase works
  • how the PSC works

The PSC is made of individuals involved in the project. Those individuals don't represent their employer or any other entity. An odd amount of members facilitates the voting process.

Process

  1. Anyone can propose a GIP (GeOrchestra Improvement Proposal), be it as an individual or an entity. The GIP has to be redacted by filing an issue in this repository - in the author's native language - and posted on the community's mailing-list (georchestra at georchestra.org). When not in english, an english translation would be appreciated, otherwise the PSC will translate it to english.

  2. To make it easier to examinate and adopt the GIP, it is preferred that the GIP matches the following structure:

  • intended purpose
  • expected benefits for the community
  • how it will be implemented
  • potential risks, and ways to work around them

  1. Anyone is welcome to examine the GIP, ask questions, propose modifications on github or on the mailing list. The individual who proposed the GIP can account for those modifications by modifying the GIP in the issue tracker - This way modifications are tracked.

  2. When the individual thinks the GIP is ready for review, they ask the PSC to examine it. The PSC then announces on the community's mailing-list that a voting process has started.

  3. Every PSC member has 15 days (360 hours starting at the voting process announce) to vote. To do so, they comment on the issue tracker with:

  • +1 : the PSC member supports the GIP
  • +0 : mildly for, with positive support
  • 0 : neutral
  • -0 : mildly against, with negative support
  • -1 : against, with detailed motives

  1. A vote is definitive.

  2. At the end of the period, PSC members who havent voted automatically vote with a +0.

  3. If all the PSC members have voted, the voting period ends immediately.

  4. Every PSC member can ask for a 15 days extension period for the voting period, as long as the period isn't over. The voting period can only be extended once.

  5. Every PSC member that votes -1 against a GIP must publicly explain the reasons of his vote.

  6. If the GIP gets at least 30% of the PSC headcount +1 votes, and if it gets no -1, then the GIP is accepted. The complete voting process is archived on the issue tracker and stays public.

  7. If the GIP gets at least 30% +1 votes AND one or more -1, then it is pending.

  • Every PSC member having voted -1 must propose within two months an alternative making the GIP acceptable for them. The GIP's proponent is then free to modify his proposal then ask for a new voting process, starting anew, with a minor identification number.
  • If the PSC members having voted -1 don't propose an alternative making the GIP acceptable for them, then the GIP is accepted.

  1. No GIP breaking the manifesto can be accepted. If such a GIP is proposed, PSC members don't have to provide an alternative.

  2. A GIP can't be proposed more than three times. If the GIP is rejected three times, or if it isn't reproposed, then the GIP is refused.