From: Julien Lepiller <julien@lepiller.eu>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: 35545@debbugs.gnu.org
Subject: [bug#35545] [PATCH] Add josm.
Date: Tue, 18 Jun 2019 14:29:36 +0200 [thread overview]
Message-ID: <20190618142928.528d0b0b@tachikoma.lepiller.eu> (raw)
In-Reply-To: <20190506005353.3c9b20d7@alma-ubu>
Le Mon, 6 May 2019 00:53:53 +0200,
Björn Höfling <bjoern.hoefling@bjoernhoefling.de> a écrit :
> On Sun, 5 May 2019 13:37:09 +0200
> Julien Lepiller <julien@lepiller.eu> wrote:
>
> > > I know JOSM has plugins. Do you know anything about the licenses
> > > of these plugins? Should we/do we need to compile all of them from
> > > sources? Can we stick with the default Plugin-Repository? I'm
> > > thinking about FSDG-compatibility.
> > >
> > > Björn
> > >
> > >
> > >
> >
> > That's a very good question! It doesn't look like they commit to
> > only free software. In fact here is what I found on the website:
> >
> > Note for plugin developers: If you wrote a plugin and want JOSM to
> > find it, it should be enough to add the plugin to the OpenStreetMap
> > Subversion Repository (SVN) and it will automatically appear on this
> > page. If you cannot put your plugin into SVN then edit this page and
> > insert a link to your plugin jar file into the page; after a few
> > minutes your plugin will be downloaded and the MANIFEST file will be
> > used to extract information for the table below.
> >
> > I don't know if that implies being listed at that page only or also
> > in the plugin manager. I don't use plugins, so I didn't notice, but
> > attempting to use one failed anyway:
> >
> > 2019-05-05 11:30:47.967 GRAVE:
> > org.openstreetmap.josm.plugins.PluginException: Une erreur est
> > survenue dans le greffon buildings_tools. Cause :
> > java.lang.ClassNotFoundException:
> > org.openstreetmap.josm.plugins.buildings_tools.BuildingsToolsPlugin
> > org.openstreetmap.josm.plugins.PluginException: Une erreur est
> > survenue dans le greffon buildings_tools
> >
> > I don't know how to load plugins outside of the plugin manager.
> > Ideas?
>
> I could install the buildings plugin successfully.
>
> I have no idea on how to load plugins from outside the manager and
> haven't looked into the code. But the plugins could be of any license
> and/or could at least have unfree (or at least unbootstrappable)
> dependencies. Until we know how to deal correctly with plugins, we
> could disable the plugins-manager?
So I've looked into that, but I haven't seen how to disable the plugin
manager. I've talked to a JOSM developper during State of the Map
France, and he told me every plugin was free software, and if not, it
should be considered a bug, and the plugin will be removed. I think
this is close to the spirit of the FSDG, so we might not have to
disable the manager. WDYT?
I agree it would be nicer to bootstrap plugins properly ourselves, but
at least we won't advertise for non free plugins. I'll try to update to
a newer version before pushing, unless you have more objections.
>
> Björn
next prev parent reply other threads:[~2019-06-18 12:31 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-03 12:58 [bug#35545] [PATCH] Add josm Julien Lepiller
2019-05-03 13:01 ` [bug#35545] [PATCH 01/17] gnu: Add java-signpost-core Julien Lepiller
2019-05-03 13:01 ` [bug#35545] [PATCH 02/17] gnu: Add java-jsonp-api Julien Lepiller
2019-05-05 10:37 ` Björn Höfling
2019-05-03 13:01 ` [bug#35545] [PATCH 03/17] gnu: Add java-jsonp-impl Julien Lepiller
2019-05-03 13:01 ` [bug#35545] [PATCH 04/17] gnu: Add java-xmp Julien Lepiller
2019-05-05 10:52 ` Björn Höfling
2019-05-03 13:01 ` [bug#35545] [PATCH 05/17] gnu: Add java-metadata-extractor Julien Lepiller
2019-05-05 11:07 ` Björn Höfling
2019-05-03 13:01 ` [bug#35545] [PATCH 06/17] gnu: javacc: Install binaries Julien Lepiller
2019-05-04 11:52 ` Ricardo Wurmus
2019-05-04 12:14 ` Julien Lepiller
2019-05-04 17:08 ` Ricardo Wurmus
2019-05-03 13:01 ` [bug#35545] [PATCH 07/17] gnu: Add java-openjfx-build Julien Lepiller
2019-05-03 15:14 ` Nicolas Goaziou
2019-05-04 11:48 ` Ricardo Wurmus
2019-05-04 12:22 ` Julien Lepiller
2019-05-05 22:05 ` Björn Höfling
2019-05-03 13:01 ` [bug#35545] [PATCH 08/17] gnu: Add java-openjfx-base Julien Lepiller
2019-05-03 15:15 ` Nicolas Goaziou
2019-05-04 11:38 ` Julien Lepiller
2019-05-04 21:03 ` Nicolas Goaziou
2019-05-04 11:46 ` Ricardo Wurmus
2019-05-03 13:01 ` [bug#35545] [PATCH 09/17] gnu: Add java-openjfx-graphics Julien Lepiller
2019-05-03 13:01 ` [bug#35545] [PATCH 10/17] gnu: Add java-openjfx-media Julien Lepiller
2019-05-03 13:01 ` [bug#35545] [PATCH 11/17] gnu: Add java-jmapviewer Julien Lepiller
2019-05-05 22:06 ` Björn Höfling
2019-05-03 13:01 ` [bug#35545] [PATCH 12/17] gnu: Add java-svg-salamander Julien Lepiller
2019-05-05 22:07 ` Björn Höfling
2019-05-03 13:01 ` [bug#35545] [PATCH 13/17] gnu: Add java-jboss-transaction-api-spec Julien Lepiller
2019-05-05 22:07 ` Björn Höfling
2019-05-03 13:01 ` [bug#35545] [PATCH 14/17] gnu: Add java-commons-pool2 Julien Lepiller
2019-05-05 22:07 ` Björn Höfling
2019-05-03 13:01 ` [bug#35545] [PATCH 15/17] gnu: Add java-commons-dbcp2 Julien Lepiller
2019-05-03 13:01 ` [bug#35545] [PATCH 16/17] gnu: Add java-commons-jcs Julien Lepiller
2019-05-03 13:01 ` [bug#35545] [PATCH 17/17] gnu: Add josm Julien Lepiller
2019-05-05 22:22 ` Björn Höfling
2019-05-05 10:07 ` [bug#35545] [PATCH 01/17] gnu: Add java-signpost-core Björn Höfling
2019-05-05 11:18 ` [bug#35545] [PATCH] Add josm Björn Höfling
2019-05-05 11:37 ` Julien Lepiller
2019-05-05 22:53 ` Björn Höfling
2019-06-18 12:29 ` Julien Lepiller [this message]
2019-06-18 16:14 ` Björn Höfling
2019-06-20 11:39 ` Ludovic Courtès
2019-11-13 21:52 ` bug#35545: " Julien Lepiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190618142928.528d0b0b@tachikoma.lepiller.eu \
--to=julien@lepiller.eu \
--cc=35545@debbugs.gnu.org \
--cc=bjoern.hoefling@bjoernhoefling.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).