emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: Dan Davison <davison@stats.ox.ac.uk>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>,
	Bastien <bastien.guerry@wikimedia.fr>
Subject: Re: Co-maintainer, a least for some time?
Date: Wed, 19 May 2010 17:46:48 +0200	[thread overview]
Message-ID: <36D3D817-7AE4-4E18-A71B-9675672CC077@gmail.com> (raw)
In-Reply-To: <87bpccqbe4.fsf@stats.ox.ac.uk>


On May 19, 2010, at 3:17 PM, Dan Davison wrote:

> Bastien <bastien.guerry@wikimedia.fr> writes:
>
>> Hi Carsten,
>>
>> Carsten Dominik <carsten.dominik@gmail.com> writes:
>>
>>> Is there anyone who would be willing to step up as a co- 
>>> maintainer, at
>>> least for some time?
>>
>> I'd be glad to help, but I'm short of time for the moment and I  
>> prefer
>> to concentrate on maintaining the server and Worg.
>
> I'm afraid I can't devote significantly more time. (In any case, I do
> not know the agenda and task/time management side of org well enough.)
>
> But I would be happy to help out in a, err, coalition. Would it be
> possible for us to develop a slightly more formalised triage/bug
> tracking system whereby any list member who feels able to can say  
> "I'll
> look into this and report back with a recommendation for
> action". Perhaps this would work via a jointly maintained todo list on
> Worg or elsewhere? Any thoughts? Or is this optimistic and do we  
> really
> need one person to step up?

I think an issue-tracking system would be great.  And if there are  
other people besides John who want to take up individual issues, I am  
sure this would be good.

I will be happy with anything you propose in this direction.  Also I  
know that John is (I think) tracking ledger issues in org-mode - maybe  
we can use his setup in a file that is part of the git repo?

If we have reports continue to come in on the mailing list, then a bug  
tracker could use the message number on gmane as a reference number.   
So the discussions could stay on the list, but negotiation and  
assignment would happen in the tracker.

But - I have no experience with bug trackers, so anything anyone will  
put forward would be an improvement.

- Carsten

  parent reply	other threads:[~2010-05-19 16:23 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 [this message]
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
     [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=36D3D817-7AE4-4E18-A71B-9675672CC077@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=bastien.guerry@wikimedia.fr \
    --cc=davison@stats.ox.ac.uk \
    --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).