-
Notifications
You must be signed in to change notification settings - Fork 945
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
Contribution activity on user page #5298
Comments
I don't see why OSM should look like GitHub. OSM is a map editor, not a social network. What you are proposing is to turn OSM into a social network. The activities you listed can be seen at:
The diagram you provided in the picture is not readable to me at all. There are a lot of symbols and the whole thing is difficult to understand. |
I've successfully implemented this locally and plan to start opening PRs for this soon. The implementation will be completed in stages, with the following plan:
|
Problem
Currently, the OpenStreetMap user profile page lacks a comprehensive contribution activity feed similar to those seen on platforms like GitHub. This means users cannot easily track or showcase their activity across changeset edits, note interactions, diary entries, and GPS trace uploads. This gap limits the visibility of a user's contributions and engagement within the community.
Edit:
After further thought and experimentation, we've decided to focus on an approach that retrieves all user activity directly from the database. This will allow for a more comprehensive and scalable solution.
Here are some activity types we plan to include:
Changesets
Comments
Followers/Following
GPX Files
Issues (for moderators only, requires indexing)
Notes
Moderation (for moderators only, requires indexing)
Additionally, we are refining the design to align with this approach. The new design will reflect these expanded activity types while maintaining a clean and user-friendly interface.
Screenshots
This is the fast mockup i came up with. Could be modified to fit our use case a bit better according to feedback. Thank you.
The text was updated successfully, but these errors were encountered: