Re: LilyPond GSoC logistics

classic Classic list List threaded Threaded
8 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: LilyPond GSoC logistics

Werner LEMBERG

Hello Owen,


> First, would it be possible to shift the schedule a week earlier?
> ASU classes start on August 20th, and it would not be ideal for me
> to still be working then.  I can take the rest of this week to
> familiarize myself with the codebase (I've already started doing
> that), and then we can start on Monday, if you're open to that.

this is fine.  Basically, it doesn't matter for me when you start or
stop; it's only GSoC that gives a rhythm.

> Second, just so you're aware, I may take a weekday or two off during
> the summer, but if I do, I'll make up for the lost time on weekends,
> so that shouldn't set the timetable back.

Again, I don't care :-) Most people work in bursts, and I won't
enforce any way of scheduled working.  The only thing that is both
useful and important is weekly reports to the list – even if you just
write that you weren't able to work because of this and that.  I
measure progress in git commits and educated questions to the list.

> Third, how often would you like to touch base?

What do you mean with 'base'?

> My thought is that I could send a weekly progress report to the
> mailing list to allow for others' input, but if you have a better
> idea, please let me know.

Yep, see above.

> Fourth, now that I have LilyDev up and running and can compile from
> source, what branch should I work from?

I suggest that you take current master.  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'.

> Should I periodically fetch changes to make sure my work stays
> compatible with current development?

Ideally, yes, but this is probably not an issue since there are only
few changes (if at all) to the code you are expected to work on.  So
rebasing can be delayed until you've reached a stage that you are
comfortable with.

> And should I be working off the new GitLab repository now that
> that's a thing?

Yes, we've moved.


    Werner
Reply | Threaded
Open this post in threaded view
|

Re: LilyPond GSoC logistics

Arthur Reutenauer
On Wed, May 20, 2020 at 07:39:51AM +0200, Werner LEMBERG wrote:
>> Third, how often would you like to touch base?
>
> What do you mean with 'base'?

  “How often would you like me to make contact?” :-)

        https://www.lexico.com/definition/touch_base

  Best,

                Arthur

Reply | Threaded
Open this post in threaded view
|

Re: LilyPond GSoC logistics

Valentin Villenave-3
On 5/20/20, Arthur Reutenauer <[hidden email]> wrote:
>   “How often would you like me to make contact?” :-)
> https://www.lexico.com/definition/touch_base

I urge you not to look up that phrase on Urban Dictionary… ;-)

Cheers,
-- V.

Reply | Threaded
Open this post in threaded view
|

Re: LilyPond GSoC logistics

Caio Barros
Em qua, 20 de mai de 2020 04:17, Valentin Villenave <[hidden email]>
escreveu:

> On 5/20/20, Arthur Reutenauer <[hidden email]> wrote:
> >   “How often would you like me to make contact?” :-)
> >       https://www.lexico.com/definition/touch_base
>
> I urge you not to look up that phrase on Urban Dictionary… ;-)
>
> Cheers,
> -- V.
>

That got me laughing a lot!

Caio

>
Reply | Threaded
Open this post in threaded view
|

Re: LilyPond GSoC logistics

Dan Eble
In reply to this post by Valentin Villenave-3


> On May 20, 2020, at 03:17, Valentin Villenave <[hidden email]> wrote:
>
> On 5/20/20, Arthur Reutenauer <[hidden email]> wrote:
>>  “How often would you like me to make contact?” :-)
>> https://www.lexico.com/definition/touch_base
>
> I urge you not to look up that phrase on Urban Dictionary… ;-)

s/that phrase/anything


Dan


Reply | Threaded
Open this post in threaded view
|

Re: LilyPond GSoC logistics

Owen Lamb
In reply to this post by Werner LEMBERG
>
> 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!
Reply | Threaded
Open this post in threaded view
|

Re: LilyPond GSoC logistics

Urs Liska-3


Am 21. Mai 2020 19:21:27 MESZ schrieb Owen Lamb <[hidden email]>:

>>
>> 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?

Yes, that should be how it is.

I think the message should read "not a fork". A fork is a personal copy that you need when you don't have push access to a repository.

A "clone" in Git-speak is the local copy you are actually working in. Of course you will have such a clone.

HTH
Urs


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

--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

Reply | Threaded
Open this post in threaded view
|

Re: LilyPond GSoC logistics

Werner LEMBERG
In reply to this post by Owen Lamb

> 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?

Thanks, Urs, for correcting me: I indeed mean 'no personal fork'.


    Werner