Commit 91230c29 authored by Vasilis Tsiligiannis's avatar Vasilis Tsiligiannis
Browse files

Improve documentation formatting consistency


Signed-off-by: Vasilis Tsiligiannis's avatarVasilis Tsiligiannis <acinonyx@openwrt.gr>
parent a9052391
====================================
Libre Space Foundation documentation
====================================
Intro
-----
Welcome to Libre Space Foundation documentation.
......
......@@ -21,4 +21,4 @@ As the highest leadership body of the Foundation and to satisfy its fiduciary du
Joining
-------
A new member joining the board requires an existing board member nomination and a unanimous decision among the current board members.
\ No newline at end of file
A new member joining the board requires an existing board member nomination and a unanimous decision among the current board members.
......@@ -22,6 +22,7 @@ Joining
Joining the "Core Contributors" group requires a nomination by an existing member and approval by the LSF board.
Onboarding
----------
......
======
People
========
======
Overview
--------
......
========
Projects
########
========
.. toctree::
:maxdepth: 2
......
......@@ -20,6 +20,7 @@ This document provides a simple list of the LSF's expectations of any Libre Spac
Ultimately, Libre Space projects report to, and are responsible to, the Libre Space Foundation Board, which mandates these policies for the LSF as a whole.
Governance
**********
......
......@@ -31,7 +31,7 @@ So, all issues created shall involve a task or be expressed as tasks.
Open column
~~~~~~~~~~~~~~
^^^^^^^^^^^
Once an issue is created, it goes in the Open column as a new card.
Cards which remain in this column shall always be unassigned.
......@@ -40,7 +40,7 @@ No GitLab label shall be used for this column
To Do column
~~~~~~~~~~~~
^^^^^^^^^^^^
The backlog can grow quite large but the team has a maximum working capacity.
The 'To Do' column is used to limit the pending work which can be overwhelming for the team.
......@@ -50,9 +50,9 @@ Cards which remain in To Do state shall always be unassigned.
The idea with this column is that people can have a quick visual indication on which pending issues to focus on.
The set of issues in ready state shall be selected based on:
1. How ready are the issues to be worked on
2. If they all deliver a working feature
3. The future working capacity of the team.
#. How ready are the issues to be worked on
#. If they all deliver a working feature
#. The future working capacity of the team.
The number of issues in this column shall be kept low and not more than the team can handle.
A GitLab label shall be created for this column.
......@@ -60,13 +60,13 @@ The label shall have ``#F0AD4E`` as a background colour.
Doing column
~~~~~~~~~~~~~~
^^^^^^^^^^^^
People can assign themselves issues using this column.
This shall be done by:
1. Pulling the card from 'To Do' to 'Doing' column and
2. Assigning the card to themselves.
#. Pulling the card from 'To Do' to 'Doing' column and
#. Assigning the card to themselves.
Cards which remain in doing state shall always be assigned.
The idea with this column is that people can have a quick visual indication on which issues are worked on.
......@@ -76,7 +76,7 @@ The label shall have ``#5CB85C`` as a background colour.
Done column
~~~~~~~~~~~
^^^^^^^^^^^
Done column is optional.
If used, completed tasks shall be moved in this column.
......@@ -88,7 +88,7 @@ The label shall have ``#428BCA`` as a background colour.
Closed column
~~~~~~~~~~~~~
^^^^^^^^^^^^^
The Closed column is used for:
......@@ -109,19 +109,19 @@ The meeting shall result a concrete action plan towards improvement.
Rules
~~~~~
^^^^^
The retrospective meeting shall follow these rules:
1. A retrospective meeting shall be held once a month
2. A positive environment shall be created
3. The meeting shall focus on continuous improvement
4. Blaming people must be avoided
5. All opinions shall be listened
#. A retrospective meeting shall be held once a month
#. A positive environment shall be created
#. The meeting shall focus on continuous improvement
#. Blaming people must be avoided
#. All opinions shall be listened
Process
~~~~~~~
^^^^^^^
The retrospective is a regular meeting.
The meeting shall be scheduled when most people can attend, taking into account the distribution of people across different timezones.
......
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment