I think the concern here was in adding further volume to the dev list, which should be primarily about just that, 'Development'. And EDU could be an opt-in list. EDU is a wonderful initiative, however the more non-dev related content we poor into dev, the more we pester the core development population and dilute the purpose of the list. Besides, us Edu/Marketing people are nothing without the devs focused on building an awesome product :).
-my 2 cents >-----Original Message----- >From: Sebastien Goasguen [mailto:run...@gmail.com] >Sent: Tuesday, April 16, 2013 1:58 AM >To: dev@cloudstack.apache.org >Subject: [DISCUSS] labels for cloudstack university and GSoC > >Hi folks, > >Some of you may have seen: >https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+Univer >sity > >I also emailed about the Google Summer of Code. > >Kelcey mentioned creating an edu mailing list. > >I have not particular feelings about this and I wanted to discuss it. > >GSoC will be across dev and users. Students are expected to join the >community, work on JIRA and submitted patches etc.. >ACSEDU will be across dev/users and marketing. > >Instead of creating a list maybe we can just use tags/labels in emails: > >[GSOC] and [ACSEDU] > >The only issue I see is that there will be information that is relevant to all lists >and I don't want to leave anyone out. > >Thoughts ? > >-Sebastien
