Posted by
Andrew Sykes on
May 31, 2006; 2:22pm
URL: http://ofbiz.116.s1.nabble.com/Dev-this-week-s-development-blog-is-done-tp168137p168175.html
David,
On Wed, 2006-05-31 at 13:33 +0200, David Welton wrote:
> I think the distinction really comes down to people being cognizant of
> what they know and don't know - if someone can't be trusted to be
> careful with a portion of code, even after a warning to be careful and
> not stomp on it, they might not be the sort of 'community minded'
> individuals that you want to hand the keys to in any case... ?
The problem with this idea is, that by definition, it's very difficult
to know what you don't know - especially when there's so much to, er,
not know.
It may work out fine, and it would certainly make an interesting
experiment, but it would be a shame if a massive increase in interest
coincided with a lot of muddled revisions, thus negatively impacting
uptake.
Anyway, I'm not opposed to it as a way of working, as I have no hard
evidence to corroborate that position. Do you think that productivity
could be improved or is currently stifled etc?
--
Kind Regards
Andrew Sykes <
[hidden email]>
Sykes Development Ltd
http://www.sykesdevelopment.com
_______________________________________________
Dev mailing list
[hidden email]
http://lists.ofbiz.org/mailman/listinfo/dev