name: fedora-l10n
If we should wait for the namespace creation to create our projects: the sooner the better.
When is this no longer needed or useful? (YYYY/MM/DD) this is a long term need, that's why we ask for a generic name so it can answer other need of the Localization team in the future.
If we cannot complete your request, what is the impact? We'll have to use a giant git repository to store all translations of documentation, which is a terrible idea.
For any question: contact is @asamalik @bex may also give some context More information is here: https://taiga.fedorainfracloud.org/project/asamalik-antora-for-docs/epic/1
oh, it was easier than expected, @bex told me "namespace" may be related to "groups". I just created one, you may now close this ticket ;)
The group is created: https://pagure.io/group/fedora-l10n but it doesn't lists projects and I can't add members.
But the projects are well listed here: https://pagure.io/projects/fedora-l10n/%2A
I'm really confused now..
You should add the group to the projects, then they will show up in the project's page
There looks like to be an issue with group addition because I can't find "fedora-l10n", or I did something wrong (it's a webm video, let's hope it works): <img alt="Capture_decran_video_de_27-09-2018_215324.webm" src="/fedora-infrastructure/issue/raw/files/278606440724c82d3a41d81595dc7314674a0a62bab7ef095b68509201a88b89-Capture_decran_video_de_27-09-2018_215324.webm" />
Yep, that definitely looks like a bug. ;(
Hopefully @pingou can look into it soon...
Metadata Update from @kevin: - Issue assigned to pingou - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: pagure
Filed upstream at pagure#3801.
Fixed upstream in pagure#3803 which I hotfixed on pagure.io so you can keep going :)
Sorry for the issue!
I confirm it works, thanks for your help
Metadata Update from @kevin: - Issue close_status updated to: Upstream - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.