From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Best practice for providing an Org-based application?
Date: Wed, 18 Sep 2019 21:02:37 +0200 [thread overview]
Message-ID: <87k1a5fmwi.fsf@gmail.com> (raw)
In-Reply-To: CAKuG=vu78tB-YEbjp0EYvU61DTWFXuS8bU_H7WyQaTTzqe3tdw@mail.gmail.com
Neil Jerram <neiljerram@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
prev parent reply other threads:[~2019-09-18 19:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 17:37 Best practice for providing an Org-based application? Neil Jerram
2019-09-08 19:57 ` Marcin Borkowski
2019-09-09 1:01 ` Bob Newell
2019-09-09 16:47 ` John Kitchin
2019-09-10 13:44 ` Jean Louis
2019-09-10 21:49 ` Neil Jerram
2019-09-11 7:11 ` Marcin Borkowski
2019-09-10 21:34 ` Neil Jerram
2019-09-10 23:11 ` John Kitchin
2019-09-11 7:13 ` Marcin Borkowski
2019-09-11 7:35 ` SYOGM Management
2019-09-11 13:58 ` Martin Alsinet
2019-09-18 19:02 ` Thorsten Jolitz [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k1a5fmwi.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).