aboutsummaryrefslogtreecommitdiffstats
path: root/modules
Commit message (Collapse)AuthorAgeFilesLines
* Update introduction titleHEADmasterChloe Kudryavtsev2019-05-261-1/+1
|
* Rename to "governance"Chloe Kudryavtsev2019-05-263-4/+6
|
* fix(teams): Remove consecutive term restrictionChloe Kudryavtsev2019-04-111-1/+0
| | | | | Note: further conversation needs to happen regarding possible alternate ways to handle the issues it was intended to address.
* fix(teams): Do not claim base owns the projectChloe Kudryavtsev2019-04-111-1/+1
|
* fix(teams): h2 Team Structure got lost; relocateChloe Kudryavtsev2019-04-091-2/+2
|
* Rework the base team descriptionDrew DeVault2019-04-091-16/+12
| | | | | | It's important to firmly establish the authority of the base team. The guiding principles to which the base team holds itself are out-of-scope for this document and better served elsewhere.
* Move team structure before team administrationDrew DeVault2019-04-091-33/+33
| | | | | You have to establish what the teams are before you can establish how they are maintained
* feat(Teams): Remove extranious policiesChloe Kudryavtsev2019-04-061-22/+0
| | | | | They don't need to be here for bootstrapping and can be added as Base team's policies (and thus applying to everyone).
* fix(voting): Fix moved cross-refsChloe Kudryavtsev2019-04-041-2/+2
|
* goals: apply suggestion regarding community goalChloe Kudryavtsev2019-04-041-1/+1
|
* [intro] Apply ddevault's principle rewordingChloe Kudryavtsev2019-03-281-4/+4
|
* [intro] Initial draft of goals and principlesChloe Kudryavtsev2019-03-281-0/+10
|
* [policy] Base can settle issues outrightChloe Kudryavtsev2019-03-281-0/+2
|
* [teams] Move into its own moduleChloe Kudryavtsev2019-03-283-1/+1
| | | | This also makes making team-specific pages easier
* [teams] Remove all teams except BaseChloe Kudryavtsev2019-03-281-76/+1
| | | | Faster bootstrap, easier to move to per-team pages later
* [policy] Remove extranious policiesChloe Kudryavtsev2019-03-283-24/+0
| | | | | They can be re-added later if needed, and arguably should be in per-team pages.
* [policy] Fix typo: condorset -> condorcetChloe Kudryavtsev2019-03-271-1/+1
|
* [teams] Avoid another forward referenceChloe Kudryavtsev2019-03-261-1/+1
| | | | This time, developer def is moved after member def.
* [teams] Move members above admins in glossaryChloe Kudryavtsev2019-03-261-1/+1
| | | | Avoids an unnecessary forward reference.
* [teams] Re-add minimum admin count, add maxChloe Kudryavtsev2019-03-261-0/+1
|
* [policy] Add a way to skip the 3 extra votesChloe Kudryavtsev2019-03-261-0/+2
| | | | | In some cases, it may be obvious that a project-wide vote is needed. Make that possible to acheive faster.
* [policy] Handle multiple-answer votesChloe Kudryavtsev2019-03-261-0/+2
|
* [teams] Base have term limits and are voted onChloe Kudryavtsev2019-03-261-0/+4
|
* [policy] Add project-wide voting as a fallbackChloe Kudryavtsev2019-03-261-6/+22
|
* [teams] Update based on new policies/discussionChloe Kudryavtsev2019-03-261-29/+30
| | | | | | | 1. Voting, conflicts, etc are not mentioned elsewhere. 2. Rename Core -> Packaging 3. Rename Packaging -> Packaging: Community 4. Add "Base" as an administrative team
* [policy] Fix formatting error (h1\n)Chloe Kudryavtsev2019-03-263-0/+3
| | | | You need an extra space between h1 and content
* [policy] Add tabs vs spaces policyChloe Kudryavtsev2019-03-262-0/+9
|
* [policies] Draft initial conflict resolutionChloe Kudryavtsev2019-03-261-0/+12
|
* [policy] How to update policies and others?Chloe Kudryavtsev2019-03-261-0/+12
|
* [policy] Draft initial voting policyChloe Kudryavtsev2019-03-261-0/+23
|
* [policies] Initial structureChloe Kudryavtsev2019-03-264-0/+5
|
* [teams] Expand member expectationsChloe Kudryavtsev2019-03-261-0/+1
| | | | They should also follow policies and the CoC.
* [nav] Rename Organization to Structure here tooChloe Kudryavtsev2019-03-261-1/+1
|
* [teams] Rename Organization -> StructureChloe Kudryavtsev2019-03-261-1/+1
| | | | This way policies can go into a separate section.
* [nav] Switch from single-pageChloe Kudryavtsev2019-03-263-190/+196
| | | | Still stay in single-module.
* [teams] Add kunkku to the infra teamChloe Kudryavtsev2019-03-251-0/+1
|
* [teams] Add removal timeout sectionChloe Kudryavtsev2019-03-251-0/+8
|
* [teams] Change packaging to handle all of aportsChloe Kudryavtsev2019-03-251-1/+1
|
* [teams] Add a BIG warning about team specificityChloe Kudryavtsev2019-03-251-0/+9
|
* [teams] `link:` is not required for `mailto:`Chloe Kudryavtsev2019-03-251-1/+1
|
* [teams] Core is a subset of packagingChloe Kudryavtsev2019-03-251-0/+2
| | | | Temporary note as we figure this distinction out
* [teams] Update core teamChloe Kudryavtsev2019-03-251-1/+3
| | | | | Using data from gitolite. Also update rdutra's email (he has an @a.o one now).
* [teams] Add project-specific resource sectionChloe Kudryavtsev2019-03-251-0/+14
| | | | Focused mostly on emails, but open for other such things.
* [teams] Rewrite half the pageChloe Kudryavtsev2019-03-201-17/+58
| | | | | | | | | | | | | Lots of things could be worded better. Further, a few specific things came up: - how do members get removed, specifically? - how do leads get removed, specifically? - the "lead" terminology confused many people, making them think it is more than it is. tentatively rename the position to "admin" - what is expected of members and leads? - what's a "developer"? This attempts to address all of the above.
* Reorganize glossaryChloe Kudryavtsev2019-03-201-1/+2
|
* [teams] Correct clandmeter's emailChloe Kudryavtsev2019-03-181-2/+2
|
* [teams] Add clandmeter to CoreChloe Kudryavtsev2019-03-181-10/+11
|
* [typo] Fix leitao's emailChloe Kudryavtsev2019-03-181-1/+1
|
* [content] Teams and OrganizationChloe Kudryavtsev2019-03-172-0/+112
Also initialize ROOT, navigation and make it the index (temporarily).