Changes between Version 59 and Version 60 of DevelopersGuide/DevelopingPlugins

Timestamp:

2012-02-27T18:23:05+01:00 (13 years ago)

Author:

joshdoe

Comment:

add info about publishing plugins

DevelopersGuide/DevelopingPlugins

@@ -196 +196 @@
  * The perl script [osm:source:applications/editors/josm/i18n/i18n.pl i18n.pl] must be called with a destination directory and the '''.po''' files to create translation data.
 
-== Managing a plugin in OSM SVN ==
-There is an SVN repository for JOSM plugins in the main OSM SVN repository, see [http://svn.openstreetmap.org/applications/editors/josm/plugins/ here]. Note that this repository is different from the [http://josm.openstreetmap.de/svn/ main JOSM SVN repository] which only manages the JOSM core. 
+== Publishing a plugin ==
+The plugin list a user sees ([http://josm.openstreetmap.de/plugin here]) is automatically generated at regular intervals (currently about 10 minutes) from plugin JAR files that are located in [http://svn.openstreetmap.org/applications/editors/josm/dist/ josm/dist] on the OSM.org SVN repository (referred to as "internal" plugins) and from links that are embedded in the [[wiki:Plugins]] page (referred to as "external" plugins). Each method has advantages and disadvantages.
+
+Advantages of hosting code externally:
+* Use VCS other than SVN, such as Git or Mercurial
+* Take advantage of robust features provided by services such as GitHub (forking, pull requests, tickets, change commenting, etc.)
+
+Disadvantages of hosting code externally:
+* Strings are less likely to be [[Translations|translated]] due to reduced visibility
+* Changes in the core aren't likely to be propagated to the plugin unless done so by the plugin author(s)
+* Shortcuts won't be listed in [[DevelopersGuide/ShortcutsList|the overview]] and thus will very likely be used by others
+
+Disadvantages of hosting JAR externally:
+* It is marked as "bad external" in JOSM plugin list
+* There is no automatic history handling for older JOSM versions
+
+=== Managing a plugin in OSM.org SVN ===
+There is an SVN repository for JOSM "internal" plugins in the main OSM.org SVN repository, see [http://svn.openstreetmap.org/applications/editors/josm/plugins/ here]. Note that this repository is different from the [http://josm.openstreetmap.de/svn/ main JOSM SVN repository] which only manages the JOSM core. 
 
 You can easily get write access to the JOSM plugins repository by [http://wiki.openstreetmap.org/wiki/Accounts#SVN_access_.28OSM_software.29 following these steps]. If your plugin should be available for other users too and if you want to integrate it into the JOSM plugin update procedure you should submit it to the JOSM plugins repository. The following [http://svn.openstreetmap.org/applications/editors/josm/plugins/00_README readme file] might be helpful too.
@@ -206 +222 @@
  * Links for JOSM core compatibility are automatically inserted
 
-=== Updating a plugin in SVN ===
+==== Updating a plugin in SVN ====
 
 You have found a bug in a plugin and you are able to fix it. Then your next steps are: