From mboxrd@z Thu Jan 1 00:00:00 1970 From: Neil Jerram Subject: Best practice for providing an Org-based application? Date: Sun, 8 Sep 2019 18:37:49 +0100 Message-ID: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000f0e68f05920e219a" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:38628) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i718W-0005Ax-0M for emacs-orgmode@gnu.org; Sun, 08 Sep 2019 13:38:05 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i718U-0008Sp-9u for emacs-orgmode@gnu.org; Sun, 08 Sep 2019 13:38:03 -0400 Received: from mail-qk1-x730.google.com ([2607:f8b0:4864:20::730]:44456) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i718U-0008S7-1H for emacs-orgmode@gnu.org; Sun, 08 Sep 2019 13:38:02 -0400 Received: by mail-qk1-x730.google.com with SMTP id i78so10695806qke.11 for ; Sun, 08 Sep 2019 10:38:00 -0700 (PDT) List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Org Mode List --000000000000f0e68f05920e219a Content-Type: text/plain; charset="UTF-8" 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 --000000000000f0e68f05920e219a Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Is there a best practice or recommended approach for prepa= ring and providing an Org-based application so that others could make use o= f it?

I've been using Org for a few years to keep tr= ack of the membership and 'fixing' for my choir - where 'fixing= ' means finding out and recording who can sing in each concert, who wil= l be there for rehearsals, and so on.=C2=A0 This involves a mix of data tha= t is private to my choir, and workflows and code that are potentially gener= ic.=C2=A0 I don't know how many people in the world are both choir orga= nisers and Emacs users, but it seems to me that it could be useful to separ= ate out and document the generic code and workflows, so that others could u= se that as well as me, and that it would also be an interesting technical c= hallenge.

Has anyone else done something like this= ?=C2=A0 I wonder if you have recommendations=C2=A0for how to document, stru= cture and publish=C2=A0this kind of thing?

Many th= anks!
=C2=A0 =C2=A0Neil

--000000000000f0e68f05920e219a--