Dear Cristian, Thank you for your kind and thoughtful reply.
I understand that much of the situation stems from infrastructure limitations and procedural ambiguity, rather than malice or oversight. Your recognition of my efforts — even informally — means a great deal, and I appreciate your time reviewing my work. As for acknowledgment, I do not seek credit for personal gratification, but rather to ensure that open contribution is respected fairly, especially when contributors follow procedures and provide verifiable results. This is especially important in environments where transparency and reproducibility matter, such as when EPEL packages are used in regulated or critical systems. I will consider joining the #devel room and Join-SIG as you suggested, and I welcome further dialogue on how we can improve the non-packager experience. Thank you again for your respect and professionalism. Best regards, Akiyoshi Kurita (FAS: redadmin) 2025年6月19日(木) 21:02 Cristian Le via devel <devel@lists.fedoraproject.org>: > > Hi Kurita-san, > > I believe most of this is a miscommunication and some issues with the > infrastructure. The primary mode of contribution for non-packagers is to open > PRs in the src.fedoraproject.org. > > Regarding the ssh issue, this is indeed a known issue because only packagers > have access to pushing via SSH. This will likely be fixed when the git forge > is changed. Before I was a packager, I pushed to the fork via https, but I > don't remember how I authenticated it, maybe via `fkinit`. > > We are happy to recognize your efforts before-hand, but how would you like > that recognition. I have checked your work and it seems to be the same as the > version in src.fedoraproject.org which is a rebuild with the rawhide sources > for the epel version. Usually you can get acknowledgement for testing such > builds in the bugzilla bug, the pull request or bohdi update tests. There are > no official guidelines for more fine-grained acknowledgements, and if there > were, it would get very clogged up in the kernel package for example, where > all sorts of people do such tests [1]. > > I hope you don't take this as discouragement towards present and future > contributions. If you have some suggestions on how to improve the > non-packager experience, we are more than happy to hear them. > > Also consider joining us in the #devel:fedoraproject.org [2] where we can > discuss more fine-grained issues, and where you can get responses from the > community much faster. There is also the Join-SIG as Vit mentioned, where you > can find more general guidance for the contribution process. > > [1]: https://bodhi.fedoraproject.org/updates/FEDORA-2025-d22e0cdcad > [2]: https://matrix.to/#/#devel:fedoraproject.org > > -- > _______________________________________________ > 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
