> 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
Yes, most of the work should be finished. At this stage testing would
be much appreciated: Basically everything that works in master but
doesn't after applying the patches or compiling dev/hahnjo/python3