Commit 78377cdc authored by intrigeri's avatar intrigeri

GitLab: adjust links to Redmine custom queries

parent 15b3f9bc
......@@ -8,7 +8,8 @@ Git or the command line.
This is the technical design documentation of our new setup.
It is by no means perfect. We track known issues via
[tickets on Redmine](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=321).
[[!tails_gitlab groups/tails/-/issues?label_name%5B%5D=C%3ATranslation+Platform
desc="issues on GitLab"]].
[[!toc levels=2]]
......
......@@ -64,8 +64,8 @@ and it has the *Code* Type of work, then you can probably
safely skip to the next section.
So you want to contribute code to Tails but do not know where to
start? Our coding [TODO
list](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=119)
start? Our coding
[[!tails_gitlab groups/tails/-/issues?label_name%5B%5D=T%3ACode desc="TODO list"]]
is huge and frightening, but...
*Do not panic!*
......@@ -84,10 +84,9 @@ Let's see how we can help you picking up a task. A few tips:
language|contribute#mentors]].
On the one hand, you may want to **start doing practical stuff
immediately**. In this case, see [list the tasks that have the `Code`
*Type of
work*](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=119)
set. You probably want to start looking
immediately**. In this case, see the
[[!tails_gitlab groups/tails/-/issues?label_name%5B%5D=T%3ACode desc="list of tasks that have the `T:Code` label"]].
You probably want to start looking
at the few ones that are also in the [[!tails_gitlab_starter]]
first so that you can gain confidence and we can smoothly learn to
work together.
......
......@@ -18,8 +18,8 @@ relationship with Debian.
* Work on the [[Debian bugs that affect
Tails|contribute/relationship_with_upstream#debian-bts]].
* Work on our [tickets about Debian
work](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=138).
* Work on our [[!tails_gitlab groups/tails/-/issues?label_name%5B%5D=T%3ADebian
desc="issues about Debian work"]].
* Help maintain backports:
- look for "jessie-backports" on [[!tails_gitweb config/chroot_apt/preferences]]
- Xorg stack (at least the foundations and the major drivers)
......
......@@ -22,17 +22,17 @@ translations that were made of the previous version.
But there are still many ways you can start contributing:
- We maintain a list of [documentation
tasks](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=330).
- We maintain a list of
[[!tails_gitlab groups/tails/-/issues?label_name%5B%5D=T%3AEnd-user+documentation
desc="documentation tasks"]].
You can start writing a draft in the corresponding ticket and then
[[ask us for review|contribute/merge_policy]].
- Small fixes and enhancements to the current documentation are
greatly welcome. This can be done by sending Git patches to
[[tails-dev@boum.org|about/contact#tails-dev]] or by publishing a
[[Git]] branch (for example to a fork on
[[!tails_gitweb_repo tails/tails desc="our GitLab"]]. In general,
documentation changes should be based on the `master` branch.
[[tails-dev@boum.org|about/contact#tails-dev]] or by sending
us a [[Merge Request|contribute/merge_policy#submit]].
In general, documentation changes should be based on the `master` branch.
We recommend you to [[build an offline version of the
documentation|contribute/build/website]] to test your contributions
......
......@@ -10,9 +10,9 @@
- [[!tails_gitlab tails/tails/-/blob/testing/debian/changelog]]
- If the changelog of the final release has not been written
yet, either book some time to update the release notes on the
day of the release or go through the tickets:
- marked as "Needs Validation" on Redmine
- [fixed for the upcoming release](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=327)
day of the release or go through:
- the [[!tails_gitlab tails/tails/-/merge_requests desc="Merge Requests (MRs)"]]
- the issues [[!tails_gitlab tails/tails/-/milestones desc="fixed for the upcoming release"]]
- If a release candidate was announced, read the call for testing
- Analyze the diff of packages
- in testing for a major release: `wget http://nightly.tails.boum.org/build_Tails_ISO_testing/lastSuccessful/archive/latest.packages`
......
......@@ -7,18 +7,19 @@ You can improve how Tails looks, and make it easier to [[promote]].
Known tasks
===========
The tasks marked as [graphic
design](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=124) in
Redmine correspond to things that would benefit from the work of graphic
The issues with the
[[!tails_gitlab groups/tails/-/issues?label_name%5B%5D=T%3AGraphics desc="`T:Graphics` label"]]
in GitLab correspond to things that would benefit from the work of graphic
designers.
Other ideas
===========
If you are a graphic designer, you can surely find other ideas to improve Tails!
Even if you don't implement your suggestions yourself, [create
tickets](https://redmine.tails.boum.org/code/projects/tails/issues/new) with your ideas
so that others can benefit from your insight.
Even if you don't implement your suggestions yourself, [[!tails_gitlab
tails/tails/-/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=
desc="create issues"]]
with your ideas so that others can benefit from your insight.
Talk to us
==========
......
......@@ -30,9 +30,10 @@ for advice or review of your material.
# Specific tasks
See the [tasks about promoting
Tails](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=139)
on Redmine.
See the [[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=T%3APromote
desc="tasks about promoting Tails"]]
on GitLab.
# Advertising material
......
......@@ -42,16 +42,18 @@ ready to learn whatever you need to know :)</li>
# How to choose a task
We use Redmine to manage our list of tasks:
We use GitLab to manage our list of tasks:
* [tasks that require *Sysadmin*
work](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=113)
* [tasks that belong to the *Infrastructure*
category](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=140)
* [[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=T%3ASysadmin
desc="tasks that require *Sysadmin* work"]]
* [[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=C%3AInfrastructure
desc="tasks that belong to the *Infrastructure* category"]]
Here are a few tips to pick a task:
* Focus on the issues marked as *[[Starter|starter_tasks]]* on Redmine.
* Focus on the issues marked as *[[Starter|starter_tasks]]* on GitLab.
* Choose something that matters for you.
* Choose something where your singular skills are put to work.
......@@ -72,7 +74,7 @@ contribute usefully without having an account on the actual systems.
## If you don't know Puppet
A few tasks in Redmine can be fulfilled by testing something, and then
A few issues in GitLab can be fulfilled by testing something, and then
reporting your results on the relevant ticket.
However, most tasks are a bit more complicated. Follow these steps to
......
......@@ -7,18 +7,22 @@ You can improve the Tails user interface and user experience.
Known tasks
===========
The tasks marked as [user interface
design](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=123) in
Redmine correspond to things that we would like to see improved in the Tails
The issues labeled
[[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=T%3AUser+interface+design
desc="`T:User interface design`"]]
on GitLab correspond to things that we would like to see improved in the Tails
user interface.
Other ideas
===========
If you are a UI or HCI person, you can surely find other ideas to improve Tails!
Even if you don't implement your suggestions yourself, [create
tickets](https://redmine.tails.boum.org/code/projects/tails/issues/new) with your ideas
so that others can benefit from your insight.
Even if you don't implement your suggestions yourself,
[[!tails_gitlab
tails/tails/-/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=
desc="create issues"]]
with your ideas so that others can benefit from your insight.
Relate pages
============
......
......@@ -11,18 +11,20 @@
# Known tasks
We have identified some things that we would like to see improved on
our website: see the [website-related
tasks](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=115)
on Redmine.
our website: see the [[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=T%3AWebsite
desc="website-related issues"]]
on GitLab.
# Other ideas
Nevertheless, if you are a web or graphics person, you can surely
find other ideas to improve the Tails website! Even if you don't plan
to implement every suggested enhancement yourself, it may be worth
[creating
tickets](https://redmine.tails.boum.org/code/projects/tails/issues/new) with
your ideas so that others can benefit from your insight.
[[!tails_gitlab
tails/tails/-/issues/new?issue%5Bassignee_id%5D=&issue%5Bmilestone_id%5D=
desc="creating issues"]]
with your ideas so that others can benefit from your insight.
# Working on the website
......
......@@ -371,7 +371,7 @@ Then, gather other useful information from:
- new upstream releases of applications mentioned in [[doc/about/features]]
- new upstream releases of other important components such as the
Linux kernel
* the [*Completed for the next release*](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=327) Redmine view.
* the [[!tails_gitlab tails/tails/-/milestones desc="GitLab milestone"]].
Finally, sanity check the version and commit:
......@@ -1558,10 +1558,6 @@ Bug tracker
Skip this part if preparing a release candidate.
Edit the [*Completed for the next
release*](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=327)
Redmine view: set the _Target version_ filter to the next scheduled release.
Postpone to next release any remaining open issue for the version
you've just released. Use the right-click contextual menu to do so in
one single batch.
......@@ -1760,7 +1756,6 @@ this, and skip what does not make sense for a RC.
<https://jenkins.tails.boum.org/>.
1. Make sure you pushed all changes in every of our Git repo (including our
Debian packages ones).
1. Delete the _Release Manager View for ${VERSION_:?}_ Redmine custom query.
1. Ensure the next two releases have their own _Release Manager View_.
1. On the [[!tails_roadmap]], update the *Due date* for the *Holes
in the Roof* so that this section appears after the next release.
......
......@@ -3,10 +3,9 @@
Plans for the next releases
===========================
You can track on Redmine the list of tickets that we want to solve for
the next releases:
<https://redmine.tails.boum.org/code/projects/tails/roadmap>
You can track on
[[!tails_gitlab tails/tails/-/milestones desc="GitLab milestones"]]
the list of tickets that we want to solve for the next releases.
Priorities for the next years
=============================
......@@ -55,7 +54,8 @@ Priorities for the next years
### Sustainability of core code
- <strike>**Release Tails 4.0 based on Debian Buster** ([[Version 4.0|news/version_4.0]])</strike> [DONE]
- **Solve important usability issues** in our core applications ([[!tails_ticket 14544]])
- **Solve important usability issues** in our core applications
([[!tails_gitlab tails/tails/-/issues?scope=all&utf8=✓&state=opened&label_name[]=UX%3Acandidate]])
- **Port complex shell scripts to Python** ([[!tails_ticket 11198]], [[Blueprint|blueprint/Port_shell_scripts_to_Python]])
- **Migrate from `aufs` to `overlayfs`** ([[!tails_ticket 8415]])
- **Have more robust time synchronization** when starting Tails ([[!tails_ticket 5774]], [[Blueprint|blueprint/robust_time_syncing]])
......
......@@ -4,16 +4,18 @@ The tasks marked as *Starter* in our bug tracker have been identified as good
starting points for new contributors. They cover all kinds of work: testing,
design, writing, coding, etc.
[*Starter* tasks ordered by type of work](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=112)
[[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=Starter
desc="*Starter* tasks"]]
The description of the task should provide enough useful information to help you
complete it. Otherwise, don't hesitate to [[ask us on tails-dev@boum.org|about/contact#tails-dev]] for
clarification.
You can also have a look at other tasks marked as [low
priority](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=131) in
our bug tracker. We marked them as of low priority according to our
[roadmap]((https://redmine.tails.boum.org/code/projects/tails/roadmap) but they might
You can also have a look at other tasks marked as
[[!tails_gitlab groups/tails/-/issues?label_name%5B%5D=P%3ALow
desc="low priority"]] on our GitLab.
We marked them as of low priority according to our [[!tails_roadmap]] but they might
be interesting, useful and fun to work on!
Recommendations
......
......@@ -51,16 +51,11 @@ The Tails Foundations Team is responsible for:
- An emergency release is often needed shortly after [[!wikipedia Pwn2Own]].
* reviewing'n'merging proposed branches in a timely manner (1 week in
general, up to 2 weeks if needed in exceptional cases). If an issue
is labeled *3. Needs Validation*, but nobody on the Foundations Team can
take care of the review'n'merge, it's the Foundations Team's
responsibility to ask for help. These issues can be tracked using:
- the
[Needs Validation, with no assignee](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=194)
view;
- [Needs Validation](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=117);
* reviewing
[[!tails_gitlab groups/tails/-/merge_requests desc="Merge Requests (MRs)"]]
in a timely manner (1 week in general, up to 2 weeks if needed in exceptional
cases). If nobody on the Foundations Team can take care of a given MR,
it's the Foundations Team's responsibility to ask for help;
* deal with last minute emergency fixes needed during release process,
e.g. [[!tails_ticket 14962]];
......@@ -115,9 +110,10 @@ meetings, please send the team before the meeting:
# Tasks management
This section documents the principles and guidelines we use for
tracking [our
tasks](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=307).
This section documents the principles and guidelines we use for tracking
[[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=Core+Work%3AFoundations+Team
desc="our tasks"]].
This applies on top of the broader Tails project's tasks management
guidelines:
......@@ -134,8 +130,10 @@ The Foundation Team treats the _Milestone_ field as a commitment.
Other Tails teams, contributors, and users should be able to rely on
the value of this field.
An issue [owned by the Foundations
Team](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=307)
An issue
[[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=Core+Work%3AFoundations+Team
desc="owned by the Foundations Team"]]
should have the _Target version_ field set if, and only if, at least
one of these conditions is met:
......@@ -169,14 +167,17 @@ See [[contribute/working_together/GitLab#assignee]].
## UX improvements
Our [[UX designers|roles/ux]] maintain a list of UX improvements that
would be welcome, as issues related to [[!tails_ticket 14544]].
Our [[UX designers|roles/ux]] maintain a
[[!tails_gitlab groups/tails/-/issues?scope=all&utf8=✓&state=opened&label_name[]=UX%3Acandidate
desc="list of UX improvements"]] that would be welcome,
using the "UX:candidate" label.
From time to time, some Foundations Team members meet with UX
designers and do a value/cost analysis of these issues. Then, those
with the best value/cost, that we can work on without waiting for lots
of UX design work to be done, are added to [our list of
tasks](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=332).
of UX design work to be done, are added to
[[!tails_gitlab groups/tails/-/issues?scope=all&utf8=✓&state=opened&label_name[]=Core%20Work%3AFoundations%20Team&label_name[]=UX%3Acandidate
desc="our list of tasks"]].
That is, working on them automatically qualifies as Foundations Team work.
In general, before looking for other UX improvements we could work on,
......@@ -184,17 +185,22 @@ we should first focus on these selected issues and on the most
important or urgent of our other [[duties|foundations_team#duties]].
Still, while keeping this in mind, you might personally be
particularly interested in working on an issue related to
[[!tails_ticket 14544]], that was not added to our plate yet.
particularly interested in working on an issue that has the "UX:candidate" label,
but that was not added to our plate yet.
It is an option to turn one such issue into Foundations Team work,
provided a few conditions are met.
The Foundations Team lead maintains a list of issues that meet
these conditions, in the description of [[!tails_ticket 14544]].
these conditions:
- [[!tails_ticket 6084]]
- [[!tails_ticket 8061]]
- [[!tails_ticket 15028]]
You can check yourself if a particular issue meets all these
conditions:
- It was marked as related to [[!tails_ticket 14544]] by our UX designers.
- Our UX designers added the `UX:candidate` label.
- It is possible work on it without waiting for lots of UX work to be done first.
To determine whether that's the case:
......
......@@ -115,18 +115,23 @@ Tails system administrators have write access to the puppetmasters, and can log
the hosts.
They read the <tails-sysadmins@boum.org> encrypted mailing list.
We use [[!tails_gitlab desc="GitLab"]] tickets for public discussion
We use [[!tails_gitlab desc="GitLab"]] issues for public discussion
and tasks management:
* To bring a ticket to the attention of system administrators,
assign it to the _Sysadmins_ group. You'll find it at the end
of the list of possible assignees.
* [tickets that should be taken care of as part of sysadmin shifts](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=262)
* [tickets that are on the sysadmin team's roadmap](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=267)
* [tasks requiring *Sysadmin*
work](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=113)
* [tasks belonging to the *Infrastructure*
category](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=140)
* To bring an issue to the attention of system administrators,
mention the `@sysadmins-team` group.
* [[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=Core+Work%3ASysadmin+%28maintenance%29
desc="issues that should be taken care of as part of sysadmin shifts"]]
* [[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=Core+Work%3ASysadmin+%28adapt%29
desc="issues that are on the sysadmin team's roadmap"]]
* [[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=T%3ASysadmin
desc="tasks that require *Sysadmin* work"]]
* [[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=C%3AInfrastructure
desc="tasks that belong to the *Infrastructure* category"]]
<a id="services"></a>
......
......@@ -41,6 +41,8 @@ As general guidelines we should give priority to:
- Tasks that impact users the most or that impact the largest number of users.
- Tasks that have the highest impact on sustainability.
These tasks are tracked using the [Core work: Technical
writing](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=243)
view on Redmine.
These tasks are tracked using the
[[!tails_gitlab
groups/tails/-/issues?label_name%5B%5D=Core+Work%3ATechnical+writing
desc="Core work: Technical writing"]]
label on GitLab.
......@@ -17,7 +17,9 @@ Check if the bug is already known
Have a look at:
- the [[list of known issues|support/known_issues]]
- the [list of things that will be fixed or improved in the next release](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=327)
- the
[[!tails_gitlab tails/tails/-/milestones
desc="list of things that will be fixed or improved in the next release"]]
<a id="useful_bug_report"></a>
......
......@@ -44,7 +44,9 @@ waiting to be implemented: browser extensions,
[[!tails_ticket 7246 desc="default sound card"]],
[[!tails_ticket 5979 desc="mouse and touchpad settings"]],
etc. See the
[[corresponding tickets|https://redmine.tails.boum.org/code/projects/tails/issues?query_id=122]]
[[!tails_gitlab
groups/tails/-/issues?scope=all&utf8=✓&state=opened&label_name[]=C%3APersistence
desc="corresponding issues"]]
for more details.
</div>
......
[[!meta title="Recent changes"]]
See also the [recent activity on the task tracker](https://redmine.tails.boum.org/code/projects/tails/activity).
See also the [[!tails_gitlab dashboard/activity
desc="recent activity on the task tracker"]].
[[!inline pages="internal(recentchanges/change_*) and !title(change to forum/*) and !*/Discussion"
template=recentchanges show=0 sort="age"]]
......@@ -34,7 +34,9 @@ Check if the problem is already known
You can have a look at:
- The [[list of known issues|support/known_issues]]
- The [list of things that will be in the next release](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=327)
- The
[[!tails_gitlab groups/tails/-/milestones
desc="list of things that will be fixed or improved in the next release"]]
- The [[!tails_gitlab desc="rest of our open issues on GitLab"]]
<div id="bugs" class="blocks two-blocks">
......
......@@ -329,8 +329,10 @@ sessions. See the list of existing [[persistent
features|doc/first_steps/persistence/configure#features]].
We are frequently requested to add new persistent features but we are usually
busy working on other priorities. See our [open
tickets](https://redmine.tails.boum.org/code/projects/tails/issues?query_id=122)
busy working on other priorities. See our
[[!tails_gitlab
groups/tails/-/issues?scope=all&utf8=✓&state=opened&label_name[]=C%3APersistence
desc="open issues"]]
about persistence. Any bit of help [[is welcome|contribute/how/code]].
<a id="luks"></a>
......
Markdown is supported
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