Sebastian Faubel pisze: >> Form my experience, it's almost impossible to come up with a working patch >> when suggesting something significant and especially when requesting a >> feature. >> >> There are often lots of possible ways to implement something and without the >> initial discussion, you get a 95% useless patch, especially if you aren't a >> core developer. > > I agree to the above mentioned - It should not be mandatory to send in a > patch when filing a bug report. However, a patch can often serve as a > concrete starting point for discussion on the mailing list. I mean, that > from a patch people can outline concrete modeling weaknesses and offer > concrete resolutions. One difficulty when designing ontologies is not to > get off topic and stay focused on the problem at hand. I think that this > is what really needs to be addressed.
+1. Discussing a patch is much easier. Even if the initial version is 95% incorrect. We shouldn't require it, because that would alienate potential external contributors. We should seriously encourage it though at least among ourselves. Antoni Mylka [email protected] _______________________________________________ Xesam mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/xesam
