From: Thomas Martitz <thomas.martitz_at_student.htw-berlin.de>
Date: Mon, 25 Oct 2010 23:57:45 +0200

On 25.10.2010 23:14, Alex Parker wrote:
>
> I think you got no objections after a good number of days, which works for me.
> I suspect the lack of response may slightly be down to the relative lack of
> people with touchscreen targets (although a few have android phones).
>
> Alex


The "no objections" system is the system we always used. Now I'm trying
to test the vote-system which was proposed in the other thread for new
features. I think "no objections" shouldn't be enough to get something
in in this system (except maybe in a few rare cases). In fact I don't
expect objections for this feature, so I would've committed it right
away in the "no objections" system.

But "no objections" often also means that people cannot/don't want to
comment because they don't feel familiar enough with the corresponding
code. Should we wait for people who feel familiar and comfortable enough
to vote or should be perhaps ask a few people directly in order to get
the vote (and explain the problem/feature to them)?

But I think since we're talking about new features (which also implies
new code in most cases) here familiarity with the code isn't necessarily
to give an opinion or even a vote. Voting also doesn't mean code review,
it's just a +1 or -1 on the feature.
For bug fixes on the other hand familiarity with the code is more
important, and hence the vote system not suitable.

Best regards.
Received on 2010-10-25