Neil Jerram <neiljer...@gmail.com> writes: Hi,
> Is there a best practice or recommended approach for preparing and > providing an Org-based application so that others could make use of it? > > I've been using Org for a few years to keep track of the membership and > 'fixing' for my choir - where 'fixing' means finding out and recording > who can sing in each concert, who will be there for rehearsals, and so > on. This involves a mix of data that is private to my choir, and > workflows and code that are potentially generic. I don't know how many > people in the world are both choir organisers and Emacs users, but it > seems to me that it could be useful to separate out and document the > generic code and workflows, so that others could use that as well as me, > and that it would also be an interesting technical challenge. > > Has anyone else done something like this? I wonder if you have > recommendations for how to document, structure and publish this kind of > thing? > > Many thanks! > Neil long time ago, but I once started a little project called org-bandbook, its on my tj64 account on github. The interesting part about is its importing funcionality for lilypond songs from another github repo (open book I think), where a guy transposed hundreds of popular standard (real book) tunes to lilypond with some Ruby framework code, which I replaced by ob-lilypond code. The idea was to manage songs, band, concert rehearsals etc in Org-mode, and to be able to easily transpose songs (its ob-lilypond) for Bb or Eb instruments or so. OTOH isn't managing a choir or band quite similar to managing a project, and thus (ob-)taskjuggler would be a very helpful tool here? -- cheers, Thorsten
