maproulette / maproulette/maproulette-frontend

OSM Teams integration

Open
#2,036 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

discussion enhancement waiting for response
Dominant language
JavaScript
Stars
167
Forks
39
Avg merge
16h 34m
Merged PRs (30d)
11

Description

Hey 👋

At SOTMUS 23, we presented https://mapping.team, OSM Teams v2.0. It allows community managers to organize their mappers into teams, and then integrate those teams into various applications without having to enter a team multiple times. We're currently integrating with the tasking manager https://github.com/hotosm/tasking-manager/pull/5575 and OSMCha in the near future.

After talking with @mvexel I think that we could work on integrating teams with Maproulette. I think we first need https://github.com/maproulette/maproulette3/issues/1876 to be resolved, and then we would need to figure out if we want to do a 1-way sync or a 2-way sync between the Maproulette UI and the OSM Teams API server.

Let us know what you think and how we can help!

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review issue #1876 first, then inspect the MapRoulette UI and the OSM Teams API documentation referenced in this issue. The work is not yet scoped: determine whether team membership should sync one way or both ways, define how the integration should behave, and confirm the approach with maintainers before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
api, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.