I recently posted a cross-post to the project discussion which requires topics. I am not sure if the topics there are fully relevant, but could/should a new tag be made for the fedora-ci topics?
2 Likes
@mattdm can you help with this?
@mattdm Post-holiday ping?
PS: We are also considering a tmt tag as we have a few announcements we would like to make on https://communityblog.fedoraproject.org/ regarding that project that would affect the Fedora packagers
@kevin Could you create the tag #fedora-ci in the Project Discussion category by adding it to this topic? It fulfills the criteria for Project Discussion tags (see the weekend’s discussion in Matrix’s #commops chan), but it seems mods cannot do that in Project Discussion (behavior has changed: I can now create new tags in Project Discussion, but the system is immediately removing them again; not sure if a setting has been changed or if a software update made the different behavior). Would be great if you could just create / add it here 
Thanks 
(supplement: I moved this post, so the topic I am referring to for creating the tag is this one: Migration plan from Zuul to Packit as dist-git CI runners )
Looks like there is missing the specific fas-group for it 
Please let’s move this discussion to Requesting a tag for fedora-ci?
I moved some posts here.
Creating tags in Project Discussion does at the moment need a site-admin, Mod is not sufficient. Any site-admin can do that. We have already triggered Kevin and Matthew. Give them some time
In case a site-admin is available (not sure about Adam as QA + RH, if you are site-admin?) but doesn’t know the process: just go to one of the related topics (such as [1]), and do what you do to add an existing tag, and enter the tag name fedora-ci → you will then get the possibility to create the tag in the drop down that usually shows the existing tags you can choose from. once added to its first topic, the tag will be available. I can do that, but as mod, the system seems to still remove the new tags immediately once added.
[1] Migration plan from Zuul to Packit as dist-git CI runners
In reply to Requesting a tag for fedora-ci? - #5 by ilikelinux
There are 2 FAS groups associated:
We might want to merge them, but that would probably be more complicated to detangle
Creating tags in Discourse, in any category, is NOT related to FAS groups
1 Like
These tags are tied to groups. I will have to check with @mattdm on how
to add them, as it’s not clear to me off hand. ;(
1 Like
What about #ci-sig or #ci-team? I don’t want all of our tags to start with “fedora”… although maybe this is a legit special case?
The “groups” here aren’t directly related to FAS groups (they are “tag groups”, which is how tags are mapped to categories). However, there are also user groups, which are directly synced from FAS. I can set that up if you like…
Would that mean fedora-ci-user and fedora-ci-admins? Not in this case. Although it would be nice for making sure the relevant users are subscribed to the linked topics. But I think there was some push-back against such automated notification enrolling right?
In general the canonical name is Fedora CI, except that the mailing list used to be ci@lists.fp.o, and the forge.fp.o organization is also ci. Some consistency cleanup would be great. I am cautious about plain ci name because it would imply overlap with infrastructure team, and maybe fedora-forge.
Sorry about asking again … for what stands CI? I checked the abbreviations finder and now I am just 
My favorite is “Continuous Improvement”
Knowing the exact meaning of CI would maybe help to find a common understandable term?!
I found it out … but had to go into the rabit/worm hole 
CI = Continuous Integration
1 Like
There was. But that’s because I started with, like, the largest group. A small group where everyone involved actually would find it useful could be a different story.
While I am not 100% sure if I get the “manifest” of fedora-ci, I could imagine that making its tag as -SIG or -Team would be as confusing as “package-maintainer-SIG”: it’s not false but still misleading imho. It’s more “something” that needs to be able “to address others” and “to be addressed by others” rather than being a “dedicated/delimited organized sig/team”, right? I agree to the reluctance about “fedora” in the name though, it’s unnecessary redundant. How about just #ci or #Continuous-Integration ? That would align with package-maintainers
@ilikelinux about your question: Fedora Continuous Integration Portal (Making sure you're not a bot!)
Yes … while digging a bit more I also found this out, see above:
1 Like
Fine with me. If it turns out to become confusing, it could be renamed wouldn’t it? Having any tag to advertise as something that the users should subscribe to is the main priority right now.
Ideally I want to avoid the -SIG part because I want the tag to be about topics that the users subscribe to, not for the “internal” discussions.
Yes, you can always let us know if something doesn’t work. Then we can find and implement a solution. Tags ain’t fixed
1 Like
I’m totally open to revisiting this, but the concept was that we’d have tags in Project Discussion which replace team mailing lists, and then general tags like #ci in Ask Fedora for user questions and support. (If tag subscription were per category rather than global, we could have the same tag for both, but it’s awkward as things exist.)
I’m kinda leaning towards #fedora-ci actually being the best compromise in this case. And yes, we can always rename.
1 Like
Makes sense. The lists there was never used much for internal discussion about the sig itself, and now that we have the matrix channel, I don’t think that would be used for it either. The topics are more similar with the infrastructure lists. Primarily we would want to have a home for such discussions again in whatever form more convenient for future migration plans.
Well that is tricky because our users are the packagers, so I don’t think ask fedora is appropriate for that.