On Tue, Apr 16, 2013 at 4:57 AM, Sebastien Goasguen <[email protected]> wrote: > Hi folks, > > Some of you may have seen: > https://cwiki.apache.org/confluence/display/CLOUDSTACK/CloudStack+University > > 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
The goal of GSOC is to embed folks in the open source community they are working in. Not to shuffle them off to some low-volume list to isolate them from the flow of mail that is dev@. (as well as commits@, issues@, and users@) For better or worse dev@ is voluminous, and GSOC folks need to learn to operate in that environment, and operate as a part of the dev community. ACSEDU might be slightly different, but I worry about fragmenting our community. Dev@ should really be where things happen. --David
