Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Add microcosms to the website #2390
Microcosms is a feature to support (local) groups of mappers and the events they participate in.
At this time the PR is just for early feedback and discussion.
All of this code is tested using cucumber. To test run bundle install; bundle exec rake cucumber.
Please submit bugs and feature requests at this repo https://github.com/openstreetmap/openstreetmap-website.
Also convert event_attendance controller to event_attendances (plural). diff --git a/app/abilities/ability.rb b/app/abilities/ability.rb diff --git a/app/assets/stylesheets/event_attendances.scss b/app/assets/stylesheets/event_attendances.scss diff --git a/app/controllers/event_attendances_controller.rb b/app/controllers/event_attendances_controller.rb diff --git a/app/controllers/events_controller.rb b/app/controllers/events_controller.rb diff --git a/app/helpers/event_attendances_helper.rb b/app/helpers/event_attendances_helper.rb diff --git a/app/views/events/show.html.erb b/app/views/events/show.html.erb diff --git a/config/routes.rb b/config/routes.rb diff --git a/features/member.feature b/features/member.feature diff --git a/test/controllers/event_attendances_controller_test.rb b/test/controllers/event_attendances_controller_test.rb
@mmd-osm Not yet. But it will be soon. I need to rip out hard coded things for my SotM US presentation.
I created a separate branch to add oauth via osm.org, so people's OSM account will get them into this demo site. I'll create a "deployment" branch and merge these branches together before deploying to my server.
I want to use Docker, but not sure that work is ready to use yet.
Let me know if you all are interested in that omniauth branch. I can push in a separate PR. It's much like the previous one added for wikipedia.
@openbrian : I wouldn't spend too much time on pulling in users from osm.org via oauth, at least in the current development phase. Creating some new test account on the (or some) dev instance looks perfectly fine to me.
Dev site deployments get updated automatically once you push some new commits. That's really helpful for a fast review cycle.
Please don't pollute the commit history with nonsense - if the previous build failed then adding some whitespace to trigger a new one isn't going to fix anything.
If you need help understanding why the build is failing then please ask instead of randomly moving lines around and inserting whitespace.
Likewise if you really need a new build triggering then ask as I can trigger a rebuild without polluting the commit history.
As I was setting up a local Docker container, I thought we could add a few screenshots to highlight how microcosms look like at the moment. So here we go:
List of all microcosms
Details for one microcosm
Creating a new microcosm
Microcosm member list
Edit microcosm member list
List of events
Creating a new microcosm event
Joining a microcosm event