From fc156840978ecda41e908db624eadcbc46bd28b3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Antoine=20Beaupr=C3=A9?= <anarcat@debian.org> Date: Mon, 11 Nov 2024 14:20:29 -0500 Subject: [PATCH] fix markdownlint issues in tpa-rfc-73 --- policy/tpa-rfc-66-gitlab-ultimate-program.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/policy/tpa-rfc-66-gitlab-ultimate-program.md b/policy/tpa-rfc-66-gitlab-ultimate-program.md index 2e447519..3cdda4f7 100644 --- a/policy/tpa-rfc-66-gitlab-ultimate-program.md +++ b/policy/tpa-rfc-66-gitlab-ultimate-program.md @@ -90,6 +90,7 @@ request, and only GitLab administrators can manage server-side hooks. **Definition**: In Gitlab we have roles with different permissions. When the user is added to the project or group they need to have a specific role assigned. The role defines which actions they can take in that Gitlab project or group. Right now we have the following roles: + - guest - reporter - developer @@ -141,7 +142,7 @@ the different tasks that need to happen in the project and all of them will be part of the different epics in the ‘Arti relays’ project. The milestones will be used for planning specific releases. -**Difference between Epics and Milestones** +#### Difference between Epics and Milestones Milestones are better suited for planning release timelines and tracking specific features, allowing teams to focus on deadlines and delivery goals. @@ -188,13 +189,13 @@ period of time. For example they could be used for sprints for specific projects **What problem we are solving**: Represent and track in Gitlab the iterations we are having in different projects. -**Difference between Epics and Iterations** +#### Difference between Epics and Iterations While Epics group related issues to track high-level goals over multiple milestones, Iterations focus on a set timeframe (e.g., two-week sprints) for completing specific tasks within a project. Iterations help teams stay on pace by emphasizing regular progress toward smaller, achievable goals, rather than focusing solely on broad outcomes as Epics do. Using iterations enables GitLab to mirror Agile sprint cycles directly, adding a cadence to project tracking that can improve accountability and deliverable predictability. -**Proposal**: +#### Proposal For projects, we will start planning and tracking issues on iterations if we get all tickets estimated. @@ -361,7 +362,6 @@ With Gitlab Ultimate they: - track progress of projects in a more efficient way - ### Community contributor to Tor Volunteers want to: @@ -384,7 +384,6 @@ Anonymous volunteers want to: There will be no change on how they use Gitlab. - #### Sysadmins at the Tor project (TPA) Sysadmins will start managing non-free software after we migrate to Gitlab Ultimate. @@ -530,4 +529,4 @@ GitLab hopes to strengthen the open source ecosystem. It is by invitation only. Gitlab team members can nominate projects as partners by [opening an issue in the open source partners program][]. -[opening an issue in the open source partners program]: https://gitlab.com/groups/gitlab-com/marketing/developer-relations/open-source-program/gitlab-open-source-partners/-/issues \ No newline at end of file +[opening an issue in the open source partners program]: https://gitlab.com/groups/gitlab-com/marketing/developer-relations/open-source-program/gitlab-open-source-partners/-/issues -- GitLab