Dne 04. 10. 21 v 11:34 Zbigniew Jędrzejewski-Szmek napsal(a):
On Mon, Oct 04, 2021 at 10:57:42AM +0200, Vít Ondruch wrote:
Hi,
Recently, there have been a lot of discussions on this list as well
as we have internally about onboarding. During our internal
brainstorming, we were initially discussing that it could be useful
to have some package one can experiment with without being too much
worried about the result.
However, discussing this back and forth, we figured that it might
also be good idea to actually have something such as "onboarding"
package, where new coming package maintainer could gradually gain
experience with the packaging workflows. So the simplest tasks could
be:
1) Add changelog entry into onboarding package and open PR with the
change. This would not require too many privileges. Alternatively
this could include change to "CONTRIBUTORS" file. I suspect that
also some current Fedora contributors might be interested to send
such PR ;)
2) Second step could be something similar, but that would require
the packager to be already sponsored and they could go through the
whole process themeselves just with some light guidance if needed.
Forgot to mention these could be rewarded by appropriate badges ;)
+1.
We already have some test-only packages (for ci testing?), and one
more wouldn't really matter. It'd be nice to match the naming pattern.
https://fedoraproject.org/wiki/DummyTestPackages
I assume that 1) above would be be done with the sponsor/mentor doing
the merge and actual build, and 2) would be done with no direct
sponsor/mentor interaction.
The question always is how far we would go. E.g. would be some or
mutliple of those scenarios enough to be sponsored?
There could also be Copr scenarios, or it could be incorporated in the (1).
This package should have multiple release branches, to exercise
multi-release updates.
Good idea, right.
Vít
This could be extended in the future. E.g. next step could be:
3) Submit module update.
Apart from gaining experience, this could also help with the common
question "where should I start". And of course our sponsoring
guidelines could be refreshed suggesting/requesting to take these
steps at some point.
Zbyszek
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
