On Mon, Jul 12, 2021 at 7:04 PM Kevin Fenzi <kevin@xxxxxxxxx> wrote: > > On Mon, Jul 12, 2021 at 01:26:19PM -0500, Tony Asleson wrote: > > Upstream pywbem project took 2 internal libraries and broke them out > > into separate libraries. I asked if they would be OK with maintaining > > these new packages in fedora and they said yes[1]. They followed the > > process and asked for a sponsor and got no response [2]. > > Sorry about that. No worries > You could add them in as co-maintainers, provided you are willing to > show them how packaging works, etc. > > See: https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer This seems to imply co-maintaining an existing package, not a new package? > Did they or you ever submit the packages for review? Looks like this is for one of them: https://bugzilla.redhat.com/show_bug.cgi?id=1880953 It looks like a review comment was made, but no response yet from Andreas (Andy). CC'ing him on this email. IIRC after it looks good is when you can get a sponsor? > They (or you) may also want to post to the python-sig list instead of > the main devel list. Sometimes things get really busy here and people > miss posts. Andy CC'd > > They have now pitched the idea of using "vendorize" to meet this > > requirement [3]. However, I believe the answer to this from a fedora > > packaging standpoint is no. Is this correct? > > I'd say it's much better not to, yes. Yeah, otherwise all the stuff being done for rust packages wouldn't be occurring :-) Thank you for your response -Tony _______________________________________________ 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