Hi Kieren,
Hi Jonas (et al.),
I would claim that the contributor experience has been pretty stable
since the initial switch to GitLab. Enabling CI and the recent work to
also run 'make check' automatically shouldn't change much from a
contributor's point of view, I hope.
I can't promise to give detailed guidance, the procedures should be
described in unstable's CG, but if there's anything unclear or even
wrong I'm more than happy to help you and of course fix the docs.
So here’s what I’ve done, as per
<https://lilypond.org/doc/v2.19/Documentation/contributor/lilydev>:
please use http://lilypond.org/doc/v2.21/Documentation/contributor/lilydev
instead. I adjusted some parts of this section last year. However, I
would be happy to hear
if something remains still unclear.
Cheers,
Michael
1. Download & install VirtualBox. No problem!
2. Download LilyDev 2 from <https://github.com/fedelibre/LilyDev/releases/tag/v2>. Um…
There’s only one file that seems like it’s the downloadable one (LilyDev-2-debian-vm.zip), and
it’s not named as per the docs ("lilydev-vm-fedora-VERSION"). Is that a doc problem,
or am I being daft?
3. Unzip the downloaded file. It becomes a folder containing an .img file. Okay… except
the docs claim it should be a "raw" file. So do I try to convert that to VDI?
Note: I’m on Mac OS High Sierra (10.13.6).
Thanks,
Kieren.
________________________________
Kieren MacMillan, composer (he/him/his)
‣ website: www.kierenmacmillan.info
‣ email: kie...@kierenmacmillan.info
