----- Original Message ----
> From: David Reiss <[email protected]>
> To: [email protected]
> Sent: Thu, August 12, 2010 11:07:13 PM
> Subject: Re: time for a reboot?
>
> > While it's convenient to keep discussion and issue all happening in
> > jira,
> I certainly agree with that.
>
> > sometimes that cuts against having multiple people involved.
> Do you have a sense for why that is? I think switching to the mailing list
>for
> code reviews would be a pain, and I'd rather fix whatever problem prevents
>people
> from contributing to JIRA discussions (or switch to a real code review tool)
> than just toss it.
Well I'm not suggesting you toss JIRA discussions, but once the
assignee decides to commit the patch perhaps that person should
follow-up to the commit message on the dev list to ask folks to
review it for correctness, potential for improvement, etc.
Soliciting reviews is a nice idea I've seen done well in the
Subversion project.
A reviewboard instance is in the works at Apache so perhaps that
will help as well, but anything that gets people here to discuss
the thrift code is a good thing. The idea is to slowly attract
comments from non-committers to get their opinions and gradually
increase their interest in development. Building a community
takes time and effort, it doesn't just happen because the project
is at Apache.
