I agree that we have a problem. I think that we might need more
committers, to be honest. There are a lot more libraries than there
are people in charge at the moment, so clearly any patch that needs
to get committed will have to go through one of these few people. It
would also be nice to have at least a clear point person for every
library so there's someone to email. I know that we have people in
charge of a few libraries, but definitely not all of them.
Additionally, for those of you who watch the list, if you see someone
post a new patch, please try and take some time to review it once and
a while. It's a lot easier on the committers if the rest of the
community has already given the +1 on the patch.
-Bryan
On Oct 7, 2008, at 7:56 AM, Michael Greene wrote:
Hi,
Unfortunately this is typical of most of the issues, and not
specific to
Python. Pulling up a list of the issues that have been closed
fixed in the
past two months in JIRA [
https://issues.apache.org/jira/secure/IssueNavigator.jspa?
reset=true&&pid=12310800&updated%
3Aprevious=-8w&status=5&status=6&resolution=1&sorter/
field=updated&sorter/order=DESC]
is particularly revealing.
Only two individuals have had issues resolved fixed in the past two
months.
Excluding an issue committed and resolved without any voting or
mailing list
discussion, only one individual has had patches committed in the
last two
months.
Is the project slowing down?
Michael
On Tue, Oct 7, 2008 at 6:00 AM, Terry Jones <[EMAIL PROTECTED]> wrote:
Hi all!
There are at least half a dozen issues in Jira that relate to
Python, all
with patches, but these don't seem to get to the top of the
attention stack
for the Thrift team. Is that right? My apologies if not, it's just
that a
couple of those patches are things I'd like to be using without
needing to
keep a patched local version of Thrift.
There are people who'd be happy to help out, if help is needed/
wanted.
Regards & thanks,
Terry
