Re: LilyPond GSoC logistics

[Owen Lamb]

>
> To preserve your code within LilyPond it probably makes sense if you put
> your code into a private (but public) branch of the upstream lilypond
> repository (i.e., not a gitlab clone of it), for example
> 'dev/lamb/GSoC-2020'.
>

I'm a bit confused here, so let me just make sure I understand what you're
saying.

I'll be making a new branch titled "dev/lamb/GSoC-2020" in the GitLab
repository, based off the current master. It will be "private" in the sense
that it's my personal workspace (hence the "lamb" namespace), but it will
be "public" in the sense that it will be visible to the public. It will not
be merely "a gitlab clone" of the master branch, since it is a new branch
entirely. Did I interpret that correctly?

I'm pretty new to git, so please excuse my lack of expertise!