I think becoming a packager is not as complicated as you’ve written. To
become a packager, you must convince a packager sponsor to sponsor you.
That’s all; there is no rule about how to do the convincing.
Sponsors want to be confident that you understand and are likely to
follow the packaging guidelines. Submitting PR’s, submitting new
packages for review (to be imported after you are sponsored), and doing
unofficial package reviews are three common and suggested ways to
establish a track record, but a sponsor may choose to sponsor a new
packager (or not!) for any reason whatsoever.
In my opinion, rescuing orphaned packages tends to be one of the harder
packaging tasks. Many packages are orphaned for lack of time, so they
often have lingering obsolete practices that ought to be brought into
compliance with current guidelines. Many others are orphaned because
they have problems the previous packager found too difficult,
time-consuming, or frustrating to fix. Working on orphaned packages can
be a good way to learn quickly and a great way to contribute, but I
think new packagers are likely to need more mentoring for these
packages, not less.
On 8/11/21 11:55 AM, Stephen Snow wrote:
Okay,
So to become a packager you have to
- Get someone to sponsor you as a packager
- Review existing packages for others
- take over an orphaned package
- introduce a package to Fedora Linux that needs to get approval to
be packaged
- some other criteria I forgot after reading so many linked documents
....
I tried to "take" an orphaned package ... can't not a packager, so I
tried to do a review, and even though I appear to be part of the group,
I couldn't even access the review build because apparently I don't have
the rights.
My point is yes, it is requiring effort and it should but not to the
extent of stonewalling contributions, and largely because the
guidelines are confusing, it is a bit like reading a hand drawn map
while driving IMO.
So, back to orphaned packages, if a person from the community is signed
up, signed the CA, the CoC, is a member of the appropriate groups, that
person should be able to volunteer to take on orphaned packages, at
least on a trila basis till they need no handholding. The deesire to
contribute should be the bar to contribute is my point. If technical
requirements are not being met, then they would be removed as packager
and basically timed out for a specific time till they get the
opportunity to try packaging again. However, if they succeed, then
great for all, more contributors, less workload across the board. I
understand that RPM packaging is a complex process, and creating Fedora
Linux is a large task, but for new contributors how are they to learn
the process, if the gate keepers are too efficient?
Regards,
and still hoping to be a packager .... someday....
Stephen
On Wed, 2021-08-11 at 14:16 +0200, Vitaly Zaitsev via devel wrote:
On 11/08/2021 13:37, Stephen Snow wrote:
making joining the packaging group(s) a bit more open would go a
long way to garnering more packagers IMO
New contributors must know at least the Fedora packaging guidelines.
This is the minimum barrier.
use COPR. Simple and easy.
--
Sincerely,
Vitaly Zaitsev (vitaly@xxxxxxxxxxxxxx)
_______________________________________________
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
_______________________________________________
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
