Skip to content

Open Proposals: Card Analytics, Hackathon Map & Community Features #631

Description

@ShantKhatri

Summary

We want to open the floor for feature proposals around community and analytics features for DevCard. This is a discussion issue, not a single fixed spec. Multiple ideas are welcome, and the best proposal(s) get priority assignment with the proposer leading implementation.

Contexts

We're looking for proposals in (but not limited to) these areas:

Card Analytics: card owners seeing views, clicks per platform, and which events drove traffic (already scoped in the product roadmap as private-by-default, no third-party sharing).

Upcoming Hackathons Map: a visual map of upcoming hackathons, similar in spirit to developers.events, but focused on hackathons relevant to our community. Could be community-submitted, scraped from Devfolio/Unstop, or both.

Hackathon Winners Archive: a page that holds data on winners of previous hackathons, useful as a showcase and a way to recognize community members who've competed.

Connection Streaks: track meet streaks (how consistently you're meeting new people via DevCard) and "hackathon together" streaks (people who've teamed up across multiple events).

Open to other ideas in this same space, community engagement, gamification, or discovery features. If you have something that fits the spirit of these but isn't listed, propose it.

How this works: comment your proposal with the feature(s) you want to build and a rough plan. We'll review proposals in the weekly call. The best proposal, evaluated on clarity, feasibility, and fit with DevCard's principles (no CRM, no sales tooling, privacy-first), gets priority assignment to implement the feature(s) they planned. You don't need to be the most experienced contributor, a well thought out plan beats a vague one.

Tasks

  • Submit your proposal as a comment on this issue (one feature or several, your choice)
  • Include: what it does, why it's useful, rough technical approach, and any UI sketch if relevant
  • Proposals reviewed in the next weekly community call
  • Selected proposal(s) get split into their own tracked issues with the proposer assigned

Acceptance Criteria

  • At least one proposal selected per feature area (analytics, hackathon map, winners archive, streaks)
  • Selected proposals converted into individual issues with clear scope
  • Proposer assigned to their selected proposal
  • docs updated with the agreed feature scope before implementation starts

Area

shared (cuts across backend, web, and possibly mobile depending on the proposal)

Difficulty

Medium to Hard (varies by proposal, will be re-tagged once split into individual issues)

Metadata

Metadata

Assignees

No one assigned
    No fields configured for Feature.

    Projects

    Status
    Todo

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions