#56 Adjust policy following tickets
Merged 4 months ago by zbyszek. Opened 5 months ago by zbyszek.
fesco/ zbyszek/fesco-docs update-policy-update  into  main

@@ -82,6 +82,16 @@ 

  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.


  == Track dependency issues in a timely manner


  In Rawhide, updates to packages may cause other packages to have broken dependencies.

@@ -360,11 +360,21 @@ 

  Refer to the link:https://fedoraproject.org/wiki/SIGs/KDE/Update_policy[KDE update policy] for more



- [[girara-and-zathura]]

- ===== girara and zathura


- These packages are allowed to update in stable releases together.

- See link:https://pagure.io/fesco/issue/1255[this FESCo ticket].

+ ===== Other packages


+ These packages are allowed to update in stable releases:


+ * the document viewer `zathura` and the `girara` library (link:https://pagure.io/fesco/issue/1255[FESCo #1255]),

+ * 3D printer control application `prusa-slicer` and the Cura stack (`CuraEngine` and other packages)

+   (link:https://pagure.io/fesco/issue/1255[FESCo #2652]),

+ * Python code formatter `python-black`

+   (link:https://pagure.io/fesco/issue/1255[FESCo #2652]),

+ * Python test executor `python-tox`

+   (link:https://pagure.io/fesco/issue/1255[FESCo #2652]),

+ * command-line HTTP client `httpie`

+   (link:https://pagure.io/fesco/issue/1255[FESCo #2652]),

+ * ownCloud Desktop Client `owncloud-client`

+   (link:https://pagure.io/fesco/issue/1255[FESCo #2652]).



  ==== Security fixes

no initial comment

Thanks! But, should this be scoped to package-maintaining bots, or made more general?

What other bot types would there be that would be covered by "Package maintainer responsibilities"?

Assuming you mean not covered, e.g. https://fedoraproject.org/wiki/User:Issuebot and for that matter https://fedoraproject.org/wiki/User:zodbot

Obviously some things like package updates don't apply, but other things like "create the user wiki page" and "releng (infra, whoever) can disable it if there are problems" seem general.

That said, don't let me suggesting this stop recording the specific thing to start, if it seems better to just do that.

rebased onto 3541c96fe22b9bf9dea5372c5082788f1fce2cc7

5 months ago

I did mean "covered": this text is part of a document about "package maintainer responsibilities". Thus it can't really cover zodbot. But I think it makes sense to make the text more general, without constraining it just to "package updates". I reworded it, ptal.

I'll merge this without further ado. There have been no comments in the last month.

rebased onto 7626310

4 months ago

Pull-Request has been merged by zbyszek

4 months ago