Right now im working on carbon-kernel in trunk. As discussed offline, we can do a parallel trunk creating effort for platform as well. (it should be based on a released kernel version)
Or else I can attend to the task once I'm finish with this. thanks, --Pradeep On Wed, Jan 23, 2013 at 12:09 PM, Sameera Jayasoma <[email protected]> wrote: > But Amila with our current SVN model, we cannot simply restrict access > only to Carbon kernel project. Either restrict all or nothing. If we need > to implement the partial access model, we need to change the svn structure, > AFAIK. > > Thanks, > Sameera. > > > > > On Wed, Jan 23, 2013 at 11:48 AM, Amila Suriarachchi <[email protected]>wrote: > >> >> >> On Wed, Jan 23, 2013 at 11:21 AM, Nuwan Bandara <[email protected]> wrote: >> >>> +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. >>> >> >> We are going to do this from 4.1.0 release onwards. 4.1.0 and 4.2.0 based >> on svn. Will move to git with 5.0.0 >> >> thanks, >> Amila. >> >> >>> >>> 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 >>> >>> >> >> >> -- >> *Amila Suriarachchi* >> >> Software Architect >> WSO2 Inc. ; http://wso2.com >> >> lean . enterprise . middleware >> >> phone : +94 71 3082805 >> > > > > -- > 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 > > -- *Pradeep Fernando* Member, Management Committee - Platform & Cloud Technologies Senior Software Engineer;WSO2 Inc.; http://wso2.com blog: http://pradeepfernando.blogspot.com m: +94776603662
_______________________________________________ Dev mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/dev
