Zen

Source string Source string

467/10000 · 467

The string is read only.

English Actions
Manage security issues
Package maintainer should handle security issues quickly, and if they need help they should contact the link:https://fedoraproject.org/wiki/Category:Security_Team#Contact[Security Response Team].
Work with upstream
It is recommended that package maintainers work closely with upstream wherever possible. This can include:
Send any changes to upstream.
Participate on the upstream mailing list.
Get an account on upstream bug trackers.
Forward severe bugs upstream when possible for assistance.
Refer to link:https://docs.fedoraproject.org/en-US/package-maintainers/Staying_Close_to_Upstream_Projects/[Staying Close to Upstream Projects] for more information on this.
Work with Testing
There are lots of places for package maintainers to interface with QA to improve the quality of Fedora. It is recommended that maintainers:
On package submission, provide information to QA on how to debug/triage the package, for use for bug submitters and triagers
Provide test cases of general functionality, for use when testing for regressions
On update submission, provide test cases for things fixed in the update, for testers to use
Deal with reported bugs in a timely manner
If you find yourself unable to handle the load of bugs from your package(s), please ask for assistance on the link:https://admin.fedoraproject.org/mailman/listinfo/devel[devel] and/or link:https://admin.fedoraproject.org/mailman/listinfo/test[test] lists. Teaching triagers about how to triage your bugs or getting help from other maintainers can not only reduce your load, but improve Fedora. Consider reaching out for some (more) co-maintainers to assist as well.
If there are bugs which you aren't capable of fixing yourself because they deal with intricacies of the source code which you don't fully understand, then you still need to address these bugs. It can be helpful to work with the upstream maintainer of the code, obtain help from more code-oriented people on fedora-devel, or check other distributions for patches. Always be sure to post to the bug report what you have done so that the reporter knows what it happening and what to expect. It is recommended that non-coder packagers should find co-maintainers who are familiar with the programming language used by their package(s), and can help with such bugs as a kind of 'second line support'.
Try and solve bugs or issues for the release against which they were reported, or if that is impractical note to bug reporters why their bug cannot be fixed in that release
Package updates
The link:https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/[Package update policy] provides guidance for maintainers who are updating packages in Rawhide, in "branched releases", and in the already-released "stable" branches.
In summary, however, maintainers should bear in mind that:
Releases should go from less conservative (Rawhide) to more so (the oldest supported stable release).
Many Fedora users update automatically, so it is most important that an update doesn't cause a users' applications or system to stop working suddenly.
Fedora users who do not update automatically may review the descriptions attached to updates before choosing whether they should apply them.
Not all Fedora users have good Internet bandwidth available and may prefer a single update with multiple changes rather than many updates in a short period.
Mentor and watch over co-maintainers
When you take on co-maintainers you enter into a partnership with them. They are able to work on the package which takes some of the burden off of you but you need to also be prepared to both help them along and make sure they aren't committing any grevious mistakes. So do be available to answer questions that the co-maintainers may have and also keep an eye on the changes they make to the package to keep issues from cropping up unexpectedly.
Watching over the changes to your package also goes for changes made by people who are not explicit co-maintainers if you have opened your package for any packager to commit to.
You can also take on co-maintainers that are not yet sponsored into the packager group provided that you agree to mentor them in the ways of packaging for Fedora: teaching them both about the tools we use and the link:https://docs.fedoraproject.org/en-US/packaging-guidelines/[packaging guidelines] they need to follow. See the link:https://docs.fedoraproject.org/en-US/package-maintainers/How_to_Get_Sponsored_into_the_Packager_Group/#become_a_co_maintainer[How to Get Sponsored page] for details on getting a new packager sponsored if you are not a sponsor yourself.
Bot accounts
In the case when an automatic process is used in lieu of normal maintainer actions, a separate bot account should be used. The name of the account **should** end in "bot". The maintainers setting up the bot **must** create a wiki page for the bot account (https://fedoraproject.org/wiki/User:<bot>) with contact information to the maintainers and an explanation of what the bot does. If the updates submitted by the bot are causing problems that require immediate attention, rel-eng may disable the account temporarily.

Loading…

User avatar None

Source string added
If you find yourself unable to handle the load of bugs from your package(s), please ask for assistance on the link:https://admin.fedoraproject.org/mailman/listinfo/devel[devel] and/or link:https://admin.fedoraproject.org/mailman/listinfo/test[test] lists. Teaching triagers about how to triage your bugs or getting help from other maintainers can not only reduce your load, but improve Fedora. Consider reaching out for some (more) co-maintainers to assist as well.
4 years ago
Browse all string changes

Things to check

Unpluralised

The string is used as plural, but not using plural forms

Reset

Glossary

English English
No related strings found in the glossary.

1137596 String information

Source string description
type: Plain text
Flags
read-only
Source string location
./pages/Package_maintainer_responsibilities.adoc:53
String age
4 years ago
Last updated
a year ago
Source string age
4 years ago
Translation file
pot/master/pages/Package_maintainer_responsibilities.pot, string 24