Re: Access to push new branch to origin

[Jonas Hahnfeld]

Am Samstag, den 23.05.2020, 16:38 +0200 schrieb Urs Liska:
> Am 23. Mai 2020 15:01:11 MESZ schrieb Werner LEMBERG <address@hidden>:
> > > I can grant you access to the repository later today if needed.
> > > However I'd first like to understand (probably from Werner) what
> > > makes a branch in the upstream repository more "preserving" than a
> > > public clone.  Being distributed it really doesn't make much
> > > difference from the git perspective.
> > 
> > IMO, code for a LilyPond GSoC project should become an integral part
> > of the master git repository.  I think it should be freezed in its
> > final form (this is, right after GSoC ends) for documentation
> > purposes.  If the stuff gets merged, the branch should still stay and
> > not be deleted.
> > 
> > Note that this is my personal point of view, and I don't insist on it.
> > On the other hand: if you see problems with that approach please
> > elaborate.
> 
> I would second that a student who has been accepted to GSoC should be 
> considered part of the team and grantwd push access, as long as there are 
> regulations preventing them from accidentally pushing to master.

Invited @WolfGangsta to the lilypond group.

signature.asc
Description: This is a digitally signed message part