Hi Jens,
Am 05.05.20 um 21:28 schrieb Adrian Adrian:
> I was looking to join Fedora development, and as I'm most familiar with
> Python, I thought the Python SIG would be my way to go. Following the
> https://fedoraproject.org/wiki/SIGs/Python/JoinSIG guide, it suggests to post
> a self-introduction to the mailing list, so that's what I'm doing now :)
Welcome :-)
I guess there is a lot of important stuff where you can help out (both in
Fedora and/or upstream).
Just in case you don't find anything and you want to go more into packaging
you could check out blocking bugs for issue 1797129 ("certbot in EPEL 7 should
use Python 3"):
https://bugzilla.redhat.com/buglist.cgi?bug_id=1797129&bug_id_type=anddependson&format=tvp&list_id=11041137#
(click "Expand all" for the full horror show ;-)
There are a lot of bugs to fix but most fixes are really easy as it means
adding Python 3 subpackages for EPEL 7 and usually the EPEL 7 version already
works with Python 3.
However there is a good chance (50% maybe?) you find outdated/ancient
packaging which I try to clean up while working on a package:
- no tests
executed during builds even though upstream has a suitable test
suite (this can involve a bit of digging upstream as sometimes you just need
1-2 additional patches to make it work in Fedora)
- e.g. bad licensing information
- using modern macros
If you want to look a bit at upstream Python work which could also help Fedora
(+other distros) you might want to check out python-betamax.
Currently Fedora can not run the test suite during package builds because it
requires internet access. Changing network endpoints are also a reason why the
upstream test suite breaks sometimes so it would be beneficial to mock all
network interaction.
There are two upstream tickets for this:
https://github.com/betamaxpy/betamax/issues/145
https://github.com/betamaxpy/betamax/issues/184#issuecomment-612632563
Once that is fixed ideally there is an upstream release which we can package
in Fedora. You might want to ping the maintainer so he knows that there is
something extra than just bumping the version.
Another pet peeve of mine is GPG verification during package builds as
described here:
https://fedoraproject.org/wiki/PackagingDrafts:GPGSignatures#Source_file_verification
The issue is finding software which has signed releases and tweaking the spec
files accordingly.
Just a word of caution: The most frustrating thing when contributing to Fedora
(for me) is waiting for maintainers after submitting pull requests etc.
This can even affect seemingly high-profile packages like "mesa". For example
this pull request of mine did not get any reaction even though it is open for
about 1/2 year and I think its benefits are clear cut:
https://src.fedoraproject.org/rpms/mesa/pull-request/6
Pagure lists 15 maintainers and I sent several private emails but did not get
any response.
Most of the times I can get my changes in as needed. Even though I'm not a
sponsor feel free to ping me if you have questions or if you feel stuck. I'll
try to guide you to the right people/places to get you unblocked.
Felix
_______________________________________________
python-devel mailing list -- python-devel@lists.fedoraproject.org
To unsubscribe send an email to python-devel-le...@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/python-devel@lists.fedoraproject.org
