Re: Tidying-up the Issues DB

[James]

On 26/10/15 11:29, Trevor Daniels wrote:
> Devs, Bug Squad:
>
> Many of the Issues with Status:Started are no longer active, with many not 
> seeing any change for several years.  Following the move of the Issues DB 
> from GC to SF many of the original owners of these Started Issues have not 
> re-registered at SF; indeed many are no longer active on the devel list, and 
> it seems inconsistent for these issues to have a status of Started when they 
> have no Owner.  I'd like to tidy up this situation by reverting these issues 
> to Status:Accepted so they become more obviously available for someone else 
> to select for further work by appearing in the Open (Accepted) list.
>
> To this end I've already reassigned those not seeing any action for over 3 
> years.  Unless I hear objections I'll continue reassigning more recently 
> moribund issues until the Open (Begun) and Open (Patch) lists reflect more 
> closely the issues actually under active consideration.
>
> Comments?

I think you should also be setting the 'owner' if it has any to 'blank'
(if that wasn't already implied) for issues that are 'Started' and have
an 'owner' but have had no activity for a similar amount of time.

I think this may overlap the 'patch-abandoned' discussion - which i
still need to go back a review as part of my Patch Meister duties.

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: My finances for working on LilyPond

[Simon Albrecht]

On 26.10.2015 04:04, Paul Morris wrote:

Maybe “contributing” is a good heading for all these things, i.e. we could have 
a single “contributing” page instead of “help us” and “sponsoring” pages?


‘Contributing’ is the more technical term and to me it’s associated with 
doing actual work on the code. Since this page is directed to all 
_users_ of LilyPond, I’d suggest subsuming the ‘sponsoring’ page under 
the ‘Help us’ page, which latter name is more colloquial and easy.


Yours, Simon

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Tidying-up the Issues DB

[Trevor Daniels]

Devs, Bug Squad:

Many of the Issues with Status:Started are no longer active, with many not 
seeing any change for several years.  Following the move of the Issues DB from 
GC to SF many of the original owners of these Started Issues have not 
re-registered at SF; indeed many are no longer active on the devel list, and it 
seems inconsistent for these issues to have a status of Started when they have 
no Owner.  I'd like to tidy up this situation by reverting these issues to 
Status:Accepted so they become more obviously available for someone else to 
select for further work by appearing in the Open (Accepted) list.

To this end I've already reassigned those not seeing any action for over 3 
years.  Unless I hear objections I'll continue reassigning more recently 
moribund issues until the Open (Begun) and Open (Patch) lists reflect more 
closely the issues actually under active consideration.

Comments?

Trevor


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

fix unwanted capo indication in fret diagrams (issue 272150043 by thomasmorle...@gmail.com)

[thomasmorley65]

Reviewers: ,

Message:
please review

Description:
fix unwanted capo indication in fret diagrams

issue 4644

Adding a condition to do 1+ for capo-fret only if open strings are
absent and capo-fret is not zero

Please review this at https://codereview.appspot.com/272150043/

Affected files (+3, -1 lines):
  M scm/fret-diagrams.scm


Index: scm/fret-diagrams.scm
diff --git a/scm/fret-diagrams.scm b/scm/fret-diagrams.scm
index  
3b0990cf415109a0d52ddb9dfedd05c0a9b802fb..ce96752b6378088ec041b13530e32c409f347c3e  
100644

--- a/scm/fret-diagrams.scm
+++ b/scm/fret-diagrams.scm
@@ -281,7 +281,9 @@ with magnification @var{mag} of the string @var{text}."
 (cons minfret
   (let ((upfret (- (+ minfret my-fret-count) 1)))
 (if (> maxfret upfret) maxfret upfret)
-  (set! capo-fret (1+ (- capo-fret minfret)))
+  (if (not (and (zero? (apply min (map cadr dot-list)))
+(zero? capo-fret)))
+  (set! capo-fret (1+ (- capo-fret minfret
   ;; subtract fret from dots
   (set! dot-list (subtract-base-fret (- (car fret-range) 1) dot-list)))
 (acons 'fret-range fret-range



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

New Dutch PO file for 'lilypond' (version 2.19.26)

[Translation Project Robot]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'lilypond' has been submitted
by the Dutch team of translators.  The file is available at:

http://translationproject.org/latest/lilypond/nl.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

http://translationproject.org/latest/lilypond/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

http://translationproject.org/domain/lilypond.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

The Translation Project robot, in the
name of your translation coordinator.



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

New Dutch PO file for 'lilypond' (version 2.19.26)

[Translation Project Robot]

Hello, gentle maintainer.

This is a message from the Translation Project robot.

A revised PO file for textual domain 'lilypond' has been submitted
by the Dutch team of translators.  The file is available at:

http://translationproject.org/latest/lilypond/nl.po

(We can arrange things so that in the future such files are automatically
e-mailed to you when they arrive.  Ask at the address below if you want this.)

All other PO files for your package are available in:

http://translationproject.org/latest/lilypond/

Please consider including all of these in your next release, whether
official or a pretest.

Whenever you have a new distribution with a new version number ready,
containing a newer POT file, please send the URL of that distribution
tarball to the address below.  The tarball may be just a pretest or a
snapshot, it does not even have to compile.  It is just used by the
translators when they need some extra translation context.

The following HTML page has been updated:

http://translationproject.org/domain/lilypond.html

If any question arises, please contact the translation coordinator.

Thank you for all your work,

The Translation Project robot, in the
name of your translation coordinator.



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: My finances for working on LilyPond

[Federico Bruni]

Il giorno sab 24 ott 2015 alle 13:08, Federico Bruni 
 ha scritto:

3) GITSTATS
The gitstats linked in the sponsoring pages are a great idea but 
they are out-of-date (november 2012). Any chance to keep them 
up-to-date automatically?

Also, I'd rather link to the Authors tab:
http://lilypond.org/~graham/gitstats-3months/AUTHORS.html

gitstats is just a python script. Who has access to the server may 
just set up a cron job to create the stats every X days:

https://github.com/hoxu/gitstats/blob/master/doc/INSTALL


Actually, it can be even run within 'make doc'. I've just run and it 
compiles the stats of 2015 in 40 seconds:


$ time gitstats -c processes=2 -c start_date=1/1/2015 lilypond-git 
lilypond-gitstats-2015

[...]
real0m40.352s

$ du -h lilypond-gitstats-2015
612Klilypond-gitstats-2015

I'll move the discussion to @bug-lilypond


There's already an open issue for this:
https://sourceforge.net/p/testlilyissues/issues/2086/

(just added a comment to make it up-to-date)




___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Paul Morris]

Hi Trevor,

You’re right.  I also just looked closer at the traceback and at the function 
_GetAuthToken in git-cl/upoad.py where things go wrong (line 262).  The doc 
string says that function raises a ClientLoginError for authentication 
problems, and an HTTPError for "some other form of HTTP error”.  And the 
traceback I got ends with an HTTPError, namely 404 not found.  So it sounds 
like it’s may not be a problem with the authentication with google per se, but 
with connecting with google in the first place.

-Paul

> On Oct 26, 2015, at 3:29 PM, Trevor Daniels  wrote:
> 
> Hi Paul
> 
> Looking at the error again it seems to be a problem with authenticating at 
> GoogleCode rather than Allura at SourceForge.
> 
> Trevor
> 
> - Original Message - 
> From: "Paul Morris" 
> To: "James" 
> Cc: "Phil Holmes" ; "Trevor Daniels" 
> ; "lilypond-devel" 
> Sent: Monday, October 26, 2015 6:15 PM
> Subject: Re: Allure and git-cl troubleshooting
> 
> 
> Thanks Trevor, Phil, and James.  I believe I have everything configured 
> correctly.  (I removed my bearer token below, but I just double checked and 
> it’s correct.)
> 
> [lilypond-git (whiteout-style)]$ git cl config
> Rietveld server (host[:port]) [codereview.appspot.com]: 
> Allura server [https://sourceforge.net/p/testlilyissues/issues/]: 
> Allura bearer token (see https://sourceforge.net/auth/oauth/) 
> [***REMOVED***]: 
> CC list ("x" to clear) [lilypond-devel@gnu.org]: 
> 
> -Paul


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Trevor Daniels]

Hi Paul

Looking at the error again it seems to be a problem with authenticating at 
GoogleCode rather than Allura at SourceForge.

Trevor

- Original Message - 
From: "Paul Morris" 
To: "James" 
Cc: "Phil Holmes" ; "Trevor Daniels" 
; "lilypond-devel" 
Sent: Monday, October 26, 2015 6:15 PM
Subject: Re: Allure and git-cl troubleshooting


Thanks Trevor, Phil, and James.  I believe I have everything configured 
correctly.  (I removed my bearer token below, but I just double checked and 
it’s correct.)

[lilypond-git (whiteout-style)]$ git cl config
Rietveld server (host[:port]) [codereview.appspot.com]: 
Allura server [https://sourceforge.net/p/testlilyissues/issues/]: 
Allura bearer token (see https://sourceforge.net/auth/oauth/) [***REMOVED***]: 
CC list ("x" to clear) [lilypond-devel@gnu.org]: 

-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Reasons why a LilyPond-to-MEI conversion should be developed

[Paul Morris]

> On Oct 24, 2015, at 3:02 AM, David Kastrup  wrote:
> 
> The latest is that the project is over and I have a dump of stuff I need
> to integrate into LilyPond before it may be useful.  My motivation to do
> that is so-so as I've not yet seen a cent of the tutor's money yet (and
> no mention whatsoever that there is any intent of or procedure for a
> payout) for the considerable work I put in so far, and there does not
> seem much of a point to ask for it when the code is not yet in LilyPond.
> 
> So it will likely arrive sometime next year.  It's just a starting
> point, anyway, but it uses decidedly different techniques than current
> converters.

Glad to hear that it resulted in code that can be integrated into LilyPond, 
moving things further in this direction.  Sorry to hear that google has not 
paid you yet…  it’s not fair for them to not uphold their end of the deal.  

> Anybody wanting to get that dump and a sketch of how to integrate it is
> welcome.  It's Scheme-only work requiring digging through LilyPond's own
> Scheme internals for existing hooks in order to integrate it into a
> command line utility.

Would it make sense to start an issue for this with a link to the dump or a zip 
file of it?

-Paul
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Tidying-up the Issues DB

[Federico Bruni]

Il giorno lun 26 ott 2015 alle 13:07, Werner LEMBERG  ha 
scritto:



 Many of the Issues with Status:Started are no longer active, [...]


Any progress on moving to Savannah?  Is there a TODO list somewhere?


No progress, as far as I know.

Nobody is willing to work on maintaining an Allura deployment. Josiah 
was the only one who seemed to have the skills and the will to do it, 
but he vanished.





___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Tidying-up the Issues DB

[Trevor Daniels]

James wrote Monday, October 26, 2015 11:54 AM

> On 26/10/15 11:29, Trevor Daniels wrote:
>> Devs, Bug Squad:
>>
>> Many of the Issues with Status:Started are no longer active, with many not 
>> seeing any change for several years.  Following the move of the Issues DB 
>> from GC to SF many of the original owners of these Started Issues have not 
>> re-registered at SF; indeed many are no longer active on the devel list, and 
>> it seems inconsistent for these issues to have a status of Started when they 
>> have no Owner.  I'd like to tidy up this situation by reverting these issues 
>> to Status:Accepted so they become more obviously available for someone else 
>> to select for further work by appearing in the Open (Accepted) list.
>>
>> To this end I've already reassigned those not seeing any action for over 3 
>> years.  Unless I hear objections I'll continue reassigning more recently 
>> moribund issues until the Open (Begun) and Open (Patch) lists reflect more 
>> closely the issues actually under active consideration.
>>
>> Comments?
> 
> I think you should also be setting the 'owner' if it has any to 'blank'
> (if that wasn't already implied) for issues that are 'Started' and have
> an 'owner' but have had no activity for a similar amount of time.

I shall, although the Owner field is almost always blank anyway for these 
moribund issues.  During the migration it was filled in only for those Devs who 
were already registered at SF.

> I think this may overlap the 'patch-abandoned' discussion - which i
> still need to go back a review as part of my Patch Meister duties.

I don't think what I said conflicts with anything we discussed then - I'm just 
getting on  with doing it.  Usually I shall leave the patch status unchanged, 
unless on inspection I think it looks wrong, in which case I shall add a 
comment explaining any change I make.

Trevor

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Tidying-up the Issues DB

[Werner LEMBERG]

 
> Many of the Issues with Status:Started are no longer active, [...]

Any progress on moving to Savannah?  Is there a TODO list somewhere?


Werner

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Reasons why a LilyPond-to-MEI conversion should be developed

[David Kastrup]

Paul Morris  writes:

>> On Oct 24, 2015, at 3:02 AM, David Kastrup  wrote:
>> 
>> The latest is that the project is over and I have a dump of stuff I need
>> to integrate into LilyPond before it may be useful.  My motivation to do
>> that is so-so as I've not yet seen a cent of the tutor's money yet (and
>> no mention whatsoever that there is any intent of or procedure for a
>> payout) for the considerable work I put in so far, and there does not
>> seem much of a point to ask for it when the code is not yet in LilyPond.
>> 
>> So it will likely arrive sometime next year.  It's just a starting
>> point, anyway, but it uses decidedly different techniques than current
>> converters.
>
> Glad to hear that it resulted in code that can be integrated into
> LilyPond, moving things further in this direction.  Sorry to hear that
> google has not paid you yet…  it’s not fair for them to not uphold
> their end of the deal.

Google does not pay the tutors.  They hand the money to the tutoring
organization, in this case GNU, and the default for GNU is to keep it.
A few years ago that was the only possibility.  Purportedly that has
changed, but the information where to apply has not made it past me.
Presumably I need to ask the organizators.

>> Anybody wanting to get that dump and a sketch of how to integrate it
>> is welcome.  It's Scheme-only work requiring digging through
>> LilyPond's own Scheme internals for existing hooks in order to
>> integrate it into a command line utility.
>
> Would it make sense to start an issue for this with a link to the dump
> or a zip file of it?

Maybe.  It's somewhat disorganized right now.  But it won't become more
organized by me sitting on it.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Phil Holmes]

- Original Message - 
From: "Trevor Daniels" 
To: "Paul Morris" ; "Phil Holmes" 


Cc: "lilypond-devel" 
Sent: Sunday, October 25, 2015 9:48 PM
Subject: Re: Allure and git-cl troubleshooting




Paul Morris wrote Sunday, October 25, 2015 9:33 PM


I gave git-cl another try and got the same error from my previous 
message, ending in:


File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
 raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 404: Not Found


Hhm, assuming you've got a bearer token from
https://sourceforge.net/auth/oauth/,
and have set up the full url to the correct page:
https://sourceforge.net/p/testlilyissues/issues/
I don't know what else might be wrong.

We'll have to let Phil have a look.

Trevor



I'd bet it's getting the URL to the correct page right: the one you cite 
above.  The error could be more enlightening, though.  I'd suggest Paul 
checks his URL, and when I have time I'll look at sorting an error trap.


--
Phil Holmes 



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCHES: Countdown for October 29th 2015

[James]

Hello,
Here is the current patch countdown list. The next countdown will be on
October 29th



PUSH:


No patches to Push at this time.





COUNTDOWN:

No patches in Countdown at this time.




REVIEW:


4640 coord-rotate should return exact values for angles like PI/2, etc -
Thomas Morley
https://sourceforge.net/p/testlilyissues/issues/4640/
http://codereview.appspot.com/269530043


___


NEW:

No New patches at this time.




WAITING:


4600 Let notes/rests suppress multi-measure rest grobs - Dan Eble
https://sourceforge.net/p/testlilyissues/issues/4600/
https://codereview.appspot.com/265160043/


3918 Add \alternatingTimeSignatures - Urs Liska
https://sourceforge.net/p/testlilyissues/issues/3918/
http://codereview.appspot.com/97110045


3156 Prevents vertical axis groups with empty skylines - Mike Solomon
https://sourceforge.net/p/testlilyissues/issues/3156/
http://codereview.appspot.com/7311048


3134 Removes the translate_axis call from axis-group-interface
outside-staff positioning.  - Mike Solomon
https://sourceforge.net/p/testlilyissues/issues/3134/
http://codereview.appspot.com/7185044


2643 Attach lilypond source in pdf - Valentin Villenave
https://sourceforge.net/p/testlilyissues/issues/2643/
http://codereview.appspot.com/225040043





James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[James]

Paul

On 26/10/15 15:25, Phil Holmes wrote:
> - Original Message - From: "Trevor Daniels"
> 
> To: "Paul Morris" ; "Phil Holmes"
> 
> Cc: "lilypond-devel" 
> Sent: Sunday, October 25, 2015 9:48 PM
> Subject: Re: Allure and git-cl troubleshooting
>
>
>>
>> Paul Morris wrote Sunday, October 25, 2015 9:33 PM
>>
>>
>>> I gave git-cl another try and got the same error from my previous
>>> message, ending in:
>>>
>>> File "/usr/lib/python2.7/urllib2.py", line 558, in http_error_default
>>>  raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
>>> urllib2.HTTPError: HTTP Error 404: Not Found
>>
>> Hhm, assuming you've got a bearer token from
>> https://sourceforge.net/auth/oauth/,
>> and have set up the full url to the correct page:
>> https://sourceforge.net/p/testlilyissues/issues/
>> I don't know what else might be wrong.
>>
>> We'll have to let Phil have a look.
>>
>> Trevor
>
>
> I'd bet it's getting the URL to the correct page right: the one you
> cite above.  The error could be more enlightening, though.  I'd
> suggest Paul checks his URL, and when I have time I'll look at sorting
> an error trap.


You can re-run git-cl config again in the terminal and check the URL.

James

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Allure and git-cl troubleshooting

[Paul Morris]

Thanks Trevor, Phil, and James.  I believe I have everything configured 
correctly.  (I removed my bearer token below, but I just double checked and 
it’s correct.)

[lilypond-git (whiteout-style)]$ git cl config
Rietveld server (host[:port]) [codereview.appspot.com]: 
Allura server [https://sourceforge.net/p/testlilyissues/issues/]: 
Allura bearer token (see https://sourceforge.net/auth/oauth/) [***REMOVED***]: 
CC list ("x" to clear) [lilypond-devel@gnu.org]: 

-Paul


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel