YunoHost/doc
1
0
Fork 0
mirror of https://github.com/YunoHost/doc.git synced 2024-09-03 20:06:26 +02:00
Code Issues Projects Releases Packages Wiki Activity

[fix] surplus word. fix group name.

Browse source
This commit is contained in:
Moul 2017-02-02 08:05:28 +01:00
parent bc78c03aaf
commit dab0e989bc
1 changed files with 2 additions and 2 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
yunohost_project_organization.md
View file

@ -27,7 +27,7 @@ Historically, the project has been very close to initiatives which aim at creati
### A theme-based, open structure
The objective of the the YunoHost organisation is to allow the largest number of people to contribute to software improvement, whether from a technical point of view (development, application packaging) or otherwise (communication, end-user assistance, documentation, etc.). Inspired by the projects which were reviewed at a recent event (Kodi, Debian, Django, Fedora, Wikipedia, etc.) and by ideas stemming from YunoHost contributors (Jérôme, Bram, opi, scith, ju), a decision was made to organise work by special interest groups, federated thanks to a board to key contributors.
The objective of the YunoHost organisation is to allow the largest number of people to contribute to software improvement, whether from a technical point of view (development, application packaging) or otherwise (communication, end-user assistance, documentation, etc.). Inspired by the projects which were reviewed at a recent event (Kodi, Debian, Django, Fedora, Wikipedia, etc.) and by ideas stemming from YunoHost contributors (Jérôme, Bram, opi, scith, ju), a decision was made to organise work by special interest groups, federated thanks to a board to key contributors.
YunoHost project organisation schema
@ -96,7 +96,7 @@ To be a member of the Board does not imply that you have access to all resources
Decisions to be taken can be of 2 kinds:
1. for a group (for example, "to merge a PR" would be assumed by the Apps Group whereas to "post a tweet" would fall under the responsibility of the Communication Group)
1. for a group (for example, "to merge a PR" would be assumed by the Dev Group whereas to "post a tweet" would fall under the responsibility of the Communication Group)
2. for the overall project (for instance, to decide on a release with new features)
If a consensus is not reached over a decision within a particular group, they must refer to the Board for further discussions. If no consensus has been reached, the proposal will be submitted to a vote by all contributors.