+1 for separate branches for separate GSOC features, they could get easily organized to branches named like /gsoc2025/<feature-name>
K On Wed, Apr 9, 2025 at 9:48 AM Ádám Sághy <adamsa...@gmail.com> wrote: > Hi > > If many gsoc students are working on different things, this might be a > challenge and later it will be hard to cherrypick things. > > Would it be better to ask them to work on feature branches and each gsoc > student has its own branch and they implement their feature there? > > Regards > Adam > > Sent from my iPhone > > On 9 Apr 2025, at 08:39, James Dailey <jamespdai...@gmail.com> wrote: > > > There isn’t a way to implement different branch level commit rights, so > no… But the idea would be to “loosen” the review since the code will not > be part of /dev mainline… in that case “LGTM -GSOC” on that branch is just > a cursory check and someone with rights is free to accept the change into > this special branch. It has to be understood what the acceptance means. > > if the mentor and the student want to take it to a full commit level and > face additional scrutiny, they can do that, but it may delay or stall their > efforts. > > > > > On Tue, Apr 8, 2025 at 11:28 PM Bharath Gowda <bgo...@mifos.org> wrote: > >> Hi James, >> >> Yes it sounds like a good idea. >> Will it also help to give more people(especially mentors) the permission >> to review and merge the PRs on to the new branch (only to this branch if it >> is possible)? >> >> >> Regards, >> Bharath >> Lead Implementation Analyst | Mifos Initiative >> Skype: live:cbharath4| Mobile: +91.7019635592 >> http://mifos.org <http://facebook.com/mifos> >> <http://www.twitter.com/mifos> >> >> >> On Wed, Apr 9, 2025 at 11:26 AM James Dailey <jdai...@apache.org> wrote: >> >>> Devs - >>> >>> I’d like to propose that we create a branch on the project that would >>> allow for the GSOC students to commit changes to that branch. >>> /gsoc2025 >>> >>> This branch would not need to be merged upstream but having it visible >>> and with a different acceptance standard would be useful. >>> >>> All students working in that branch would have to figure out their >>> conflicts and essentially be a project within the project. It’s less >>> stressful for all concerned - no need to pass all on the reviews to get >>> your PR accepted in this “provisional” branch. >>> >>> Maybe some commits could be cherry picked later on. >>> >>> What do you think? >>> >>> Thanks >>> >>
