Re: [Engine-devel] Getting rid of arch@ovirt.org?

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 07/15/2012 01:53 AM, Ayal Baron wrote: - -1 I don't normally read engine-devel and vdsm-devel, so I hadn't noticed that discussions I would expect to be on arch@ are not happening here. I'm probably not the only person in that situation. If this project were 100% about Engine and VDSM, then I could understand your reasoning. But we've already added a few new incubating projects, we have subsystem teams such as documentation and infrastructure, and we all need a single location where we know we can reach *all* contributors to this project. If we try to force all that discussion on to engine-devel, not everyone would be interested. There is enough on engine-devel that is not general interest that it would become noise (as it has for me, so I filter it) or people would drop it all together. Perhaps what we need to do is have the discipline to cross-post *all* general interest discussions from the project mailing list back to arch@? Enforce the rule that decisions that affect the whole project have to be ratified on arch@ instead of whatever project list the discussions started on? Strongly suggest that all contributors be on arch@ and announce@ as a minimum? I'm sure there are open source projects that don't have a general interest contributor list, preferring to run all that discussion on a technical-focused list. But I don't recommend it. It's the kind of thing that repels contributors who don't want to sort through deep developer discussions just to find out what is generally going on. - - Karsten - -- Karsten 'quaid' Wade, Sr. Analyst - Community Growth http://TheOpenSourceWay.org .^\ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41