Yes, that distinction is clear to me, but as you said if English is not your first language it might be less clear or the process might seem scary.
I feel there could at least be maintenance of the documents themselves, which never hurts. It's a part of Fedora too! We have the nice site for Packaging Guidelines themselves, but Joining the Package Collection Maintainers wiki page is a little dated in layout and whatnot. We could earmark that.
I haven't thought of submitting my package at all until last week. I've maintained it on Copr for several months now, and I've spent a few hours with a Debian user who was having troubles with an build script I made for Debian & Ubuntu users (they had library conflicts because of Matlab).
It's clear, but it's not plainly stated that package submission to, and more importantly inclusion in, the official package repository is a different thing from simple application distribution. Responding to users, addressing edge cases, and ensuring breakage don't occur is definitely the actual responsibility that comes with hurdling through the process and having a package included in the repo.
For all other intents and purposes, Copr, the Outer Rim, is the place to be. It's fun there, a bit of a Kessel run.
On Sat., May 1, 2021, 2:42 a.m. Mattia Verga via devel, <devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Il 01/05/21 10:21, Joan Moreau via devel ha scritto:
>
> For instance, personally, I am not using Fedora at all (Arch fan ;) )
> but just willing to make my piece of software available widely for
> those interested. I am happy to maintain the package in the long run,
> but will not get involve to much into Fedora project except my small
> piece of software contribution.
>
>
That's absolutely fine, but in my opinion the wiki should clarify one
thing: a certain amount of involvement in Fedora should be taken into
account if one wants to become a packager.
I don't think it's not entirely clear that by publishing a package in
Fedora repositories implies 1) maintain the package updated, 2) maintain
the specfile in line with future Packaging Guidelines changes and 3) get
in touch with the community to handle possible bugs filed by other users
which install your package.
There must be a section that clearly states that if the scope is "I made
this piece of software and I'll fire through Fedora repositories, then
goodbye", or "I use this software, I'll push into Fedora repositories
and never touch it again until this version is fine for me" there are
other means to achieve that.
That's the reason for having the "sponsorship barrier" at joining time,
that, I know very well, it's quite scaring if you're not English mother
tongue. Anyway, after a successful review of a package, one could get in
touch with some sponsors by filing a ticket in the appropriate page [1]
and some nice folk will help them to enter the packager group.
Mattia
[1] https://pagure.io/packager-sponsors/
_______________________________________________
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
