From: Gary Thomas <gary@mlbassoc.com>
To: eCos Maintainers <ecos-maintainers@sources.redhat.com>
Subject: Patch policy
Date: Tue, 06 May 2003 12:59:00 -0000 [thread overview]
Message-ID: <1052225944.30126.4370.camel@hermes> (raw)
** 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.
In an ideal world, patches from outside our group would
be posted to a database which could be queried by anyone.
Maybe the easiest way to do this would be to forward the
patch to BugZilla.
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.
I know everyone is busy (or hopefully so!) and this is certainly
not a finger-pointing, but our credibility may be affected.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
next reply other threads:[~2003-05-06 12:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-06 12:59 Gary Thomas [this message]
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
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=1052225944.30126.4370.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-maintainers@sources.redhat.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).