On 21-12-2023 14:25, Patrick Vavrina wrote:
Thank you for your comments.
First I could take the current GitHub upstream source for Frites [1] and create a RPM
package locally.
Have I to use Fedora Rawhide for packaging and testing?
Not necessarily. But it will make you understanding of the packaging
process easier if you familiarize yourself with the process.
While it is certainly possible to build the software locally, before you
set out to write the spec file and have mock build an RPM from the spec
file, I usually start with mock right away using `fedpkg`, which is
explained in the docs [2].
There's also the GNU Hello tutorial [3] which explains the process a bit
more.
You will probably still have some questions after reading through the
docs and taking the first steps. Don't be shy. Just ask. Either here or
on Matrix. Whatever you feel the most comfortable with. Every journey
starts with a first step...
Could you please tell me when I will go for acceptance to Package
Maintainers group?
As Ankur already pointed out, there different ways to get sponsored into
the packager group. All of these are outlined in the docs [4]. You are
currently on the "submitting a package" path. Once you have packaged
Frites, you submit it for review. After successful review by a sponsor,
you will be added to the packagers group, so you can import the package
and make it available in Fedora.
Not every packager is also a sponsor. I'm not. But Ankur is. But all
that is for later and we'll help you get sorted. First, there needs to
be a package that can be reviewed.
[2]
https://docs.fedoraproject.org/en-US/package-maintainers/Package_Maintena...
[3]
https://docs.fedoraproject.org/en-US/package-maintainers/Packaging_Tutori...
[4]
https://docs.fedoraproject.org/en-US/fesco/Packager_sponsor_policy/#reque...
PS: Please don't feel discouraged by the large amount of information
that is thrown at you. Take it one step at a time at your desired speed.
Things will become clearer as you go.
-- Sandro