Lester, I agree with you that Wikidata should not contain an object for
everything that OSM may have. I don't believe there should be an entry for
every McDonalds on the planet, or for every artist's work that someone may
decide to include in OSM. But that's up to Wikidata contributors. Lets
ins
Probably what we could do with is a set of guidelines for people organising
mapping groups. This is not policy so much as best practices.
Could this be done before we thrash out a policy?
Thanks John
On 17 Oct 2017 8:27 pm, "Frederik Ramm" wrote:
> Hi,
>
> the results are in!
>
> https://wiki
Hi,
the results are in!
https://wiki.osmfoundation.org/wiki/Data_Working_Group/Results_of_Organised_Editing_Survey_2017
Thank you everyone who participated.
Bye
Frederik
--
Frederik Ramm ## eMail frede...@remote.org ## N49°00'09" E008°23'33"
__
Thank you everyone for the very informative replies. I've decided to
use GPLv3. (And I think the difference between it and MIT is negligible
in practice for this particular use case)
___
talk mailing list
talk@openstreetmap.org
https://lists.openstreetm
Rory, I agree with you - there are always corner cases. And while we
concentrate on the geographical aspect (e.g. "somewhere there might be a
large territory where the tags mean different thing"), the corner case can
actually exist in our own neighborhood, simply because our neighbor
understood s
Hi Safwat,
I thought about your hypothetical, and if someone was using a personally
modified bot for personal use, the AGPL does not impose different
conditions than GPL ("if you modify the Program, your modified version must
prominently offer all users interacting with it remotely..." doesn't app
You could always release it under Mozilla Public License 2.0 and that
explicitely requires people to offer source code.
On Tue, Oct 17, 2017 at 3:01 PM, Nicolás Alvarez
wrote:
> 2017-10-17 13:27 GMT-03:00 Safwat Halaby :
> > I understand that GPLv3 has a loophole in which someone could modify
>
2017-10-17 13:27 GMT-03:00 Safwat Halaby :
> I understand that GPLv3 has a loophole in which someone could modify
> your GPL-licensed code, and then run it on a server which offers some
> service. Since a service is being sent over the wire, and not the
> executable itself, then they can keep their
I understand that GPLv3 has a loophole in which someone could modify
your GPL-licensed code, and then run it on a server which offers some
service. Since a service is being sent over the wire, and not the
executable itself, then they can keep their modified code private. AGPL
prevents this loophole
On 16/10/17 19:49, Tobias Zwick wrote:
Except that's not true. In Ireland "handball" is Gaelic Handball¹
which is a one-on-one game, not a team sport (which is apparently a
different thing²). There are some sport=handball's tagged in Ireland.
Now the tag is clearly wrong, and we need to figur
Hi,
On 17.10.2017 10:32, Yuri Astrakhan wrote:
> The thing is - we have been discussing hypothetical issues so far, not
> the real ones.
Users have been blocked and edits reverted for indiscriminately applying
JOSM's autofixer to large swaths of data. But those who do that are
usually aware that
Polyglot, I don't think there is a substantial **real** problem in JOSM
with the autofixes. And yes, I have worked with JOSM devs and was
impressed at the speed of response.
The thing is - we have been discussing hypothetical issues so far, not the
real ones. And hypothetically, allowing a simp
If there would be real problems with autofixes in JOSM, it's easy to report
those as a bugs or enhancement requests. JOSM's issue tracker may be
antiquated, but it does work and JOSM's developers are very responsive.
If JOSM users who apply these auto fixes would worsen the data, then they
would g
Well, you kind of can fix one with the other - by introducing a better tool
and disabling some of the autofixes in JOSM (very easy to do). A more
complex approach would clearly require a separate topic(s) and a
substantial dev involvement.
P.S. No, https://master.apis.dev.openstreetmap.org/ doesn
> compromise between the two, how about I disable the "embed edit". If
> the query is executed from a link, without the query editor mode, users
> can only view results. But in the power mode, the users can still use
> the tool to write a query they need, test and edit things as they need.
> So
On 17/10/2017 08:29, Tobias Zwick wrote:
Does the dev API have real (=mirrored) data?
It has whatever data you add to it. I've used it in the past to
demonstrate a "different way of mapping something" by copying everything
from live to dev in a small area and then making the changes in that
I get your point, especially regarding the appliance of the JOSM
fix-button as a "by-the-way" fixing.
Though, you can't fix possible issues with of one tool by introducing
another tool. People will not stop using (that feature of) JOSM. That is
why I think, if you think you detected a problematic
>> Anyway, generally, with everyone raising the alarm about this tool, it
>> would be a friendly gesture to either take the tool offline for now or
>> set it to read-only mode
>
> Or have it run on the dev API.
Does the dev API have real (=mirrored) data?
18 matches
Mail list logo
