Re: Lilypond issue tracker account request

2016-03-22 Thread Karl O. Pinc
On Tue, 22 Mar 2016 08:25:05 -
"Phil Holmes" <m...@philholmes.net> wrote:

> - Original Message ----- 
> From: "Karl O. Pinc" <k...@meme.com>
> To: <lilypond-devel@gnu.org>
> Sent: Tuesday, March 22, 2016 3:47 AM
> Subject: Lilypond issue tracker account request

> > I'd like an account in the lilypond issue tracker.
> >
> > I'm thinking about someday contributing to lilypond
> > in the area of harp related notation.  

> I believe you can contribute to the tracker without an account: it's
> just that the contributions require moderation.  Could I suggest you
> start like that and see how you progress?

Sure.  Sounds good.  Thanks.

FYI.  I wrote because it was suggested here:
http://lilypond.org/doc/v2.19/Documentation/contributor/git_002dcl#configuring-git_002dcl


Karl <k...@meme.com>
Free Software:  "You don't pay back, you pay forward."
 -- Robert A. Heinlein

P.S.  Is the nettiqute here to reply-all or just reply to the
list?  (Or, I suppose, just reply to the sender?)


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


Re: Lilypond issue tracker account request

2016-03-22 Thread Karl O. Pinc
On Tue, 22 Mar 2016 12:14:37 -
"Trevor Daniels" <t.dani...@treda.co.uk> wrote:

Hi Trevor,

> Karl O. Pinc wrote Tuesday, March 22, 2016 3:47 AM

> > I'd like an account in the lilypond issue tracker.  
> 
> Happy to add you to the Issue Tracker as a Member.
> That allows you to comment on Issues without moderation.
> That's the way to start.
> 
> You'll need to post or send me your SourceForge Username
> so I can set that up.

I am "kpinc" at sourceforge.

>  
> > I'm thinking about someday contributing to lilypond

> Great!  The first step is to post specific issues that
> you have identified to the bug list:
> http://lists.gnu.org/archive/html/bug-lilypond/
> for discussion and to have an Issue created.

Ok.  Thanks.

I take it that this is not required for a doc patch?
I'm thinking I'll send in something simple like that (through
the development pipeline) to get started.


> When you are ready to contribute to a specific Issue,
> post a patch to the bug list.

Ok.

> The first few patches are usually sheparded through the
> system by one of the Devs before you are elevated to
> Developer status.

I am at present way too ignorant of music to be comfortable
with Developer status.

Regards,


Karl <k...@meme.com>
Free Software:  "You don't pay back, you pay forward."
 -- Robert A. Heinlein

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


Lilypond issue tracker account request

2016-03-22 Thread Karl O. Pinc
Hi,

I'd like an account in the lilypond issue tracker.

I'm thinking about someday contributing to lilypond
in the area of harp related notation.  I'd probably
start with the fingering notation.

FYI.  I don't know much music or much harp.  Or much
lilypond.  Harp fingering notation seems to be like
\startGroup ... \stopGroup, or, after
\set Staff.pedalSustainStyle = #'bracket
\sustainOn ... \sustainOff.  Except that the line can be
slanted.  And in some styles the finger numbers are
written so their midpoint falls on the line and the
line is broken.

There seems to be 2 more variations, one where the
line segments on the ends remain at right angles to the
overall line, and are therefore slanted.  And another
style where the line segments at the end are vertical,
independent of the slope of the overall line.

Fingering runs from 1 to 4 with 1 being the thumb.

See also:
http://www.harpspectrum.org/harpworks/composing_for_harp/images/sacred_harp_notation.gif
from
http://www.harpspectrum.org/harpworks/composing_for_harp/composing_for_harp.shtml
for "lots 'o harp notation", most of which seems to
be missing from lilypond.  In the latter link
you can find an example of finger placement notation
in "Writing for the Harp", section 1, "Notation".

I've no idea if I'll every get around to contributing
but am reading through the developer docs and it
can't hurt to get setup for it.  FWIW I've done
FOSS development work with FOSS tools.

Regards,

Karl 
Free Software:  "You don't pay back, you pay forward."
 -- Robert A. Heinlein

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