You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
98 lines
8.8 KiB
98 lines
8.8 KiB
THIS IS A DRAFT, AND IS NOT IN EFFECT.
|
|
|
|
This document is the Lubuntu Constitution, which aims to define Lubuntu as a project, its community, and its governance. If something is not explicitly defined here, please refer to the [Ubuntu Code of Conduct](https://www.ubuntu.com/community/code-of-conduct). This document is not exhaustive or complete. It is not a rulebook; it serves to distil our common understanding of a collaborative, shared environment and goals. We expect it to be followed in spirit as much as in the letter.
|
|
|
|
# Definitions
|
|
|
|
Lubuntu refers to the free software distribution project (https://lubuntu.me).
|
|
|
|
Ubuntu refers to the free software distribution project (https://www.ubuntu.com/community/governance).
|
|
|
|
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC 2119](https://tools.ietf.org/html/rfc2119).
|
|
|
|
# The Community
|
|
|
|
The Lubuntu community is defined as the people, interactions, and accounts on the following platforms, as linked:
|
|
|
|
- [#lubuntu](irc://irc.freenode.net/lubuntu), [#lubuntu-devel](irc://irc.freenode.net/lubuntu-devel), and [#lubuntu-offtopic](irc://irc.freenode.net/lubuntu) on the freenode IRC network.
|
|
- The [User support](https://lists.ubuntu.com/mailman/listinfo/lubuntu-users) and [Development](https://lists.ubuntu.com/mailman/listinfo/lubuntu-devel) mailing lists on [lists.ubuntu.com](https://lists.ubuntu.com/).
|
|
- The [Support](https://telegram.lubuntu.me/support), [Development](https://telegram.lubuntu.me/development), [Offtopic](https://telegram.lubuntu.me/offtopic), and [Spanish](https://telegram.lubuntu.me/espa%C3%B1ol) channels on Telegram.
|
|
- [Lubuntu's Matrix channel](https://chat.disroot.org/#/room/#lubuntu:disroot.org).
|
|
- Our self-hosted [Phabricator instance](https://phab.lubuntu.me/).
|
|
- Lubuntu's [Twitter account](https://twitter.com/lubuntuofficial).
|
|
- Lubuntu's [Mastodon account](https://mastodon.technology/@lubuntu).
|
|
- [r/Lubuntu](https://www.reddit.com/r/Lubuntu) on Reddit.
|
|
- Posts and Disqus comments on [our official website](https://lubuntu.me/).
|
|
|
|
Discussion on these forums should aim to be constructive, collaborative, and inclusive. If there are disagreements or misunderstandings, the parties involved should aim to resolve them in a constructive way; if this is not possible, it should be raised to the appropriate administrators, and as a secondary avenue, the Lubuntu Council.
|
|
|
|
# Governance
|
|
|
|
Lubuntu is a meritocracy first and a democracy second. The individuals who contribute the most to the project as a whole, regardless of who they identify as culturally, should be given the most authority over how the project runs. Inversely, people who cease their contributions to the project need to gracefully step down if they can no longer handle their responsibilities as a contributor.
|
|
|
|
## Lubuntu Council
|
|
|
|
The Lubuntu Council is a board consisting of five individuals. The Council serves as the governing body of the Lubuntu project, and has the ability to do the following:
|
|
|
|
- Mediate disputes within the community (as defined above) that cannot be resolved by themselves, or cannot be resolved peacefully.
|
|
- Appoint team members to positions temporarily if a position being held becomes vacant, and until a new leader can be chosen.
|
|
- Delegate administration of community groups to individuals which report directly to the Lubuntu Council. These delegated administrators should be the clear leaders of these groups already, to keep the spirit of meritocracy.
|
|
- Grant Lubuntu Membership to individuals within the Lubuntu project who have made significant and sustained contributions.
|
|
|
|
Quorum of the Lubuntu Council is defined as half of the members plus one. No decision can be made on behalf of the Lubuntu Council without a quorum.
|
|
|
|
Although this is exercised with great care, the Lubuntu Council has the authority to remove people from the Lubuntu project, for clear violations of this constitution or the Ubuntu Code of Conduct that occur within the community. It is the duty of the Lubuntu Council to publicly announce removal of team members from the project, and any removal must be done only after a unanimous vote has passed.
|
|
|
|
The current members of the Lubuntu Council can be found under the [~lubuntu-council team](https://launchpad.net/~lubuntu-admins) on Launchpad.
|
|
|
|
The Lubuntu Council members' terms expire yearly, and only Lubuntu Members are eligible to run for a position on the Lubuntu Council. Active Lubuntu Members are eligible to vote, using the [Condorcet Internet Voting Service](https://civs.cs.cornell.edu/); the results of which are put into effect after being confirmed by the expiring Lubuntu Council.
|
|
|
|
## Lubuntu Members
|
|
|
|
Lubuntu Members are official members of the Lubuntu project. In order to be a Lubuntu member, an individual must demonstrate significant and sustained contributions to the Lubuntu project, and also must be confirmed by the Lubuntu Council.
|
|
|
|
Lubuntu Members are inherently [Ubuntu Members](https://wiki.ubuntu.com/Membership), and since the benefits of which are also granted, the same high expectations upheld for Ubuntu Members must also be upheld for Lubuntu Members.
|
|
|
|
A current list of Lubuntu Members can be found under the [~lubuntu-members team](https://launchpad.net/~lubuntu-members) on Launchpad.
|
|
|
|
## Role of the Ubuntu Community Council
|
|
|
|
The Ubuntu Community Council is the governing board of the Ubuntu project, and as Lubuntu is a sub-project of Ubuntu, the Ubuntu Community Council is a direct parent board of the Lubuntu Council. As a board they have one vote in decisions; however, any decision made by the Lubuntu Council can be overruled by the Ubuntu Community Council through a majority vote.
|
|
|
|
## Team Lead
|
|
|
|
The Lubuntu Team Lead is a Lubuntu Council-appointed individual which serves as a representative for the Lubuntu Council when executive action is required and the Lubuntu Council cannot reach a quorum. If the Team Lead takes any action, they must inform the Lubuntu Council within seven days, and the Council has the right to overrule any decision made by the Team Lead. Intentional failure to report any decision to the Council within that time will result in re-evaluation by the Council of the Team Lead's ability to serve.
|
|
|
|
The current Lubuntu Team Lead is Simon Quigley.
|
|
|
|
## Delegated Positions
|
|
|
|
The following are the current administrators who hold titles delegated by the Lubuntu Council. They have the ability to appoint assistants to their position which take their place in the case that they are no longer fit to fulfull their duties, either temporarily or permanently. Should a replacement be permanent, the Lubuntu Council must be informed. These delegated administrators and assistants should be the clear leaders of these groups already, to keep the spirit of meritocracy.
|
|
|
|
### Lubuntu Release Manager
|
|
|
|
The Lubuntu Release Manager is the individual responsible for all release management for the Lubuntu Product. They make the final decision as to what packages are in the Product (although this is subject to platform expectations set by the Ubuntu Technical Board), the release goals for the Product, and whether or not the Product is in a releaseable state. They serve as the point of contact for Product releases, and have the ability to establish release-related rules for Product-specific packages.
|
|
|
|
The current Lubuntu Release Manager is Simon Quigley, and the assistant is Walter Lapchynski.
|
|
|
|
### Lubuntu Quality Assurance Manager
|
|
|
|
The Lubuntu Quality Assurance Manager, or the Lubuntu QA Manager, is the individual responsible for testing the Lubuntu Product. They conduct exploratory testing, establish quality assurance and bug triage policies for the Product, and assist the Release Manager in finding testers for the Product prior to a release. They serve as the point of contact for bugs in Lubuntu, and work with the Lubuntu Release Manager to determine if the Product is in a releaseable state.
|
|
|
|
The current Lubuntu Quality Assurance Manager is Walter Lapchynski.
|
|
|
|
### Lubuntu Documentation Manager
|
|
|
|
The Lubuntu Documentation Manager is the individual responsible for all of Lubuntu's documentation. They make the final decisions for all of the content which goes into the Lubuntu Manual and any other documentation which is officially released on behalf of the project. They aim to gather relevant information from the community and transform it into something that is easy to read.
|
|
|
|
The current Lubuntu Documentation Manager is Lyn Perrine.
|
|
|
|
### Lubuntu Design Manager
|
|
|
|
The Lubuntu Design Manager is the individual responsible for design and user experience decisions in the Product. They aim to take feedback from the community and other team members regarding how to improve the design of the Product and what the best experience for the end user is.
|
|
|
|
The current Lubuntu Design Manager is Wendy Hill.
|
|
|
|
|
|
TODO: Separate out the Lubuntu Spanish Group.
|