On 11/15/2012 09:22 AM, Hugh Brock wrote:
----- Original Message -----
From: "Justin Clift" <jclift(a)redhat.com>
To: "aeolus-devel" <aeolus-devel(a)lists.fedorahosted.org>
Sent: Thursday, November 15, 2012 4:29:51 AM
Subject: Please move Community Dev discussions to new mailing list
Hi all,
Now that we have the new "Aeolus Community Management" mailing
list, please move our Community Development discussions there:
https://lists.fedorahosted.org/mailman/listinfo/aeolus-comm-mgmt
Example threads to move:
* "Aeolus Developer Conference Report" thread
* [all] Cabal discussion / planning threads
* [anything to do with mission statement]
Things to not move:
* Patches
* Aeolus coding topics
* Technical architecture discussion
(ie "How should we do persistent state?")
* Sprint scheduling
Regards and best wishes,
Justin Clift
--
Aeolus Cloud Evangelist
http://www.aeolusproject.org
This isn't exactly the split I was imagining -- I had thought that coding topics and
technical discussion would also go on the new community list. I'm OK with doing it
this way, but is this how everyone else understood the split?
--Hugh
I'm confused then. If we're moving everything but patches and pull
request notifications, etc., then shouldn't we be moving the opposite
direction? Keep aeolus-dev and make a new list for patches?
I understood that "aeolus development discussions" would continue as-is
on aeolus-devel, we'd have this new list relating to cabal-oriented
discussions (i.e. things explicitly cross-project and related to
decisions for the cabal, and there was some other possibility of a
separate new list where we would configure a github hook to actually
post the patches associated with pull requests (instead of just links).
Scott