emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Matt Lundin <mdl@imapmail.org>
To: Carsten Dominik <carsten.dominik@gmail.com>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Co-maintainer, a least for some time?
Date: Thu, 20 May 2010 11:17:41 -0400	[thread overview]
Message-ID: <87mxvu61re.fsf@fastmail.fm> (raw)
In-Reply-To: <A869ECDE-8131-40F3-95FD-18CBF1F48828@gmail.com> (Carsten Dominik's message of "Wed, 19 May 2010 10:08:17 +0200")

Hi Carsten,

Carsten Dominik <carsten.dominik@gmail.com> writes:

> I am having a lot of trouble keeping up with everything here in emacs-
> orgmode, in combination with the rest of my life.
>
> Is there anyone who would be willing to step up as a co-maintainer, at
> least for some time?
>
> The tasks would include looking at small patches people submit, making
> decision about whether to apply them, checking copyright issues, and
> applying the patches.  I will be around, so important decisions can be
> deferred to me.

I'm happy to help out as much as my emacs-lisp and git skills allow.
Though others here are far more qualified to serve as an official
co-maintainer, I could try to pick up some of the slack by working on
any bug fixes, issues, patches, etc. you or the co-maintainer might be
willing to delegate.

Speaking of which, I've been meaning to sign papers with the FSF. I'll
do that ASAP.

I, too, vote for some sort of issue tracking system. Perhaps this could
be as simple as some of around us here replying to issues on the list
with an "I'll take a look at this" or "I'll take responsibility for
this." We've all been spoiled by your wonderfully quick and attentive
responses to mailing list posts. Perhaps, however, it's time for the
community to take more responsibility for claiming issues, bug fixes,
etc. within the first 24 to 48 hours of their arrival on the list. If an
issue proves too difficult to solve then the responsible party can defer
to your or the co-maintainer's expertise.

Since this is org-mode, I would prefer to use an org-mode file to track
issues. After all, the Wikipedia article on org-mode highlights its
suitability for "Distributed issue tracking."[1] The challenge, of
course, would be to coordinate this file with the mailing list. Perhaps
we could publish a remember template so that contributors, when claiming
an issue, can easily create a new todo (with a unique id) in the
org-issues file and publish the id in their reply: e.g., "opened and
claimed issue [ID number]." Just an idea...

Best,
Matt

Footnotes:

[1] Org-mode can be used as a distributed issue tracker, by storing .org
files in a distributed revision control system. Developers of the
org-babel extension to org-mode use org-mode in this way to track bugs
and feature requests. http://en.wikipedia.org/wiki/Org-mode

  parent reply	other threads:[~2010-05-20 15:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-19  8:08 Co-maintainer, a least for some time? Carsten Dominik
2010-05-19 12:38 ` Bastien
2010-05-19 13:17   ` Dan Davison
2010-05-19 14:28     ` Eric Schulte
2010-05-19 15:49       ` Carsten Dominik
2010-05-19 15:46     ` Carsten Dominik
2010-05-19 18:08       ` Karsten Heymann
2010-05-19 18:15         ` Matthew Jones
2010-05-19 18:51         ` Anthony Lander
2010-05-19 21:23           ` Carsten Dominik
2010-05-19 21:39             ` Anthony Lander
2010-05-19 21:22         ` Carsten Dominik
2010-05-19 22:30           ` Nick Dokos
2010-05-19 16:24   ` Carsten Dominik
2010-05-19 17:01 ` Thomas S. Dye
2010-05-19 21:41 ` Bernt Hansen
2010-05-20 14:22 ` David Maus
2010-05-20 15:19   ` Carsten Dominik
2010-05-20 16:27     ` Matt Lundin
2010-05-20 21:26   ` John Wiegley
2010-05-20 15:17 ` Matt Lundin [this message]
     [not found] <4bf55eb1.216ae50a.74d1.0bfeSMTPIN_ADDED@mx.google.com>
2010-05-20 17:52 ` Thomas Renkert
2010-05-24 14:50   ` Uday S Reddy

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=87mxvu61re.fsf@fastmail.fm \
    --to=mdl@imapmail.org \
    --cc=carsten.dominik@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).