[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can I help porting to python 3?
From: |
Karlin High |
Subject: |
Re: Can I help porting to python 3? |
Date: |
Wed, 22 Jan 2020 11:52:53 -0600 |
User-agent: |
Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.3.1 |
On 1/22/2020 10:20 AM, Arusekk wrote:
I would like to help porting lilypond python scripts to python 3.
There is an ongoing effort in this area, largely by Jonas Hahnfeld. Here
are what I believe to be current references to it.
Link to email thread in lilypond-devel mailing list archive:
<https://lists.gnu.org/archive/html/lilypond-devel/2019-12/msg00156.html>
Issue tracker:
<https://sourceforge.net/p/testlilyissues/issues/5646/>
Code review:
<https://codereview.appspot.com/553420043>
Git branch:
<https://git.savannah.gnu.org/cgit/lilypond.git/commit/?h=dev/hahnjo/python3>
2) is there a policy on how to split changes into commits (or
guidelines, whatever to call it),
3) where to test / send partial commits to,
4) how to file the final version for review and merging.
I can start porting as soon as I know what to start from, and prefer to
use a GitHub fork for my commits and submitting a pull request if it is
up to me to decide.
The LilyPond Contributor's Guide is probably the best reference for
those questions.
WEB:
<http://lilypond.org/doc/v2.19/Documentation/contributor/index.html>
PDF:
<http://lilypond.org/doc/v2.19/Documentation/contributor.pdf>
--
Karlin High
Missouri, USA