Torsten Curdt wrote:
On Wed, Apr 8, 2009 at 05:30, Ian Holsman i...@holsman.net wrote:
guys.
we have a private list to discuss the pro's and con's of people being a
comitter.
keep these personal discussions off the development list. It doesn't help
anyone.
Not sure I agree here. I did not see
+1 for Sandeeps development process suggestions.
In order to address some of the issues brought forward in this thread I
have adapted the following wiki pages from other projects and from
various emails. They could serve as the basis for an initial process.
I think we have a handle on this now. All changes are put on Jira for
review and are not committed until there is at least one +1 from a
reviewer. (I personally prefer post-commit review because manually
attaching and applying patches is tedious but we don't have enough
people following the
The refactoring question seems to be a bit of thorn:
My understanding was that new committers come in and start with some feature
implement that and then slowly start looking into what more they could do
going forward. It is NOT come in and refactor the hell out of the system
because you like
On Wed, Apr 8, 2009 at 6:26 PM, Sandeep Tata sandeep.t...@gmail.com wrote:
I think it is reasonable that a codebase that has evolved for over two
years has significant opportunity for refactoring when it is opened to
a host of new developers. That said, large scale refactoring *at this
stage*
