On Mon, Feb 13, 2012 at 7:24 AM, Paolo Cavallini <[email protected]> wrote: > Il 12/02/2012 23:15, Larry Shaffer ha scritto: > >> didn't want to break it trying out new ideas (i.e. start doing forks and >> merges). It's my opinion that most new dvelopers won't even need it for most >> small projects. > > -1: I think an SCM is a necessity, to speed up collaboration. E.g., in case > of API breakage, a dev can go round all the plugins and fix them quickly, > whereas waiting for all authors to understand and apply the fix can be very > long.
I share Larry's opinion - for a small one man show project SCM is not necessary. Of course at some stage it is useful to introduce it. Regarding API breakage and fixing plugins by someone else - I do not support that. Even though plugin code may be hosted at hub.qgis, only the plugin author is the real owner of the code - it is not in public domain. Therefore doing some changes without author's permission (and releasing new version on his/her behalf) does not sound good to me. Also from the practical point of view - core developers doing some API breakage will surely not going to update dozens of contributed plugins in order to make them work again. Regards Martin _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
