jberkus added a new comment to an issue you are following: `` I am opposed to both having a new list and especially to having a new IRC channel. Let me explain the main reason for my opposition, followed by some detail on IRC vs. ML. A lot of the container audience is new developers and devops people. These folks generally prefer not to use "antiquated" media like email and IRC at all (mostly they use slack and github issues). We really want to reach this sector as users and potential contributors. It's bad enough that we're asking them to join a mailing list or an IRC channel at all; asking them to join *multiple* lists and channels is an automatic "Forget it, I'll use something else". Now, for the IRC channel, it's a fact today that #fedora-cloud and #atomic are used almost interchangeably by the contributors to Atomic Host and its underlying tech. I've seen CAH, CLI and rpm-ostree discussions on #fedora-cloud, and I've seen Fedora Atomic build discussions on #atomic. Given that, we should stop confusing new users and simply have One Big Channel with all things Atomic, which would be channel #atomic. The mailing list is more complicated. If you look at the traffic on cloud@lists.fedoraproject, you'll see that 80% of the traffic is automated notices of some kind. My proposal is that we: a. Move all *discussion* traffic to atomic-devel@xxxxxxxxxxxxxxxx b. Create a new list, atomic@xxxxxxx, which is exclusively for automated notices While this seems like a fine difference from Dusty's proposal, the distinction is important. Again, like #atomic, there is no clear distinction between what discussion belongs on atomic-devel vs. cloud@fedora, and as a result discussions end up getting crossed over or sent to both. This is very confusing to new community participants, especially if they're only subscribed to one of the lists. Second, by making the list split discussion vs. notices, we allow people to join in the discussion without requiring them to receive all of the automated notices. `` To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/295 _______________________________________________ cloud mailing list -- cloud@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to cloud-leave@xxxxxxxxxxxxxxxxxxxxxxx
