Hi! I just want to think public about this "forking" plugins problem:
IMHO if the "old" functionality is preserved and the plugin is extended and has the same functionality plus a little (a lot) more.. than it would be good to contact the maintainer and collaborate with him.. If the old functionality is gone and it is a pretty much new plugin I'd vote to create a new plugin and give credits to the "inspirator" of the former plugin with "based on the plugin xyz created by" .. just my 2¢ kind regards Werner On Wed, Mar 7, 2012 at 9:24 AM, <[email protected]> wrote: > On Wed, 07 Mar 2012 09:03:46 +0100, Paolo Cavallini wrote: >> >> Il 07/03/2012 01:57, Alex Mandel ha scritto: >>> >>> There are a few questions I'm not sure about: >>> Should the name be changed so both plugins can exist side by side? >> >> I think this would be very confusing for users, and should be avoided >> if possible. >> The best option is always collaborating, and avoid forking a project. > > > +1 for that > > Boris, could you please review the changes and then merge them into your > plugin ? For me it would be better to update one plugin than adding a new > one to our internal qgis' package and explain the difference to the users. > > _______________________________________________ > Qgis-developer mailing list > [email protected] > http://lists.osgeo.org/mailman/listinfo/qgis-developer _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
