From: "Thomas S. Dye" <tsd@tsdye.com>
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: Wed, 19 May 2010 07:01:35 -1000 [thread overview]
Message-ID: <143D63FD-E8F2-4B1C-ABFD-DB11159E53CA@tsdye.com> (raw)
In-Reply-To: <A869ECDE-8131-40F3-95FD-18CBF1F48828@gmail.com>
Aloha Carsten,
From my view on the list it appears you work without a queue, which
seems counterintuitive for a Lisp programmer of Org-mode :) But a
queue for Carsten is not the answer because Org-mode people love the
furious pace of development and would likely chafe at a slow queue.
Perhaps what is needed are community queues for bugs, feature
requests, and patches.
A list of proposed patches would let early adopters try them out.
Once the patches had been tested, early adopters could report their
results to the list. Presumably this would weed out the bad patches,
hone the good ones with flaws, and pass through the gems in good
order. Once the buzz on the list about a patch reached a certain
level and you found time to look at the vetted result, early adopters
could move off their bug-test branches and back onto the main branch.
This organization might maintain the pace of development activity, but
put you in a position of working with a community managed queue at
your leisure.
It is difficult for me to imagine the co-maintainer solution.
All the best,
Tom
On May 18, 2010, at 10:08 PM, 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.
>
> People I know who would be technically able an have enough overview
> over Org include
> a couple of obvious choices
>
> Dan
> Eric
> Bastien
> Nick
> Bernt
> David Maus
> John Wiegley
> Matt, maybe
>
> I may well have overlooked someone else who could do this as well,
> please do not be offended if I left you off this list.
>
> I completely understand if all of you say no, of course - this is
> just an attempt to keep some control of my life :-)
>
> - Carsten
>
>
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Please use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent reply other threads:[~2010-05-19 17:01 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 [this message]
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=143D63FD-E8F2-4B1C-ABFD-DB11159E53CA@tsdye.com \
--to=tsd@tsdye.com \
--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).