On 2019-09-08, at 19:37, Neil Jerram <neiljer...@gmail.com> wrote:
> 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? That looks pretty interesting, and I suspect that it could be useful not only for choirs but for other teams as well. I'd love to see this, even though I'm probably not a potential user. Best, -- Marcin Borkowski http://mbork.pl
