Thank you for the info. Unfortunately I haven't learned c yet so I'd be relying
pretty heavily on upstream to patch issues after being reported. I can't tell
if it's been abandoned because the Github repo hasn't been touched in ~6
months, but I pinged the developer for a status update. Should be the last
thing that needs to get sorted before I can be confident in submitting the
package.
And yes I am aware that pretty much all software has bugs, my question was
mainly about if severe usability bugs are problematic in this situation, I
believe it was issue #12 which prevented(and still prevents) Tails from using
kloak, so I wasn't sure if it would be enough to bar it from Fedora's repos. I
hope that clears my question up a bit, nonetheless you still answered my
question just fine, so thank you again.
Mar 24, 2024, 08:17 by msu...@redhat.com:
> Dne 24. 03. 24 v 12:32 dop. None via devel napsal(a):
>
>> Hello everyone! My name is Jonathon Hyde, and I want to become a packager
>> for Fedora. I'm excited to contribute back something to a project that I
>> have been using for so long. I haven't made my first package submission yet,
>> but I wanted kloak to be among the first packages I submit. I had a question
>> first though, what is the tolerance for buggy/beta software in Fedora? The
>> project has a couple of notable open issues on Github, mainly
>> https://github.com/vmonaco/kloak/issues/12 and
>> https://github.com/vmonaco/kloak/issues/72. I have already successfully
>> built with mock and weeded out the issues that showed up in rpmlint, I'm
>> just not sure what state upstream needs to be in before a package submission
>> can be accepted in Fedora. I had quite a few submissions I wanted to make
>> and maintain, so a generalized answer/explanation is preferred, because I
>> can't find any documentation to answer this particular question.
>>
>> I look forward to learning and contributing back what little I can offer to
>> the Fedora community.
>>
> Closest to your question is:
>
> https://docs.fedoraproject.org/en-US/fesco/Package_maintainer_responsibilities/#_manage_security_issues
>
> You should work on security bugs in timely manner. And you should co-operate
> with upstream on solving bugs. Somehow. In very elemental meaning that means
> you forward the bug to upstream.
>
> And BTW every project has bugs. If therewa condition to include only packages
> without bug then Fedora would have no package at all. :)
>
> Feel free to submit your package for Package Review.
>
> --
> Miroslav Suchy, RHCA
> Red Hat, Manager, Packit and CPT, #brno, #fedora-buildsys
> --
> ___
> devel mailing list -- devel@lists.fedoraproject.org
> To unsubscribe send an email to 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/devel@lists.fedoraproject.org
> Do not reply to spam, report it:
> https://pagure.io/fedora-infrastructure/new_issue
>
--
___
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to 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/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue