Tim, I agree. I suggested github because that’s what I’m familiar with, and that’s where Atsuyoshi’s notes are. I had a quick look at the Inkscape Wiki and didn’t see “request access to the source” instructions. Besides, I’d be worried I’d do something wrong and screw stuff up causing more work for the “real” developers ;-).

My thought was that if it were to be got working, send in a patch request. (Launchpad is a little daunting for the casual user!)

I’m looking for the least effort path to try and help and also see a Mac build available long term. I no longer do development regularly, but am willing to try and help out… but have some concerns I might drown in learning the tools/mess up/make work for others before providing anything helpful.

OTOH, the roadmap I found suggests a long-term migration to github and using travis is under consideration. I’m a relative newb with both, but have managed to hook up travis on a trivial project, er, trivially.

Doing this in github might be helpful???

I’ll come back in a couple of days and see where the consensus lies, and help out if I can.

I'd personally rather put effort into helping sort out the official
packaging situation rather than work on a satellite macOS packaging
effort.

Specifically, I'd rather resurrect the old packaging/macos tree that
was removed (http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/15381)
so that it can be worked on. It's a bit annoying that it was removed
rather than just disabling it and letting it to lie fallow in case
people want to work on it. I've got some patches for it that I put on
hold when it went.

I wasn't subscribed to inkscape-devel at the time, so am not clear on
the background/issues/discussion that led up to its removal. If
Martin, ~suv or whoever else could give a summary or link to any
discussion, I'd really appreciate it.

Cheers,
Tim