Akihito Kurita venit, vidit, dixit 2025-06-17 01:02:13: > Hi all, > > I’d like to report an issue currently preventing me from contributing > to Fedora from Japan. > > - SSH access to `src.fedoraproject.org` is consistently timing out > from multiple Japanese networks (home ISP, Sakura VPS, EC2 Tokyo). > - HTTPS `git push` with API tokens fails as expected. > - I also cannot generate a Git Authentication Token (CLI token), as > the option is missing from my account (`redadmin`). > > I’ve filed a full report with evidence and screenshots here: > 👉 https://pagure.io/fedora-infrastructure/issue/12602 > > This blocks all push access, even to forks, while I'm still waiting > for packager sponsorship. > > Thanks for your time and attention. >
Hi there, and welcome as a contributor! I don't consider it an undue restriction if packaging infrastructure is available to packagers only. You can clone dist-git freely, build locally/in mock and submit spec files and patches via bugzilla or otherwise. Indeed, being able to do that shows that you can test changes before submitting them, which you should do as a packager. Once you are in the packagers' group you have full access (including pushes and cache uploads). Cheers, Michael -- _______________________________________________ epel-devel mailing list -- [email protected] To unsubscribe send an email to [email protected] 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/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
