Hi Robie, On 1/22/25 05:40 AM, Robie Basak wrote:
On Tue, Jan 21, 2025 at 11:44:41PM +0100, Sebastien Bacher wrote:-1 from me on merging those, I think there is value in having a lower traffic channel where people can be focused on milestones (today it is not really making a difference becasue #ubuntu-devel is quiet but let's hope that moving to a more modern platform will bring back some activity). The queuebot is also quite noisy during freezes and I think that would have an negative impact on the #devel channel.That said I think we would benefit of some guideline/clarity on the purpose of the channels. I do think that pings to the archive admin and SRU teams would be better placed on #devel which is often not the case today.The general sentiment seems to be -1 on merging the -devel and -release channels, so let's consider that dropped from my proposal.
Thanks.
I think your point on needing guideline/clarity on purpose is a good one though. Could those wanting to keep the split define what belongs in which channel please? It seems reasonable to ask for that if we're going to keep the split, we need this anyway for a split to be useful in practice, and I'm interested to see if everyone actually agrees on what each side of the split is actually for :-)
From what I can tell, the general consensus is that it should stay as-is. If someone were to ask me about the differences today, here's what I'd say... The Release IRC channel contains: - queuebot, for queue-related messages. - The SRU Team, via the ubuntu-sru ping, and pokes related to SRUs. - The Archive Administrators, via the ubuntu-archive ping. - The Release Team, via the ubuntu-release ping. - Discussion around interpreting Britney/Heidi outputs and transitions, generally speaking. - Generally speaking, it's nice to communicate when something disruptive is happening (mass FTBFS due to a broken upload, a freeze being set in place, starting a massive transition). This is the place for it. - Unlike Debian, in Ubuntu during the normal open archive, we do not require explicit approval from the Release Team for transitions. That being said, it's the Cool and Good Thing to do to give them a heads-up beforehand. - I'll note my recent (within the last few days) ping to ubuntu-release and Utkarsh's response being a good model. That was a great interaction, and I'd like to see more of that. The Development IRC channel contains: - Pings from the wider community about current development issues. As a semi-frequent example, Debian Developers popping in to point out a patch we should grab. (Thank you to the DDs that are collaborative in this respect!) - Patch piloting, and general chatter about patch sponsorship. - In-depth discussions about the technical aspect of Ubuntu among Ubuntu Developers. As an example, recent libgit2 discussions. I see #ubuntu-release as being much more specific and pointed in intent than #ubuntu-devel. As it stands right now, it's much easier to go off-topic in #ubuntu-release than #ubuntu-devel. Speaking of on-topic versus off-topic, thus far in the Ubuntu Matrix community, we have avoided those terms entirely in favor of channel purpose. For example, the Ubuntu Flavors channel does not have an idea of on-topic versus off-topic; it's much looser, and allows for free discussion not otherwise constrained by a list. That being said, it's not free-range; it just has to stay related to flavors, directly or indirectly. I'd encourage us to relax the standards a little bit on the development Matrix channels as well. Lastly, I also suggest that we split Patch Piloting into its own room. This would serve as a dedicated hub for training new Ubuntu Developers, sponsoring their patches, maintaining the sponsorship report, and packaging guide discussion. That would allow a degree of separation between the extremely green, new developers asking tons of questions, and the day-to-day chatter from established Ubuntu Developers. Thoughts on that are welcome. Thanks, -- Simon Quigley si...@tsimonq2.net @tsimonq2:ubuntu.com on Matrix tsimonq2 on LiberaChat and OFTC 5C7A BEA2 0F86 3045 9CC8 C8B5 E27F 2CF8 458C 2FA4
OpenPGP_signature.asc
Description: OpenPGP digital signature
-- ubuntu-devel mailing list ubuntu-devel@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel
