Commit 4b96e1e9 authored by Martyn Welch's avatar Martyn Welch
Browse files

Tweak description of maintainers



Take into account that maintainers may take resposibility for a single
component.
Signed-off-by: default avatarMartyn Welch <martyn.welch@collabora.com>
parent 0ea5ec1e
Pipeline #165479 passed with stages
in 6 minutes and 57 seconds
......@@ -465,8 +465,10 @@ of the project and long-term trusted contributors, though in many projects with
a longer history, lead of the project may well have been taken on by another
knowledgable contributor.
The basic role of a project maintainer is to:
- set direction for the project;
The basic role of a project maintainers is to:
- help set the direction for the project;
- ensure that the projects polices followed and that the project continues to
work towards it's stated objectives;
- review and evaluate contributions for correctness and suitability;
- apply accepted contributions;
- resolve issues (such as bugs and security issues) that arise;
......@@ -475,13 +477,15 @@ The basic role of a project maintainer is to:
Larger projects may have many maintainers who specialise in parts of the work
that need to be carried out or who have deeper knowledge of specific parts of a
larger codebase.
larger codebase. For example such maintainers may be in charge of applying
these roles to a single component within the Apertis distribution.
The Apertis maintainers are funded by the projects backers, with direction
agreed between the maintainers and backers to fullfill the needs of the
backers. Many of the maintainers have a long history with the Apertis project
or have come to the project with lots of experience in the area in which they
work (such as Debian packaging).
backers whilst driving the project towards it's stated objectives. Many of the
maintainers have a long history with the Apertis project or have come to the
project with lots of experience in the area in which they work (such as Debian
packaging).
The Apertis maintainers are responsible for ensuring that bug and security
fixes are applied to the various components of which Apertis is made and for
......@@ -494,7 +498,7 @@ In addition to tracking updates and fixes from the projects that Apertis uses,
the maintainers also review changes that are submitted to the project from
contributors. The maintainers actively contribute to the project and submit
changes following the same processes that are expected from other contributors.
Such changes are reviewed to ensure that they meet the project goals,
All such changes are reviewed to ensure that they meet the project goals,
objectives and policies as well as ensuring the are sound and do not contain
any obvious issues.
......@@ -508,15 +512,15 @@ impossible to maintain or requiring changes to make the contribution more
maintainable for the project.
{{% notice tip %}}
The maintainer is usually taking on the responsibility to ensure that your
changes and modifications continue to be provided by the project, porting them
to new versions of packages or ensuring that they remain valid as the project
inevitably changes to accomodate new goals or the ever changing computing
landscape. As a result accepting changes will transfer this burden from you to
the maintainers. You can continue to use the project without needing to
actively maintain the changes. As a result the onus is on the contributor to
persuade the project of the advantages of the changes, not for the project to
be beholden to accept contributions.
The maintainer is usually taking on the responsibility on behalf of the project
to ensure that your changes and modifications continue to be provided by the
project, porting them to new versions of packages or ensuring that they remain
valid as the project inevitably changes to accomodate new goals or the ever
changing computing landscape. As a result accepting changes will transfer this
burden from you to the maintainers. You can continue to use the project without
needing to actively maintain the changes. As a result the onus is on the
contributor to persuade the project of the advantages of the changes, not for
the project to be beholden to accept contributions.
{{% /notice %}}
# Contribution Template
......
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