Feature: Recurring community contribution challenges

[sajeetharan]

Problem

Badges and rankings recognize accumulated activity, but DevGlobe lacks a recurring, achievable reason for the wider community to return and participate together.

Proposed solution

Introduce opt-in weekly or monthly contribution challenges based on verifiable activity from supported sources, with community progress and non-competitive recognition.

Acceptance criteria

• Define an initial small challenge set using metrics DevGlobe can verify reliably
• Show challenge rules, source, time window, progress, and completion state
• Require explicit opt-in and allow participants to leave a challenge
• Verify completion from refreshed contribution data rather than self-reporting
• Avoid rewarding spam, low-quality activity, or raw volume without context
• Keep challenge rewards separate from the core developer score
• Support individual and community-level progress without public shaming
• Handle timezone boundaries and delayed upstream metrics consistently
• Add abuse controls and tests for duplicate or late activity
• Measure participation, completion, and return rates

Retention outcome

Create a lightweight recurring ritual around meaningful community contribution.

Related issues

• Badges and milestones: Badges and milestones system #26
• Coding streaks and achievements: Feature: Coding streaks and achievement badges #46
• Automated contribution refresh: Feature: Automated weekly contribution refresh and score recalculation #124
• Retention analytics: Analytics: Measure engaged sessions and post-card retention #121