openlilylib-user Mailing List for openLilyLib (Page 2)
Resources for LilyPond and LaTeX users writing (about) music
Status: Alpha
Brought to you by:
u-li-1973
Menu
▾
▴
openlilylib-user — General openLilyLib discussion
You can subscribe to this list here.
| 2013 |
Jan
|
Feb
|
Mar
(45) |
Apr
(38) |
May
|
Jun
(4) |
Jul
(1) |
Aug
|
Sep
(10) |
Oct
|
Nov
|
Dec
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2014 |
Jan
(164) |
Feb
(4) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Marc S. <mar...@gm...> - 2014-01-26 16:44:15
|
Everyone's workflow is surely different. For me, getting line breaks the way I want them early in the process is essential, because it has major impact on spacing. For example, consideriing just the Estrella challenge, until the line breaks are in, I would not know which systems might need extra space between staves, and until I know this, I would not know which markings might need manual positioning, etc. But I can believe others might prefer differently. So I don't know that the rules have to say *when* you set the line breaks - just that when it comes to the final comparison, in most cases, it will make for more sensible comparisons if we all do it the same way. If we don't choose the same line breaks, then we are encountering different issues, making comparison less meaningful.— Marc Sabatella On Sun, Jan 26, 2014 at 3:58 AM, Phil Holmes <ma...@ph...> wrote: > ----- Original Message ----- > From: "Janek Warchoł" <lem...@gm...> > To: "OpenLilyLib User" <ope...@li...> > Sent: Saturday, January 25, 2014 11:16 PM > Subject: [oll-user] Finally, the revised instructions - please review! >> Hello, >> * i have added a rule that the submissions should have the same line >> breaking as the original engraving. This is because if the line breaking >> is significantly different, it becomes hard to compare different >> engravings. What do you think? > I'm happy with everything except this. I think line-break decisions are an > aspect to how good the overall result is, and thus how good the engraving > program is. Forcing line breaks could easily distort the overall output. > I'd accept that one of the final tweaks might be to adjust margins, staff > sizes and forced linebreaks to most closely imitate the original, but it > should be a final adjustment, not an early one. Early work should never > involve forced breaks. > -- > Phil Holmes > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > openlilylib-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlilylib-user -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Phil H. <ma...@ph...> - 2014-01-26 10:58:33
|
----- Original Message ----- From: "Janek Warchoł" <lem...@gm...> To: "OpenLilyLib User" <ope...@li...> Sent: Saturday, January 25, 2014 11:16 PM Subject: [oll-user] Finally, the revised instructions - please review! > Hello, > * i have added a rule that the submissions should have the same line > breaking as the original engraving. This is because if the line breaking > is significantly different, it becomes hard to compare different > engravings. What do you think? I'm happy with everything except this. I think line-break decisions are an aspect to how good the overall result is, and thus how good the engraving program is. Forcing line breaks could easily distort the overall output. I'd accept that one of the final tweaks might be to adjust margins, staff sizes and forced linebreaks to most closely imitate the original, but it should be a final adjustment, not an early one. Early work should never involve forced breaks. -- Phil Holmes |
|
From: Janek W. <lem...@gm...> - 2014-01-26 10:51:40
|
2014-01-26 Joshua Nichols <jos...@gm...> > Overall very good and great job. It was a little bit of a surprise to read > about the commit level of each challenge, I had no idea... I have not done > that, but I will begin doing that now. I will definitely be including all > the details of my doing as well as timing of everything. Will this be > sufficient starting now? > Don't worry! From what i see, in both challenges you have just entered the musical content - that's just the first stage in the workflow. The commits you have made seem sufficient :) > I'm very impressed with the level of commitment the authors have of these > files. > Thanks! best, Janek -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Janek W. <lem...@gm...> - 2014-01-26 10:46:06
|
Hi, 2014-01-26 Marc Sabatella <ma...@ou...> > On 1/25/2014 4:16 PM, Janek Warchoł wrote: > > * i have added a rule that the submissions should have the same line > > breaking as the original engraving. This is because if the line breaking > > is significantly different, it becomes hard to compare different > > engravings. What do you think? > > I agree this will probably make sense for most challenges. Wouldn't hurt > to leave open the possibility that some particular challenge might want > to adopt a different rule here. ok, i'll add this later. > Regarding the rules overall: I haven't read them in detail, but on a > cursory examination, this looks like exactly the level of detail I would > hope there would be. Not just regarding Git, but everything. Nice job > setting it up. We can always tweak from here. > Thanks! I put a lot of effort into them (something like 18 hours?), it's great to be appreciated :-) Janek -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Joshua N. <jos...@gm...> - 2014-01-26 02:16:31
|
Overall very good and great job. It was a little bit of a surprise to read about the commit level of each challenge, I had no idea... I have not done that, but I will begin doing that now. I will definitely be including all the details of my doing as well as timing of everything. Will this be sufficient starting now? I'm very impressed with the level of commitment the authors have of these files. IC, Josh On Sat, Jan 25, 2014 at 5:16 PM, Janek Warchoł < lem...@gm...> wrote: > Hello, > > We have finally finished rewriting the instructions for the engraving > challenges! New instructions can be found here: > > https://github.com/engraving-challenges/main/ > > Please review them and let us know if they're clear. I'm particularly > interested in opinions from people new to version control - would these > instructions make it easier for you to participate? Do you think someone > who uses Git for the first time will understand them? > > Two important questions: > * i have added a note about licensing - i'd like all submitted content to > be licensed under Creative Commons > Attribution-NonCommercial-ShareAlike< > http://creativecommons.org/licenses/by-nc-sa/4.0/deed.en_US>license. > Are you ok with that? > * i have added a rule that the submissions should have the same line > breaking as the original engraving. This is because if the line breaking > is significantly different, it becomes hard to compare different > engravings. What do you think? > > I'm going to send some invitations to our contest soon, and tomorrow we > shall start discussing the scores we already have! > > best, > Janek > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > openlilylib-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlilylib-user > -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Marc S. <ma...@ou...> - 2014-01-25 23:25:53
|
On 1/25/2014 4:16 PM, Janek Warchoł wrote: > * i have added a note about licensing - i'd like all submitted content to > be licensed under Creative Commons > Attribution-NonCommercial-ShareAlike<http://creativecommons.org/licenses/by-nc-sa/4.0/deed.en_US>license. > Are you ok with that? Yes. > * i have added a rule that the submissions should have the same line > breaking as the original engraving. This is because if the line breaking > is significantly different, it becomes hard to compare different > engravings. What do you think? I agree this will probably make sense for most challenges. Wouldn't hurt to leave open the possibility that some particular challenge might want to adopt a different rule here. Regarding the rules overall: I haven't read them in detail, but on a cursory examination, this looks like exactly the level of detail I would hope there would be. Not just regarding Git, but everything. Nice job setting it up. We can always tweak from here. Marc |
|
From: Janek W. <lem...@gm...> - 2014-01-25 23:16:28
|
Hello, We have finally finished rewriting the instructions for the engraving challenges! New instructions can be found here: https://github.com/engraving-challenges/main/ Please review them and let us know if they're clear. I'm particularly interested in opinions from people new to version control - would these instructions make it easier for you to participate? Do you think someone who uses Git for the first time will understand them? Two important questions: * i have added a note about licensing - i'd like all submitted content to be licensed under Creative Commons Attribution-NonCommercial-ShareAlike<http://creativecommons.org/licenses/by-nc-sa/4.0/deed.en_US>license. Are you ok with that? * i have added a rule that the submissions should have the same line breaking as the original engraving. This is because if the line breaking is significantly different, it becomes hard to compare different engravings. What do you think? I'm going to send some invitations to our contest soon, and tomorrow we shall start discussing the scores we already have! best, Janek -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Urs L. <ul...@op...> - 2014-01-20 23:50:23
|
Am 21.01.2014 00:47, schrieb Marc Sabatella: > Sounds good. For the record, I've gone ahead and restructed my repos as > described the previous update. I have a couple of small changes I'll > want to commit on estrella when everything is ready, then I'll be most > interested to take part in the discussion. I think you _can_ commit to the repos already. What we're trying to get in shape is mainly the guidelines (for potential further contributors). I'll probably hold off on > beginning the winterwind challenge until a few more bugs are fixed in > the development version of MuseScore I am using - shouldn't be too long > (and I'll fix them myself if I have to). That sounds like a _very good_ use for these challenges :-) Best Urs > > Marc > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > openlilylib-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlilylib-user > |
|
From: Marc S. <ma...@ou...> - 2014-01-20 23:47:57
|
Sounds good. For the record, I've gone ahead and restructed my repos as described the previous update. I have a couple of small changes I'll want to commit on estrella when everything is ready, then I'll be most interested to take part in the discussion. I'll probably hold off on beginning the winterwind challenge until a few more bugs are fixed in the development version of MuseScore I am using - shouldn't be too long (and I'll fix them myself if I have to). Marc |
|
From: Janek W. <lem...@gm...> - 2014-01-20 22:10:46
|
Hi all, the repositories with your submissions are allright (the cleanup that was done a few days ago doesn't seem to need any fixups). We're continuing to clean up the instructions and it will take us a few days more. After the cleanup is complete (this should happen no later than on weekend), i think we should a) start dicsussing the submissions that are already complete b) invite more participants! best, Janek -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Janek W. <lem...@gm...> - 2014-01-16 08:09:55
|
Hi all, 2014/1/16 Urs Liska <ul...@op...> > Hi folks, > > as Janek announced we have restructured our "Challenges" stuff, > hopefully having made everything a lot less complex. > Particularly we have split the repository to several independent ones, > which each hold a significantly smaller amount of data and complexity. > Indeed! We apologize for the inconvenience again. > Please: > - fork the two challenge repositories (not the other two ones) > i suggest to start with just forking Schumann's Estrella. Let's not try doing too many things at once. > - clone the forks locally on your computer > (remember that 'git clone' _creates_ the subdirectory, so don't > already cd into the directory of your choice) > The command will be git clone https://github.com/YOUR_USERNAME/estrella.git TARGET_PATH > - add the 'upstream' remote. > git remote add upstream https://github.com/engraving-challenges/estrella.git When you have successfully performed this step and verified that all > your work is present you can safely delete the previous Git repository > (the original 'engraving-challenges' one). Simply delete the whole > directory containing it. > ...and remove your Github fork (you have to go to "settings" on the right, and scroll down). Good luck! Janek -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Urs L. <ul...@op...> - 2014-01-16 07:49:03
|
Hi folks, as Janek announced we have restructured our "Challenges" stuff, hopefully having made everything a lot less complex. Particularly we have split the repository to several independent ones, which each hold a significantly smaller amount of data and complexity. We hope that now, once everything has settled and calmed down, we can continue our "challenges" and finally concentrate on what it should be all about: music engraving. The general information is now in the repository https://github.com/engraving-challenges/main You don't have to fork or clone this one as it mainly contains information files. If you should ever want to add or update material in this repo you can do so through the web interface. The two challenges that exist so far are in the repositories https://github.com/engraving-challenges/estrella and https://github.com/engraving-challenges/winterwind Every work that we were able to grab should now be available on the 'master' branch of the repos, so now you could go to the repo pages on Github, navigate to "your" directories and check if everything is visible there that you think it should. If you're missing anything please tell us. We have also created yet another repository https://github.com/openlilylib/git-introduction where we've copied some material. The idea is to add our explanations there and create an introduction to Git from a music engraver's perspective. We don't start with the idea of writing a complete and coherent "book", but just take the opportunity and lay down some introductory material that has gone through the most critical review - yours (and of other newcomers too). Currently it's pretty empty and only contains Marc's "Git Basics" document, but we may soon add material to it when we're going to the steps I'll tell you now. Please: - fork the two challenge repositories (not the other two ones) - clone the forks locally on your computer (remember that 'git clone' _creates_ the subdirectory, so don't already cd into the directory of your choice) - add the 'upstream' remote. When you have successfully performed this step and verified that all your work is present you can safely delete the previous Git repository (the original 'engraving-challenges' one). Simply delete the whole directory containing it. Best Urs |
|
From: David W. <da...@mu...> - 2014-01-14 09:26:27
|
I think mine are all there:
- one pdf + a readme.md for challenge 1.
- a series of 8 pdfs (the last one is the finished article) +
a readme.md for challenge 2.
[I did add commit push in each case.]
Dave
David Webber
Mozart Music Software
http://www.mozart.co.uk/
-----Original Message-----
From: Urs Liska
Sent: Monday, January 13, 2014 10:12 AM
To: ope...@li...
Subject: Re: [oll-user] [Challenges] Important: cleaning up
I'm OK with Janek's task-list.
It would be nice if all of you could do from this list what is necessary
in your case and report back. If you think you don't have to do anything
because all your relevant work is already on your GitHub fork, please
tell too.
As soon as you have pushed a commit we can pull it into our own
repostiories and tweak everything to our needs.
When we have everybody's work available we will either clean up the
repository or copy the work to a new, clean one and get back to you later.
Also from my side: Sorry for any inconveniences. It wasn't intended to
go that way, but we didn't expect this project to become a "Git primer"
project ;-)
And no, I'm not in any way disappointed by this, even if it means
considerable extra work I didn't expect. But it's a perfect example of
"good that it happened _now_". I intend to lobby LilyPond and related
text based tools in scholarly musicology, and it's a welcome opportunity
to check didactic approaches against reality. Much better than to run in
the situation we're currently in when doing a weekend seminar for a
research institution ;-)
Best
Urs
Am 13.01.2014 10:53, schrieb Janek Warchoł:
> Hi all,
>
> it turned out that our setup was not perfect (a bit too complicated) - it
> would be nice to do some clean up to make sure that any confusion is
> reduced to minimum (especially for any new participants that may appear).
>
> Of course, we have everything under control, so don't worry! :-)
>
> Below are instructions for cleanup. (They are not final - please wait for
> Urs to confirm that they're ok).
> We will most probably ask you to do three things:
>
> 1) stop working on challenges until the cleanup is finished (hopefully
> everything should be ready again tomorrow).
>
> 2) make sure that all your work is committed. Use 'git status' for that:
> if
> there are any "modified" files, or any "untracked" files that are part of
> your work and should be submitted (e.g. engraving files of your program,
> such as .sib or .musx files) you should add them using 'git add filename'
> and do a 'git commit'.
>
> 3) make sure that all your work is pushed ("uploaded") to your github
> fork:
> first, make sure that 'git status' says "working directory clean". Check
> if you have remote repository configured properly ('git remote -v' should
> list a remote named 'origin' pointing to your github fork). Use 'git
> branch' to see all your local branches (some of you will probably have
> just
> one - master. That'll make things easier :) ). Then, for each branch do
> the following:
> git checkout branchname
> git push origin branchname
>
> And check if you can see your work using GitHub's website.
>
> I apologize for inconvenience.
>
> I'll be at work for the next 9 hours - see you in the evening.
> Janek
> -------------- next part --------------
> An HTML attachment was scrubbed...
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> openlilylib-user mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openlilylib-user
>
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
openlilylib-user mailing list
ope...@li...
https://lists.sourceforge.net/lists/listinfo/openlilylib-user
|
|
From: Janek W. <lem...@gm...> - 2014-01-14 06:34:02
|
2014/1/14 Joshua Nichols <jos...@gm...> > I did everything you asked, and everything seemed to be in order. I found > all of my work (it hasn't been much) on the 2-schumann-challenge branch of > the master. > > Is this what I'm supposed to see? I didn't see my work on the master. I > assume that is the way it is supposed to be. > It's possible. Does 'git status' say "on branch 2-schumann-challenge" when you run it in your local repository? Janek -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Joshua N. <jos...@gm...> - 2014-01-14 01:34:40
|
I did everything you asked, and everything seemed to be in order. I found
all of my work (it hasn't been much) on the 2-schumann-challenge branch of
the master.
Is this what I'm supposed to see? I didn't see my work on the master. I
assume that is the way it is supposed to be.
IC,
Josh
On Mon, Jan 13, 2014 at 3:53 AM, Janek Warchoł <
lem...@gm...> wrote:
> Hi all,
>
> it turned out that our setup was not perfect (a bit too complicated) - it
> would be nice to do some clean up to make sure that any confusion is
> reduced to minimum (especially for any new participants that may appear).
>
> Of course, we have everything under control, so don't worry! :-)
>
> Below are instructions for cleanup. (They are not final - please wait for
> Urs to confirm that they're ok).
> We will most probably ask you to do three things:
>
> 1) stop working on challenges until the cleanup is finished (hopefully
> everything should be ready again tomorrow).
>
> 2) make sure that all your work is committed. Use 'git status' for that: if
> there are any "modified" files, or any "untracked" files that are part of
> your work and should be submitted (e.g. engraving files of your program,
> such as .sib or .musx files) you should add them using 'git add filename'
> and do a 'git commit'.
>
> 3) make sure that all your work is pushed ("uploaded") to your github fork:
> first, make sure that 'git status' says "working directory clean". Check
> if you have remote repository configured properly ('git remote -v' should
> list a remote named 'origin' pointing to your github fork). Use 'git
> branch' to see all your local branches (some of you will probably have just
> one - master. That'll make things easier :) ). Then, for each branch do
> the following:
> git checkout branchname
> git push origin branchname
>
> And check if you can see your work using GitHub's website.
>
> I apologize for inconvenience.
>
> I'll be at work for the next 9 hours - see you in the evening.
> Janek
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
>
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> openlilylib-user mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openlilylib-user
>
-------------- next part --------------
An HTML attachment was scrubbed...
|
|
From: Janek W. <lem...@gm...> - 2014-01-13 22:56:59
|
2014/1/13 Joshua Nichols <jos...@gm...> > I'm sorry that I haven't done it yet; being in CST and without my > computer, I'm sure you are thinking "What is taking so long!?" > No, i do realize that you may be busy. I just wanted to make sure that everyone knows i'm waiting for a confirmation. thanks, Janek -------------- next part -------------- An HTML attachment was scrubbed... |
|
From: Joshua N. <jos...@gm...> - 2014-01-13 22:54:00
|
I'm sorry that I haven't done it yet; being in CST and without my computer,
I'm sure you are thinking "What is taking so long!?"
I'll be on it very soon.
IC,
Josh
On Mon, Jan 13, 2014 at 4:50 PM, Janek Warchoł <
lem...@gm...> wrote:
> (please reply asap!)
>
> Hi all,
>
> I think my previous email about repository cleanup&maintenance may have
> not reached everyone, since some people who forked the repo seem not to be
> on the mailing list. Since i want to avoid creating confusion during
> cleanup, i'd like to ask every participant to look at my previous email
> (quoted below), perform the steps listed there and notify me that i can
> proceed.
>
> I apologize for the inconvenience.
>
> best,
> Janek
>
>
> 2014/1/13 Janek Warchoł <lem...@gm...>
>
>> it turned out that our setup was not perfect (a bit too complicated) - it
>> would be nice to do some clean up to make sure that any confusion is
>> reduced to minimum (especially for any new participants that may appear).
>>
>> Of course, we have everything under control, so don't worry! :-)
>>
>> Here are instructions for cleanup:
>>
>> 1) stop working on challenges until the cleanup is finished (hopefully
>> everything should be ready again tomorrow).
>>
>> 2) make sure that all your work is committed. Use 'git status' for that:
>> if there are any "modified" files, or any "untracked" files that are part
>> of your work and should be submitted (e.g. engraving files of your program,
>> such as .sib or .musx files) you should add them using 'git add filename'
>> and do a 'git commit'.
>>
>> 3) make sure that all your work is pushed ("uploaded") to your github
>> fork:
>> first, make sure that 'git status' says "working directory clean". Check
>> if you have remote repository configured properly ('git remote -v' should
>> list a remote named 'origin' pointing to your github fork). Use 'git
>> branch' to see all your local branches (some of you will probably have just
>> one - master. That'll make things easier :) ). Then, for each branch do
>> the following:
>> git checkout branchname
>> git push origin branchname
>>
>> And check if you can see your work using GitHub's website.
>>
>> I apologize for inconvenience.
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
|
|
From: Janek W. <lem...@gm...> - 2014-01-13 22:50:29
|
(please reply asap!)
Hi all,
I think my previous email about repository cleanup&maintenance may have not
reached everyone, since some people who forked the repo seem not to be on
the mailing list. Since i want to avoid creating confusion during cleanup,
i'd like to ask every participant to look at my previous email (quoted
below), perform the steps listed there and notify me that i can proceed.
I apologize for the inconvenience.
best,
Janek
2014/1/13 Janek Warchoł <lem...@gm...>
> it turned out that our setup was not perfect (a bit too complicated) - it
> would be nice to do some clean up to make sure that any confusion is
> reduced to minimum (especially for any new participants that may appear).
>
> Of course, we have everything under control, so don't worry! :-)
>
> Here are instructions for cleanup:
>
> 1) stop working on challenges until the cleanup is finished (hopefully
> everything should be ready again tomorrow).
>
> 2) make sure that all your work is committed. Use 'git status' for that:
> if there are any "modified" files, or any "untracked" files that are part
> of your work and should be submitted (e.g. engraving files of your program,
> such as .sib or .musx files) you should add them using 'git add filename'
> and do a 'git commit'.
>
> 3) make sure that all your work is pushed ("uploaded") to your github fork:
> first, make sure that 'git status' says "working directory clean". Check
> if you have remote repository configured properly ('git remote -v' should
> list a remote named 'origin' pointing to your github fork). Use 'git
> branch' to see all your local branches (some of you will probably have just
> one - master. That'll make things easier :) ). Then, for each branch do
> the following:
> git checkout branchname
> git push origin branchname
>
> And check if you can see your work using GitHub's website.
>
> I apologize for inconvenience.
>
-------------- next part --------------
An HTML attachment was scrubbed...
|
|
From: Shane B. <sh...@gr...> - 2014-01-13 18:39:03
|
O.k. I think I did it. The only thing was my origin was called github but otherwise I followed the instructions. git status says "# On branch master nothing to commit, working directory clean" Still have a number of irritating things that needed to be attended to most notably the oddity of fingering placement getting ignored when slurs occur. But it is at least at a legibly complete state. Shane On Mon, Jan 13, 2014 at 10:32 AM, Marc Sabatella <ma...@ou...> wrote: > All my work had already been pushed and is in fact already merged. There > are couple of additional tweaks I can see wanting to make once the dust > settles, but I'm also hoping to get a couple of bugs fixed in the > development version of MuseScore I am using, as they are causing some > things to render differently than they were when I initially did the work. > > As per Urs' instructions, I have deleted my "musescore" branch of the > Schumann challenge branch, both locally and in my fork. I have not > updated anything from the main upstream repo in the past couple of days > and will wait to do so until I hear the cleanup is completed. > > Marc > > > ------------------------------------------------------------------------------ > CenturyLink Cloud: The Leader in Enterprise Cloud Services. > Learn Why More Businesses Are Choosing CenturyLink Cloud For > Critical Workloads, Development Environments & Everything In Between. > Get a Quote or Start a Free Trial Today. > http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk > _______________________________________________ > openlilylib-user mailing list > ope...@li... > https://lists.sourceforge.net/lists/listinfo/openlilylib-user |
|
From: Marc S. <ma...@ou...> - 2014-01-13 15:32:05
|
All my work had already been pushed and is in fact already merged. There are couple of additional tweaks I can see wanting to make once the dust settles, but I'm also hoping to get a couple of bugs fixed in the development version of MuseScore I am using, as they are causing some things to render differently than they were when I initially did the work. As per Urs' instructions, I have deleted my "musescore" branch of the Schumann challenge branch, both locally and in my fork. I have not updated anything from the main upstream repo in the past couple of days and will wait to do so until I hear the cleanup is completed. Marc |
|
From: Phil H. <ma...@ph...> - 2014-01-13 10:46:05
|
----- Original Message ----- From: "Urs Liska" <ul...@op...> To: <ope...@li...> Sent: Monday, January 13, 2014 10:12 AM Subject: Re: [oll-user] [Challenges] Important: cleaning up > I'm OK with Janek's task-list. > > It would be nice if all of you could do from this list what is necessary > in your case and report back. If you think you don't have to do anything > because all your relevant work is already on your GitHub fork, please > tell too. I think that my Sibelius versions of the challenges are done as far as I'm planning currently, and are pushed to my github repository. -- Phil Holmes |
|
From: Urs L. <ul...@op...> - 2014-01-13 10:12:19
|
I'm OK with Janek's task-list.
It would be nice if all of you could do from this list what is necessary
in your case and report back. If you think you don't have to do anything
because all your relevant work is already on your GitHub fork, please
tell too.
As soon as you have pushed a commit we can pull it into our own
repostiories and tweak everything to our needs.
When we have everybody's work available we will either clean up the
repository or copy the work to a new, clean one and get back to you later.
Also from my side: Sorry for any inconveniences. It wasn't intended to
go that way, but we didn't expect this project to become a "Git primer"
project ;-)
And no, I'm not in any way disappointed by this, even if it means
considerable extra work I didn't expect. But it's a perfect example of
"good that it happened _now_". I intend to lobby LilyPond and related
text based tools in scholarly musicology, and it's a welcome opportunity
to check didactic approaches against reality. Much better than to run in
the situation we're currently in when doing a weekend seminar for a
research institution ;-)
Best
Urs
Am 13.01.2014 10:53, schrieb Janek Warchoł:
> Hi all,
>
> it turned out that our setup was not perfect (a bit too complicated) - it
> would be nice to do some clean up to make sure that any confusion is
> reduced to minimum (especially for any new participants that may appear).
>
> Of course, we have everything under control, so don't worry! :-)
>
> Below are instructions for cleanup. (They are not final - please wait for
> Urs to confirm that they're ok).
> We will most probably ask you to do three things:
>
> 1) stop working on challenges until the cleanup is finished (hopefully
> everything should be ready again tomorrow).
>
> 2) make sure that all your work is committed. Use 'git status' for that: if
> there are any "modified" files, or any "untracked" files that are part of
> your work and should be submitted (e.g. engraving files of your program,
> such as .sib or .musx files) you should add them using 'git add filename'
> and do a 'git commit'.
>
> 3) make sure that all your work is pushed ("uploaded") to your github fork:
> first, make sure that 'git status' says "working directory clean". Check
> if you have remote repository configured properly ('git remote -v' should
> list a remote named 'origin' pointing to your github fork). Use 'git
> branch' to see all your local branches (some of you will probably have just
> one - master. That'll make things easier :) ). Then, for each branch do
> the following:
> git checkout branchname
> git push origin branchname
>
> And check if you can see your work using GitHub's website.
>
> I apologize for inconvenience.
>
> I'll be at work for the next 9 hours - see you in the evening.
> Janek
> -------------- next part --------------
> An HTML attachment was scrubbed...
> ------------------------------------------------------------------------------
> CenturyLink Cloud: The Leader in Enterprise Cloud Services.
> Learn Why More Businesses Are Choosing CenturyLink Cloud For
> Critical Workloads, Development Environments & Everything In Between.
> Get a Quote or Start a Free Trial Today.
> http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
> _______________________________________________
> openlilylib-user mailing list
> ope...@li...
> https://lists.sourceforge.net/lists/listinfo/openlilylib-user
>
|
|
From: Janek W. <lem...@gm...> - 2014-01-13 09:53:40
|
Hi all,
it turned out that our setup was not perfect (a bit too complicated) - it
would be nice to do some clean up to make sure that any confusion is
reduced to minimum (especially for any new participants that may appear).
Of course, we have everything under control, so don't worry! :-)
Below are instructions for cleanup. (They are not final - please wait for
Urs to confirm that they're ok).
We will most probably ask you to do three things:
1) stop working on challenges until the cleanup is finished (hopefully
everything should be ready again tomorrow).
2) make sure that all your work is committed. Use 'git status' for that: if
there are any "modified" files, or any "untracked" files that are part of
your work and should be submitted (e.g. engraving files of your program,
such as .sib or .musx files) you should add them using 'git add filename'
and do a 'git commit'.
3) make sure that all your work is pushed ("uploaded") to your github fork:
first, make sure that 'git status' says "working directory clean". Check
if you have remote repository configured properly ('git remote -v' should
list a remote named 'origin' pointing to your github fork). Use 'git
branch' to see all your local branches (some of you will probably have just
one - master. That'll make things easier :) ). Then, for each branch do
the following:
git checkout branchname
git push origin branchname
And check if you can see your work using GitHub's website.
I apologize for inconvenience.
I'll be at work for the next 9 hours - see you in the evening.
Janek
-------------- next part --------------
An HTML attachment was scrubbed...
|
|
From: Urs L. <ul...@op...> - 2014-01-12 18:59:56
|
Joshua Nichols <jos...@gm...> schrieb: >On Sun, Jan 12, 2014 at 9:56 AM, Urs Liska <ul...@op...> wrote: > >> and probably also expression of Schumann's humour. > > >Or his ensuing madness. ;) I think most of Schumann's music can be seen like this ;-) > >IC, > >Josh -- Urs Liska openlilylib.org |
|
From: Joshua N. <jos...@gm...> - 2014-01-12 18:44:57
|
On Sun, Jan 12, 2014 at 9:56 AM, Urs Liska <ul...@op...> wrote: > and probably also expression of Schumann's humour. Or his ensuing madness. ;) IC, Josh -------------- next part -------------- An HTML attachment was scrubbed... |
