On Jan 17, 2008 7:59 PM, Bruce Markham <[EMAIL PROTECTED]> wrote:
> That sounds like *way* too much work in the wrong direction. If we really
> wanted to vote on stuff, I'm sure we could find something pre-packaged for
> the need.
Agreed here. Other people do this stuff, and it doesn't need to be
That sounds like *way* too much work in the wrong direction. If we really
wanted to vote on stuff, I'm sure we could find something pre-packaged for
the need.
Unfortunately, the reality of it is, anything controversial enough needing a
vote, is up to the board. And the board is small enough that t
How about this?
I don't know how the other projects are handling this kind of issues, but
I think we can make a patch management plugin for the Redmine system.
So when a user upload or attach a patch to the system,
system notification is send to the voters. and voters can see a patch if
it's appro
On Jan 13, 2008 11:44 PM, William Lahti <[EMAIL PROTECTED]> wrote:
> Agreed, but certainly exceptions can be made for students who are
> working on academic work. Also, people who are writing good code and
> has a good patch record should get svn access.
>
> It might be a good idea to split off a '
Agreed, but certainly exceptions can be made for students who are
working on academic work. Also, people who are writing good code and
has a good patch record should get svn access.
It might be a good idea to split off a 'stable' branch too.
On Jan 13, 2008 1:43 PM, Bruce Markham <[EMAIL PROTECTE
While I agree with the sentiment of careful commits, the buddy system is not
practical for handling the situation when we have a high level of momentum
from newcomers, and a normal level of activity for current project members,
such as in the last couple of weeks.
People are literally talking in t
I think we need to work on structure for committing to the trunk. We
have a lot of people doing commits, without a lot of peer review
before the patches go in. I think a good idea would be a sort of
"buddy system", where a dev gets another dev's word on the patch
before committing, and in the commi
