-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
KB:
Can you look at the excerpt below and let me know what you think?
tl;dnr - I'd like to get consensus right away on where we'll be having the technical part of the student/mentor discussions. Some cases it will be in the upstream project space, but I think best practice especially during the coding time of the Summer is to use "the usual channels", i.e. centos-devel and #centos-devel.
Regards, - - Karsten
On 03/03/2015 11:07 AM, Karsten Wade wrote:
On 03/03/2015 05:09 AM, Karanbir Singh wrote:
Just to be clear here, you meant that the centos-gsoc[1] list was going to be used for the GSoC specific content and the gsocadmin[2] list was for the adminstration stuff right ? Thats what we say on the wiki pages[3] and thats my understanding on how things are setup.
Lets not move the gsoc specific content to centos-devel if we dont need to.
I think we're saying the same thing. Does this align?
- If it's administrivia about how GSoC runs in the project,
discussions on dates & timing, announcements that specific deadlines are approaching, etc. == centos-gsoc@
- If it's about developing code, working with the community,
integrating with upstream and across the ecosystem, etc. == centos-devel@
Goal being to keep the GSoC-specific noise off this list, but keep all CentOS development on this list. GSoC students are generally considered to be actively developing for the project (as new contributors), so should be using all the usual communication channels.
If I don't have that right, let me know the concern.
- -- Karsten 'quaid' Wade .^\ CentOS Doer of Stuff http://TheOpenSourceWay.org \ http://community.redhat.com @quaid (identi.ca/twitter/IRC) \v' gpg: AD0E0C41