Calendar heatmap of user contributions on user profile

[kcne]

Problem

The current user profile page provides a detailed summary of contributions but lacks a visual representation of activity trends. A calendar heatmap, similar to GitHub's user contribution calendar, would make it easier to understand user engagement over time at a glance.

Description

I have implemented a working calendar heatmap locally for changesets using the cal-heatmap-rails library for display, querying changesets directly from the database. The heatmap visually displays daily contributions, with color intensity representing the number of changes for the changset on the given date.

Additional Ideas:

• Not sure if we should count changsets only in initial version or add diary entries and note creations/comments as well.

• Since we have dark mode on OSM plan is for that to be reflected on the heatmap as well.

Next Steps:
I’ll open a PR after refining the implementation. In the meantime, I’d love to hear your thoughts and suggestions on this feature and the proposed contribution types.

Screenshots

[AntonKhorev]

cal-heatmap-rails

Version Released:
on Oct 2, 2018

Are you sure about this gem? Looks like all it does is repackaging of (outdated version of) https://github.com/wa0x6e/cal-heatmap.

[maro-21]

The calendar heatmap is already on http://hdyc.neis-one.org.

[tordans]

Ping #5356 which looks like the ambrella issue for this.

[kcne]

cal-heatmap-rails

Version Released:
on Oct 2, 2018

Are you sure about this gem? Looks like all it does is repackaging of (outdated version of) https://github.com/wa0x6e/cal-heatmap.

You were right. In the end I've settled with integrating cal-heatmap js library directly.

The calendar heatmap is already on http://hdyc.neis-one.org.

Well yes, but wouldn't it be nice if the users could access this on the OSM profiles directly? I don't see why not..

Ping #5356 which looks like the ambrella issue for this.

Thanks for suggestion but in the end i ended up just mocking data in the database locally. Since the table is indexed it should not present issues performance wise.

[tordans]

Ping #5356 which looks like the ambrella issue for this.
Thanks for suggestion but in the end i ended up just mocking data in the database locally. Since the table is indexed it should not present issues performance wise.

FYI my ping was meant to link the different issues on the topic of adding features to the profile page together. (Not a comment on the content of this issue.) I think it is good to have separate issues per feature idea but one meta issue on the topic in general that glues those idea into one concept.