Tagging nice GSOC tickets

[michael2402]

We should add a special tag for Tickets that would be suited to be a part of a possible GSOC project.

Criteria for this include:

• Fixing the ticket does not require a deep understanding of how JOSM works internally but only affects one component
• The problem should be solvable in an incremental way (step by step), this makes mentoring easier
• The task should take at least several days to complete
• The use case of the feature should be easily explained to a non-OSM user.

Examples include:

• #7308 - separate component, not deeply related to OSM.
• #5641 - Improvements quickly visible
• #7815 - Window sizing requires quite some try / error but works fine.

This tag will be separate from the Ideas page but helps us at writing some ideas there.
TODOs: Decide on a tag, then tag the tickets.
Timeframe: Before next GSOC

[Don-vip]

Other candidates:

• #6450 - see how we can integrate JOSM with Taginfo
• #6997 - add zoom controls to slippy map
• #3841 - improve validator tooltips

For the tag I suggest "gsoc-candidate"

[Don-vip]

I clearly won't have time to mentor a student this year. Anyone willing to do that? Michael maybe?

[michael2402]

I have time for one student, preferably core (but plugin is also OK). Me and Polyglot are already in contact with potential students.

I did not write any project idea. The only Core topic I could think of at the moment is GPX / Audio marker cleanup.