Michael Wechner wrote:
Andreas Hartmann wrote:
Michael Wechner wrote:
Andreas Hartmann wrote:
Michael Wechner wrote:
[...]
How can we solve this problem?
by listening to each other and not just doing stuff with high
potential of breaking things without discussing it beforehand. This
is what really destroys a community.
IMO with a CTR policy
what exactly do you mean by CTR
commit then review
I think that's perfect for changes which won't break things, but for
changes with the potential
of breaking things I would suggest RTC (review then commit)
OK - I guess you could add your comment / vote to the guidelines thread:
http://www.nabble.com/-DRAFT-+Lenya+Project+Guidelines-t1590087.html#a4315246
[...]
Maybe the term "broken" should be entirely avoided. We should use the
terms which apply to the actual problem:
- functional problem
- quality problem
- usability problem
- ...
it certainly makes sense to finegrain, but for instance build broken
means to me build failure
(e.g. doesn't compile anymore)
That depends on the circumstances, e.g. which modules and
publications you have included, or maybe the change affected
only a certain operating system.
or publication broken means to me Lenya/Cocoon is throwing an
error/exception.
That depends on which page / screen the exception occurs.
What terms would use for these two situations?
I'd describe the problem as detailed as necessary.
It seems to me that these are the most urgent problems which can be
avoided through review and testing.
OK
[...]
or that
there is a lack of interest.
Yes, that shouldn't lead to the situation that discussions are
avoided. I sometimes dealt with this by lowering my "discuss before
commit" threshold, but I agree that the better way would be trying
to improve the quality and effectiveness of discussions. Any ideas
how to achieve this are appreciated ...
It seems to me that shorter messages are better than longer messages.
OK - but IMO the style of writing isn't as important as the focus
regarding the content.
Also mixing concerns within emails is a problem.
Yes, that's a good point.
Restarting a thread with a summary also should help.
+1
Another point:
Forking a thread if a different discussion emerges from it.
Using good subjects.
+1
-- Andreas
--
Andreas Hartmann
Wyona Inc. - Open Source Content Management - Apache Lenya
http://www.wyona.com http://lenya.apache.org
[EMAIL PROTECTED] [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
