Hi Florian, I don't see disadvantages when a plugin moving from http://svn.openstreetmap.org/applications/editors/josm/plugins to https://github.com/JOSM as long as it is added as svn:externals to the original SVN repository (mainly for I18n updates and breaking core changes). Run `svn propget svn:externals http://svn.openstreetmap.org/applications/editors/josm/plugins` to see other plugins managed in this respect.
For distributing the compiled plugin, there are different approached: Plugins like continuosDownload and tofix still commit the jar files to http://svn.openstreetmap.org/applications/editors/josm/dist, whereas shapetools uses GitHub releases https://github.com/JOSM/ShapeTools/releases and https://josm.openstreetmap.de/wiki/PluginsSource Cheers, Simon On Tue, Sep 20, 2016 at 3:45 PM, Florian Schäfer <flor...@schaeferban.de> wrote: > Hi everybody, > I'm one of the maintainers of the josm-mapillary-plugin and we are currently > considering to remove that plugin from the SVN-repo and host it on GitHub > only. > Currently we are developing using git and then sync with the SVN-repo using > git-svn. Because nobody of us really needs SVN, it just adds complication to > the workflow without much benefit. > > The DevelopersGuide for plugins states several disadvantages of hosting code > and JARs externally. But then it also states, that it's not as bad if the > plugin is developed in the JOSM account. Which of the listed disadvantages > would still hold true and which wouldn't? > Are there any extra steps needed except transferring the repo to the > JOSM-account and deleting the directory and JAR from the SVN-repo? > > Cheers, > Florian _______________________________________________ josm-dev mailing list josm-dev@openstreetmap.org https://lists.openstreetmap.org/listinfo/josm-dev
