Hello, My name is Dimitrios Desyllas, and I am seeking for a package sponsor for a small utility I develop upon: https://github.com/pc-magas/mkdotenv
I am not too familiar with the process and I followed the steps as seen upon: https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/
I already release rpms for fedrora 41: https://github.com/pc-magas/mkdotenv/releases/tag/v0.1.7
My goal is for this small utility to be part of fedora packages.
@pc-magas Was wondering, did you ever get a sponsor? I'm requestion a sponsor as well, but no luck finding one.
NO I have not found a sponsor.
Hello community, I currently have releases newer version since 0.1.7:
https://github.com/pc-magas/mkdotenv/releases/tag/v0.3.1
Maybe I missed it, but where is the package review ticket? The process starts with a submitted package; jumping directly to sponsorship is skipping a fundamental piece of the process. Either a sponsor will do the package review or the interactions that happen as part of the package review will be useful information for the prospective sponsors.
I suggest you read the packaging guidelines. Your current spec file would fail on many points, I certainly wouldn't sponsor you until you learn the basics.
https://raw.githubusercontent.com/pc-magas/mkdotenv/refs/heads/master/rpmbuild/SPECS/mkdotenv.spec
Please submit your Bugzilla new package request as out lined in https://docs.fedoraproject.org/en-US/package-maintainers/New_Package_Process_for_New_Contributors/. There is an automated Fedora review that will show many of your obvious mistakes. Correct them, resubmit and then ask for manual review