+1, thats a good idea, Once its moved to git, and if somebody needs and does a change they can trigger a pull request where kernel team can review and merge.
Regards, /Nuwan On Wed, Jan 23, 2013 at 11:12 AM, Sameera Jayasoma <[email protected]> wrote: > Hi Folks, > > During the last Carbon Architecture meeting, we had a discussion along the > $Subject. The main goal of this process is to limit the number of > Committers in Carbon kernel to regulate the code changes. Once this process > is in place, it will help us to > > > - Reduce the changes introduced in Carbon kernel > - Reduces the build breaks due to platform-wide changes. > - Reduce the number of Carbon kernel minor releases for various > product releases. > - Stabilise our P2 based provisioning story. > - and many more... > > > We can effectively put this process into the picture once the Carbon > kernel code has been moved the Git. As a start the whole carbon kernel team > or any other selected group can become committers. But others have to earn > the committer rights through our meritocracy model. > > What are your thought on this? > > > Thanks, > Sameera. > > -- > Sameera Jayasoma > Senior Technical Lead > > WSO2, Inc. (http://wso2.com) > email: [email protected] > blog: http://sameera.adahas.org > > Lean . Enterprise . Middleware > > _______________________________________________ > Dev mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/dev > > -- *Thanks & Regards, Nuwan Bandara Associate Technical Lead & Member, MC, Development Technologies WSO2 Inc. - lean . enterprise . middleware | http://wso2.com blog : http://nuwanbando.com; email: [email protected]; phone: +94 11 763 9629 * <http://www.nuwanbando.com/>
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
