From: John Kitchin <jkitchin@andrew.cmu.edu>
To: emacs-orgmode@gnu.org
Subject: Re: Best practice for providing an Org-based application?
Date: Mon, 09 Sep 2019 12:47:38 -0400 [thread overview]
Message-ID: <m2woehto0l.fsf@andrew.cmu.edu> (raw)
In-Reply-To: <CAKuG=vu78tB-YEbjp0EYvU61DTWFXuS8bU_H7WyQaTTzqe3tdw@mail.gmail.com>
It would be helpful to get a better sense of what is the private data,
e.g. is it something like org-contacts, or some structured data in a
heading? and what are the workflows that might be generic.
I have used org for lots of organizational things in the past, ranging
from conference organization, teaching classes, running job searches,
organizing special issues in scientific publications and lately to
organize some things for a cub scout troop. They have all been pretty
different, but I am sure I have reinvented pieces of it each time. I am
interested in learning more about what you are doing.
Neil Jerram <neiljerram@gmail.com> writes:
> 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
--
Professor John Kitchin
Doherty Hall A207F
Department of Chemical Engineering
Carnegie Mellon University
Pittsburgh, PA 15213
412-268-7803
@johnkitchin
http://kitchingroup.cheme.cmu.edu
next prev parent reply other threads:[~2019-09-09 16:47 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 [this message]
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
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=m2woehto0l.fsf@andrew.cmu.edu \
--to=jkitchin@andrew.cmu.edu \
--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).