From Fedora Project Wiki
(Loving this wiki syntax ^_^)
(reshuffle, update comms, redefine mvp)
Line 1: Line 1:
== Mission ==
 
  
 
'''This SIG is a work in progress and will be announced properly once we're ready, stay tuned.'''
 
'''This SIG is a work in progress and will be announced properly once we're ready, stay tuned.'''
  
We would like to offer an alternative way to maintain Fedora Linux packages in comparison to [[Package_maintenance_guide|the traditional way via dist-git]] which should be more convenient to maintainers and require less manual actions.
 
  
 
=== Rules ===
 
=== Rules ===
  
* Whatever we produce here, it MUST NOT violate Fedora Packaging Guidelines (we should strive to change them if needed).
+
* Whatever we produce here, it '''MUST NOT''' violate Fedora Packaging Guidelines (we should strive to change them if needed).
 +
* Proven packagers and rel-eng still needs to be able to do their work in dist-git: their workflows MUST NOT be dirupted.
 
* Maintainers HAVE TO be able to step in for automation and replace some of its actions if needed. The automation NEEDS TO handle such situation.
 
* Maintainers HAVE TO be able to step in for automation and replace some of its actions if needed. The automation NEEDS TO handle such situation.
* Proven packagers and rel-eng still needs to be able to do their work in dist-git: their workflows MUST NOT be dirupted.
+
 
  
 
=== Goals ===
 
=== Goals ===
  
For start, we would love to focus on two areas:
+
Our main goal is build a Minimal Viable Product during the Fedora 35 development cycle.
 +
 
 +
==== MVP ====
 +
 
 +
* Source git repos can be easily created, set up and this is well-documented.
 +
 
 +
* The workflow is defined well and it's clear where the repositories are hosted.
 +
 
 +
* Source-git content is synchronized into dist-git via dist-git pull requests.
 +
 
 +
* Specfile changes are synchronized back to the source-git repo from dist-git.
  
==== Easier maintenance for rawhide ====
 
  
Updating packages in rawhide should only require changes in the packaging files and approving PRs.
+
==== Benefits to Fedora ====
  
===== Workflow =====
+
* Downstream patches are tracked as git commits. This way it's easier to backport or cherry-pick changes from the upstream and rebase the patches when a new upstream release happens.
 +
 
 +
* Patch files are handled by automation which makes the job of maintainers easier.
  
# Set up a source-git repository manually on a packit-supported platform (github.com, gitlab.com)
+
* It should be easier to onboard more maintainers in Fedora community since the workflow would be closer to the way the contributors work in the upstream project.
#* This includes creating a specific branch and setting up jobs for packit-service to handle events.
 
#* CI can (and should) be set up (such as [https://packit.dev/docs/testing-farm/ Testing Farm]).
 
# Anyone in the community is able to interact with this repository the same way with any other open-source project.
 
# Packit-service can accept events when a new upstream release is done (via [https://release-monitoring.org/ Upstream Release Monitoring]).
 
# Packit-service creates a pull request which contains changes to bring the new release to Rawhide.
 
#* A dist-git PR is created in parallel. Downstream checks are synchronized to the source-git PR.
 
# The owner of the source-git repository reviews and updates the pull request as needed.
 
# Once approved, dist-git PR is merged first and packit-service triggers a build in Rawhide. If the build passes, source-git PR is merged as well. If the build fails, source-git PR is updated a new dist-git PR is created and doing the cycle of this step again.
 
  
==== More convenient way to work on downstream patches ====
 
  
Downstream patches are tracked as git commits. This way it's easier to backport or cherry-pick changes from the upstream and rebase the patches when a new upstream release happens.
 
  
* Commits can be picked up easily the same way as in any other git repo.
+
=== Meetings ===
  
* Patch file names can be configured.
+
TBD
  
* Patches are automatically added to spec file.
+
==== 1st meeting agenda ====
  
 +
* Agree on communication channels
 +
* Define how work is going to be tracked
  
==== MVP ====
 
  
The "product" of this SIG should be implementation of a following MVP. Once that's done, we'll evaluate what should be the next steps.
+
=== Follow-up work ===
  
* Source git repos can be easily created, set up and this is well-documented.
+
Once the MVP is implemented, we can start building more automated workflow on top of the MVP.
  
* New upstream releases are automatically brought into the source-git repos when configured.
+
===== Workflow =====
  
* Changes pushed to source-git repos are automatically proposed downstream for inclusion in dist-git.
+
# Set up a source-git repository manually on a packit-supported platform (github.com, gitlab.com)
 +
#* This includes creating a specific branch and setting up jobs for packit-service to handle events.
 +
#* CI can (and should) be set up (such as [https://packit.dev/docs/testing-farm/ Testing Farm]).
 +
# Anyone in the community is able to interact with this repository the same way with any other open-source project.
 +
# Packit-service can accept events when a new upstream release is done (via [https://release-monitoring.org/ Upstream Release Monitoring]).
 +
# Packit-service creates a pull request which contains changes to bring the new release to Rawhide.
 +
#* A dist-git PR is created in parallel. Downstream checks are synchronized to the source-git PR.
 +
# The owner of the source-git repository reviews and updates the pull request as needed.
 +
# Once approved, dist-git PR is merged first and packit-service triggers a build in Rawhide. If the build passes, source-git PR is merged as well. If the build fails, source-git PR is updated a new dist-git PR is created and doing the cycle of this step again.
  
  
Line 63: Line 72:
  
 
== Communication ==
 
== Communication ==
* #packit on Freenode IRC
+
 
* Mailing list - user-cont-team@redhat.com
+
TBD - will be defined during our first meeting.
 +
 
 +
In the meantime you can reach out to the team on #packit at Freenode IRC.
  
 
== Important links ==
 
== Important links ==
  
 
* [https://packit.dev/docs/source-git Source-git]
 
* [https://packit.dev/docs/source-git Source-git]

Revision as of 11:14, 26 March 2021

This SIG is a work in progress and will be announced properly once we're ready, stay tuned.


Rules

  • Whatever we produce here, it MUST NOT violate Fedora Packaging Guidelines (we should strive to change them if needed).
  • Proven packagers and rel-eng still needs to be able to do their work in dist-git: their workflows MUST NOT be dirupted.
  • Maintainers HAVE TO be able to step in for automation and replace some of its actions if needed. The automation NEEDS TO handle such situation.


Goals

Our main goal is build a Minimal Viable Product during the Fedora 35 development cycle.

MVP

  • Source git repos can be easily created, set up and this is well-documented.
  • The workflow is defined well and it's clear where the repositories are hosted.
  • Source-git content is synchronized into dist-git via dist-git pull requests.
  • Specfile changes are synchronized back to the source-git repo from dist-git.


Benefits to Fedora

  • Downstream patches are tracked as git commits. This way it's easier to backport or cherry-pick changes from the upstream and rebase the patches when a new upstream release happens.
  • Patch files are handled by automation which makes the job of maintainers easier.
  • It should be easier to onboard more maintainers in Fedora community since the workflow would be closer to the way the contributors work in the upstream project.


Meetings

TBD

1st meeting agenda

  • Agree on communication channels
  • Define how work is going to be tracked


Follow-up work

Once the MVP is implemented, we can start building more automated workflow on top of the MVP.

Workflow
  1. Set up a source-git repository manually on a packit-supported platform (github.com, gitlab.com)
    • This includes creating a specific branch and setting up jobs for packit-service to handle events.
    • CI can (and should) be set up (such as Testing Farm).
  2. Anyone in the community is able to interact with this repository the same way with any other open-source project.
  3. Packit-service can accept events when a new upstream release is done (via Upstream Release Monitoring).
  4. Packit-service creates a pull request which contains changes to bring the new release to Rawhide.
    • A dist-git PR is created in parallel. Downstream checks are synchronized to the source-git PR.
  5. The owner of the source-git repository reviews and updates the pull request as needed.
  6. Once approved, dist-git PR is merged first and packit-service triggers a build in Rawhide. If the build passes, source-git PR is merged as well. If the build fails, source-git PR is updated a new dist-git PR is created and doing the cycle of this step again.


Members

Status

We have been in a planning stage of the SIG: bringing interested people together to flesh out the who, what, where, when, and how.

Communication

TBD - will be defined during our first meeting.

In the meantime you can reach out to the team on #packit at Freenode IRC.

Important links