I think that - for non crucial changes, based on personal judgement
;-) - if after a few days (2-3) there are no -1, the change can be done
(lazy consensus). If it is something urgent the time can shorten.
A vote should be called for decisions that we know/feel that are more
arguable.
The point is: if someone is not reading, perhaps because he is
traveling, by definition he will not answer, so it does not make sense
wait for his +0.
Anyway I'm open to change my mind :-) .
Vincenzo
Stefano Bagnara wrote:
Should I better call Votes instead of proposal for this things?
Imho we should try to be more agile than now.. I can't think that for
every single change I have to write the proposal, wait a week to
receive no answers, start a vote, wait at least 3 days..
Stefano
Vincenzo Gianferrari Pini wrote:
Stefano,
we all read the lists, and when I answer I take it seriously.
When I do not answer is because I don't have anything to say and I
consider it like a +0. I would answer with a -1, -0 or +1 if it were
the case. I would answer in any case if it were a vote.
I think that others do the same.
Vincenzo
Stefano Bagnara wrote:
Stefano Bagnara wrote:
So, what do you think? Alternative proposals are welcome: keep in mind
that the goal is being able to make official jspf and mime4j releases
soon with a realistic roadmap.
4 days, 1 answer :-(
What's the problem? Even a +/- 0 would be useful to know that you
read this and you don't have an opinion on this.
Noel: can you please change the svn notification so that it works on
the full james repository? If you have specific options it would be
good if server commits had the server-dev reply-to and the other had
the general reply-to.
Stefano
