Thanks, Fabio!
I'm sorry I missed the process to cut a ticket in packager-sponsors. I've done
that now:
https://pagure.io/packager-sponsors/issue/511
That doc page was one of the few I was bouncing around until I opted to email this list.
That page linked to the repo's README, which then linked "Procedure for new
packagers" to
https://fedoraproject.org/wiki/Join_the_package_collection_maintainers
, which linked back to the original doc page. That page had a section on "How to find
a sponsor", which seemed to imply I'd need to find a sponsor to volunteer
*before* moving ahead. Meanwhile, I noticed that several 'Self Introduction'
emails on this list had sought and received sponsorship, so I figured this was a way that
would work.
It may help if said doc page elaborated the process, perhaps by describing an example
request, and if the README on `packager-sponsors` was also elaborated and updated to not
link to dead wikis. I can try to send some PRs to help out there.
I understood why `packager` membership is required for various infrastructure access; it
makes perfect sense to avoid managing effectively-free-world-writable storage :) I
don't believe I raised any contention there. The PR that Maxwell linked seems very
appealing, though. It would be great if PRs with new sources from non-packager-members
could pass CI without any action from maintainers.
The problem that Maxwell raised about sources updates is not one that I've
experienced. I've had a PR with new sources be accepted as-is just fine (
https://src.fedoraproject.org/rpms/python-prompt-toolkit/pull-request/1 ). It's just
that the CI run was failing (as per state of my other outstanding PRs) until the
maintainer stepped in.
Cheers,
Malcolm
P.S. my apologies for letting my corporate mailserver rules mess up the thread subject by
adding '[EXTERNAL]'. I'll try to catch that in future.
On Thu, 6 Jan 2022 18:27:31 +0000, "Fabio Valentini"
<decathorpe(a)gmail.com> wrote:
Hi Malcolm,
Welcome to Fedora! It's great to see more Amazon Linux people joining up. :)
There *is* documentation for how to join the "packager" group, but it
is sometimes not very discoverable, depending on the exact search
terms you use ...
https://docs.fedoraproject.org/en-US/package-maintainers/Joining_the_Pack...
Making PRs and proving that you have understood the basics of Fedora /
RPM packaging is a good step towards getting sponsored.
If you want to go the direct route, you can open a ticket here, where
you can apply for sponsorship into the packager group directly:
https://pagure.io/packager-sponsors (don't forget to list your
contributions to Fedora in the ticket, i.e. accepted PRs, non-binding
package reviews, etc.)
And, you are right, not being able to upload sources for new versions
when making a PR is unfortunate. On the other hand, making it possible
to upload arbitrary files to Fedora servers for "untrusted" users is
not a good idea either. So we really don't have a good solution for
that yet ...
As Maxwell has noted in another reply, you can use a partial
workaround for this problem - by updating the "sources" and
".gitignore" files (running "fedpkg new-sources --offline"). Then a
packager group member can just upload the actual file(s) to the cache
and merge the PR - and this then doesn't require any additional
commits or changes to your PR.
Fabio / decathorpe
_______________________________________________
devel mailing list -- devel(a)lists.fedoraproject.org
To unsubscribe send an email to devel-leave(a)lists.fedoraproject.org
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@lists.fedoraproject.org
Do not reply to spam on the list, report it:
https://pagure.io/fedora-infrastructure