From: Gary Thomas <gary@mlbassoc.com>
To: Jonathan Larmour <jifl@eCosCentric.com>
Cc: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Re: Patch policy
Date: Tue, 06 May 2003 15:06:00 -0000 [thread overview]
Message-ID: <1052233597.30126.4818.camel@hermes> (raw)
In-Reply-To: <3EB7CE1C.2000300@eCosCentric.com>
On Tue, 2003-05-06 at 09:00, Jonathan Larmour wrote:
> Gary Thomas wrote:
> > ** Disclaimer: I'm sure that I'm as guilty as anyone
> >
> > There seems to be a gap [i.e. failing] in the response to
> > patches from outsiders. Sometimes they are handled quite
> > quickly, sometimes never. I think we need to establish
> > some policies on how to handle these efficiently.
>
> The problem is setting time aside for the large ones. It can take a few
> hours to thoroughly review a large contrib like, say, the new openRISC
> port, even when there are few problems.
>
> If it's any consolation, after 2.0 it's one of my priorities to deal with
> the patch backlog... it's _somewhat_ been put on hold as "net time" for
> now would be better put into 2.0, and FYI we're playing with some release
> candidates here on various hosts so we're getting pretty close on that.
>
> I know it's eCosCentric's view that a proportion of my time will become
> dedicated to net stuff primarily for things like patches.
>
> > At the very least, we should try and assign a patch to
> > a maintainer within some short period of time and then it's
> > that person's responsibility to take care of it - whatever
> > the outcome. As is, I see things come in that I'm comfortable
> > with that sometimes I take up, sometimes I leave by. In the
> > latter case, I simply assume that someone else will handle
> > it. I think this is the failing.
>
> FWIW I've been assuming the final buck passes to me, so unless anyone else
> volunteers it's my problem. I do have every unapplied patch sitting here
> (just in a big pile, but still), but I do have the ability to go back and
> do it. And I still intend to, despite the age of some of the patches now!
Fair enough - I just wanted to see what we can do to formalize this.
I'm more than glad to work on some of these patches, but what I see
right now is that sometimes things get stalled - or at least seem to.
I would not want for everything to fall on your shoulders, certainly
if it makes sense to share the load :-) Whatever we can do to improve
this, especially in the punter's eyes, will be a good thing.
I'm looking at Savannah now, just for my own edification.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
prev parent reply other threads:[~2003-05-06 15:06 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 12:59 Gary Thomas
2003-05-06 13:17 ` Mark Salter
2003-05-06 13:26 ` Andrew Lunn
2003-05-06 13:34 ` Gary Thomas
2003-05-06 13:40 ` Andrew Lunn
2003-05-06 13:44 ` Gary Thomas
2003-05-06 14:51 ` Jonathan Larmour
2003-05-06 14:46 ` Jonathan Larmour
2003-05-07 20:30 ` Jonathan Larmour
2003-05-07 21:54 ` Gary Thomas
2003-05-07 22:48 ` Alex Schuilenburg
2003-05-07 23:02 ` Jonathan Larmour
2003-05-07 23:39 ` Alex Schuilenburg
2003-05-07 23:55 ` Jonathan Larmour
2003-05-08 0:18 ` Alex Schuilenburg
2003-05-08 3:16 ` Jonathan Larmour
2003-05-08 9:45 ` Alex Schuilenburg
2003-05-07 23:27 ` Alex Schuilenburg
2003-05-06 15:00 ` Jonathan Larmour
2003-05-06 15:06 ` Gary Thomas [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1052233597.30126.4818.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-maintainers@sources.redhat.com \
--cc=jifl@eCosCentric.com \
/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.
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).