emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Carsten Dominik <carsten.dominik@gmail.com>
To: David Maus <dmaus@ictsoc.de>
Cc: emacs-orgmode Mode <emacs-orgmode@gnu.org>
Subject: Re: Co-maintainer, a least for some time?
Date: Thu, 20 May 2010 17:19:19 +0200	[thread overview]
Message-ID: <5809719B-C486-4CED-B69A-2DF238E2608D@gmail.com> (raw)
In-Reply-To: <87hbm2d54x.wl%dmaus@ictsoc.de>

Hi David,

I think this i an excellent idea, and keeping this file on Worg so  
that people can access it on the web and modify it when needed is a  
good idea.

If everyone agrees, then I am glad to accept your offer to start a  
system like this.

Matt, I guess this covers pretty much exactly what you were proposing?

- Carsten

On May 20, 2010, at 4:22 PM, David Maus wrote:

> Carsten Dominik wrote:
>> Dear all,
>
>> 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 do have some time at hand I can spend for maintenance tasks of Org.
>
> As Thomas S. Dye has pointed out in
> [mid:143D63FD-E8F2-4B1C-ABFD-DB11159E53CA@tsdye.com] something that
> seems to be missing in Org development is kind of a queue for open
> issues.[1]
>
> IMO setting up patchwork as a semi-automated tracking system is a good
> idea: As far as I could see from various projects that use patchwork
> it actually /is/ kind of an issue tracker, tracking this special kind
> of issues, patches.  If it is possible the patchwork installation
> should not publish the submitters' mail addresses -- currently the
> submitter's name is displayed with a mailto: link that contains the
> email address.
>
> Tracking patches with patchwork would leave open the question of other
> kinds of issues: Bug reports w/o patches, feature requests, and
> general user questions.  I'll try to track these issues and after I've
> found a suitable work flow maybe put a file with open issues on Worg.
>
> Both systems would form a queue of things to be done: The organizing
> task consists of (a) reviewing non-patch-issues and (b) reviewing open
> patch-issues in patchwork and (c) make decisions (e.g. apply patch,
> comment, etc.).
>
> This is something I volunteer to do.
>
> HTH
> -- David
>
> [1] todo.org in ORGWEBPAGE is definitely out of date (git blame)
>
> --
> OpenPGP... 0x99ADB83B5A4478E6
> Jabber.... dmjena@jabber.org
> Email..... dmaus@ictsoc.de

- Carsten

  reply	other threads:[~2010-05-20 15:19 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 [this message]
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=5809719B-C486-4CED-B69A-2DF238E2608D@gmail.com \
    --to=carsten.dominik@gmail.com \
    --cc=dmaus@ictsoc.de \
    --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).