Modify

Opened 6 years ago

Last modified 6 years ago

#16226 new enhancement

Integrate osm-community-index

Reported by: joostschouppe Owned by: team
Priority: normal Milestone:
Component: Plugin Version:
Keywords: community Cc:

Description

The osm-community-index https://github.com/osmlab/osm-community-index contains many channels to get in touch with local mappers. The implementation in ID is already driving more people to those channels. It would be nice if JOSM mappers are also shown these channels somehow. The structure of the community data is almost identical to the mapping layer index, which is already implemented in JOSM. So it might be relatively easy.
(sorry if this has been posted already or this is the wrong place)

Attachments (0)

Change History (7)

comment:1 by stoecker, 6 years ago

Component: unspecifiedPlugin

That's not a task for the core.

in reply to:  description comment:2 by Don-vip, 6 years ago

Replying to joost.schouppe@…:

the mapping layer index, which is already implemented in JOSM

To get the facts right: ELI was created long after JOSM map index.

comment:3 by glenn@…, 6 years ago

So, if not a task for the core, who's task is it then ? The influx of mappers that start communicating with the local community due to this implemented into ID is very noticable. It would benefit OSM as a whole a lot. Now where do we direct our request to ?

comment:4 by joostschouppe, 6 years ago

@Don-vip, I'm nut sure which fact you are trying to set straight. I just mentioned the Editor-layer-index (ELI) as I understand it is available within JOSM, and that the community index follows the same kind of logic; hence an implementation might borrow some code from there.

@stoecker: this is something you want to show most of all to relative beginners, or to people who aren't naturally inclined to check documentation. So IMHO it would defeat the purpose to implement this as a Plugin

in reply to:  3 comment:5 by stoecker, 6 years ago

Replying to glenn@…:

So, if not a task for the core, who's task is it then ? The influx of mappers that start communicating with the local community due to this implemented into ID is very noticable. It would benefit OSM as a whole a lot. Now where do we direct our request to ?

Whoever finds the time and motivation to write a plugin.

in reply to:  4 comment:6 by stoecker, 6 years ago

Replying to joost.schouppe@…:

@Don-vip, I'm nut sure which fact you are trying to set straight. I just mentioned the Editor-layer-index (ELI) as I understand it is available within JOSM, and that the community index follows the same kind of logic; hence an implementation might borrow some code from there.

ELI is not available within JOSM. ELI is a clone of the JOSM concept.

@stoecker: this is something you want to show most of all to relative beginners, or to people who aren't naturally inclined to check documentation. So IMHO it would defeat the purpose to implement this as a Plugin

JOSM is an editor and no multi-purpose communication plattform. There are already communication channels in JOSM. This here is way too much for the core.

comment:7 by joostschouppe, 6 years ago

JOSM is an editor and no multi-purpose communication plattform. There are already communication channels in JOSM. This here is way too much for the core.

Editors are the one place everyone goes to. OSM documentation and tools are notoriously diverse and spread out. In the case of tags, this is largely solved with presets. In the case of "how to get in touch with local communities" (which everyone who edits outside of their comfort zone needs; and everyone who doesn't follow their local community extremely closesly needs), there is finally a simple, structured source including all the different kinds of channels that are used. Of course we can hope people find this yet-another-website. But I would think that connecting mappers to other mappers is just as important as connecting them to the right tags. In the end, it is these other mappers who define what the correct tags are anyway.

Apart from OSM messages and GeoChat, are there any other communication channels I'm not aware of within JOSM? These two aren't as directly helpfull in finding local groups, but maybe I'm missing something else?

Modify Ticket

Change Properties
Set your email in Preferences
Action
as new The owner will remain team.
as The resolution will be set. Next status will be 'closed'.
to The owner will be changed from team to the specified user.
Next status will be 'needinfo'. The owner will be changed from team to joostschouppe.
as duplicate The resolution will be set to duplicate. Next status will be 'closed'. The specified ticket will be cross-referenced with this ticket.
The owner will be changed from team to anonymous. Next status will be 'assigned'.

Add Comment


E-mail address and name can be saved in the Preferences .
 
Note: See TracTickets for help on using tickets.