Okay since this is a tag to help facilitate a group that is forming up a SIG it makes sense to me to add #hummingbird, #hummingbird-team, or #hummingbird-sig in the Fedora Teams and Interest Groups tag collection.
Based on stated intent, #hummingbird-sig seems like is what is needed right now to help. Are we good with that?
Until we have a more formal process I’m going to create that tag now. We probably need to have a checklist for “So you want to create a SIG” that has this in it.
Beyond that… #hummingbird is probably going to be used for general discussion in Water Cooler and Ask Fedora at some point if there is general discussion about hummingbird. I believe those areas are less controlled for tag creation.
Going beyond that…looking at how this tag group is organized.. we should think about how we update these tags as the governance for a specific interest area evolves. For example I’m assuming that the bootc-initiative tag may need to transition into an atomics-workinggroup as part of its transition out of an initiative. Another example. epel-sig probably needs to transition to epel-steering-commitee or some such. Just a thought, as we need to figure how tags transition as areas of interest transition from loosely organized groups of people into more formal governance structures: iniatiatives, teams, workingroups, subprojects, committees.
Going beyond that… we don’t really know right now how many SIGs are functional and which are effectively adjourned. Since we don’t have a minimum requirement for what defines an “active” SIG, its very difficult to confidently clean up after SIGs that are no longer active. But we need to start making the attempt to clean up a bit. It might be as small a thing as having SIGs doing a proof of life ping every release, a ping from an associated FAS group sponsor, and seeing which SIGs go without a ping for a couple of releases.
Well, the generally agreed process for site admin stuff is there Confusion is created by the misleading and incomplete public documentation and the fact that this topic and the repo had been created by coincidence on the same day. That issue might be mitigated in future, and the first case is documented soon. So in future, just using the public repo should suffice, and related documentation will develop over time.
I think you cannot create the tag in PD, as you are a Moderator, not a Site Admin. I would be also careful, as the tags of PD are - as mentioned - intertwined with groups. I am not fully aware of the implications. But the ticket is updated, so that a site admin can create it. That way, things are transparent in future, and it is ensured that people have in the repo all implications and issues available at first glance, may it be the creator of a ticket or those who process it, incl. review, to be sure → site admin stuff can break everything.
I can create it in ask.fedora if you want (in ask.fedora you can do it too, but you can also give me a if I shall create it there), but I suggest to reconsider water cooler, as this would cause likely confusion: on the water cooler, we usually sum that up to tech-talk in general. To give an overview of the water cooler organization, this is the tags of the water cooler: