Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add upcoming events? #25

Closed
bhousel opened this issue Mar 19, 2018 · 11 comments
Closed

Add upcoming events? #25

bhousel opened this issue Mar 19, 2018 · 11 comments

Comments

@bhousel
Copy link
Member

bhousel commented Mar 19, 2018

Some groups will have events (like local State of the Map conference, meetups, etc).
Should we add an upcoming events data to this index so that tools like iD can show the user when the group's next event will be?

@bhousel bhousel added good first issue Good for newcomers and removed good first issue Good for newcomers labels Mar 19, 2018
@mmd-osm
Copy link

mmd-osm commented Mar 20, 2018

Including upcoming events for sure adds lots of value. But there's a bit of history to this topic.... As you probably know https://wiki.openstreetmap.org/wiki/Current_events is the current go to place for OSM related events. WeeklyOSM team already parses this list for automatic inclusion in our weekly news. Would be good to leverage what is available here.

I believe duplication of maintenance effort is to some degree contributing to even more fragmentation in the community. That's why I'm not the biggest fan of adding yet another event calendar infrastructure. If for whatever reason you believe this wiki list is not really suitable for inclusion in iD (in whatever format), could you please make some suggestions on how we could possibly improve it?

I'm not saying the Wiki is perfect (in fact it's really a pain to work with). However, we also have to keep in mind that the Wiki basically allows everyone to add events, no matter or large or small they are, and publishing is immediate without any Pull Request fiddling, etc.. I guess you don't want to grant everyone write & commit access to this repo, which essentially means that we'd be losing a fair amount of flexibility here.

@Nakaner
Copy link

Nakaner commented Mar 20, 2018

@bhousel Are you planning to collect events in a Git repository at GithHub? If so, please keep in mind that the wiki is much easier to use for people who are not developers and don't know who to use Git. In addition, GitHub is not translated into any language which is a huge barrier for participation. Not to mention the privacy problems due to the collection of personal information by GitHub which is not necessary from my point of view to provide such a service.

I don't want to say that we have to stay with the wiki (a very active wiki editor made me thinking about replacing the wiki by something different) but any service which replaces the wiki or parts of it has to be as accessible as the wiki.

@bhousel
Copy link
Member Author

bhousel commented Mar 20, 2018

from @mmd-osm:

However, we also have to keep in mind that the Wiki basically allows everyone to add events, no matter or large or small they are, and publishing is immediate without any Pull Request fiddling, etc.. I guess you don't want to grant everyone write & commit access to this repo, which essentially means that we'd be losing a fair amount of flexibility here.

Actually I probably would accept almost any PR to this repo without really looking at it. If somebody asks "Add our state of the map conference to our group", I'd just do it. I'd also happily grant write and commit access to this repo to anybody who cares to help maintain it.

The success of editor-layer-index proves that this model of contribution works pretty well.

from @Nakaner:

Are you planning to collect events in a Git repository at GithHub?

I was just thinking something simple like this:

{
  "id": "Mapping-DC-meetup",
  "featureId": "dc_metro",
  "type": "meetup",
  "name": "Mapping DC",
  "description": "Improve OpenStreetMap in the DC area",
  "url": "https://mappingdc.org/",
  "contacts": [
    {"name": "Brian DeRocher", "email": "[email protected]"}
  ],
  "events": [
    {"name": "April Meetup", "when": "2018-04-10 18:00", "url": "..."},
    {"name": "June Meetup", "when": "2018-06-12 18:00", "url": "..."},
    {"name": "August Meetup", "when": "2018-08-14 18:00", "url": "..."},
    {"name": "October Meetup", "when": "2018-10-09 18:00", "url": "..."}
  ]
}

iD could add a line for the next event, or nothing if there are no next events. It's also a nice signal that a group is actually active.

This question is more for people who run the community resources - do you want your event to appear alongside to your group in a listing like this? For example, I'm more interested to know if @openbrian finds this useful. I don't have a strong opinion.

@Nakaner
Copy link

Nakaner commented Mar 20, 2018

@bhousel wrote:

Actually I probably would accept almost any PR to this repo without really looking at it. If somebody asks "Add our state of the map conference to our group", I'd just do it. I'd also happily grant write and commit access to this repo to anybody who cares to help maintain it.

The success of editor-layer-index proves that this model of contribution works pretty well.

The editor-layer-index does not have that much changes per month. Have you counted how much events are listed in the calendar of WeeklyOSM? There are about a dozen per month just in Germany!

Sorry, but the idea to use Git(Hub) and centralised editing control (pull requests) will not work for countries where English is not the main language. I agree that the wiki is not ideal from UI point of view. If you want to improve the calendar, write a web application with OSM OAuth to allow users fill out a simple form and the web application render that content as HTML (and provide a machine readable version of it for other services like WeeklyOSM). That would help OSM more.

@bhousel
Copy link
Member Author

bhousel commented Mar 21, 2018

If somebody wants to write a thing to scrape the wiki page and move the events into a more structured format, that would be great, but it's not something I know how to do.

For now I'm just going to add a very simple event array to the resources schema like described above.. We might end up using it, or not.

@mmd-osm
Copy link

mmd-osm commented Mar 21, 2018

If somebody wants to write a thing to scrape the wiki page and move the events into a more structured format, that would be great, but it's not something I know how to do.

Fortunately, WeeklyOSM already have a working solution for this issue:

Wiki page: https://wiki.openstreetmap.org/wiki/Template:Calendar
Parsed result: https://osmbc.openstreetmap.de/calendar/preview

@Nakaner should have a link to the current repo, I don't have it at hand atm.

@Nakaner
Copy link

Nakaner commented Mar 21, 2018

@mmd-osm wrote:

@Nakaner should have a link to the current repo, I don't have it at hand atm.

https://github.com/ThomasBarris/osmcalendar

@wambacher
Copy link

wambacher commented Mar 21, 2018

@bhousel trying to create a calender using GitHub is a nightmare - for all those user, which never ever used github and are not able to.

Editing a wiki page (osm wiki or wikipedia) is well known to many users - github is not.

GitHub is for software development, not for replacing an application.

@bhousel
Copy link
Member Author

bhousel commented Mar 21, 2018

trying to create a calender using GitHub is a nightmare - for all those user, which never ever used github and are not able to.

Agreed - we're not trying to create a calendar!

@wambacher
Copy link

Agreed - we're not trying to create a calendar!

what else?

@mmd-osm
Copy link

mmd-osm commented Mar 22, 2018

@wambacher : I think "We might end up using it, or not." is pretty clear. Let's see what the future brings, if there's lots of momentum in this repo, some sort of import of the existing wiki calendar is likely to happen. I'm still not sure on how to link geoJSON information in the json files with what we have in the Wiki. But that's not a priority for today or tomorrow.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants