Hi — Ray here, founder working in an adjacent space around early open-source teams and contributors. Genuine question, not a pitch.
I was reading through Gitdeck and noticed it already connects a few signals that are usually scattered: repo health, traffic/referrers, mentions, dependents, forks sorted by recent push/stars, and the paginated contributors view. The local-token architecture also makes sense for this kind of dashboard, since some of those signals are private enough that I’d hesitate to send them to a hosted service.
One outside observation: for a solo maintainer, Gitdeck is close to showing not just “what needs attention” but “who might be worth paying attention to” — e.g. someone maintaining an active fork, opening repeated issues, showing up in mentions, or depending on the repo.
Question: do you see Gitdeck eventually surfacing those contributor-followup signals directly, or is the intent to keep it as an observability/triage dashboard and leave contributor outreach outside the product?
A short reply is plenty.
Hi — Ray here, founder working in an adjacent space around early open-source teams and contributors. Genuine question, not a pitch.
I was reading through Gitdeck and noticed it already connects a few signals that are usually scattered: repo health, traffic/referrers, mentions, dependents, forks sorted by recent push/stars, and the paginated contributors view. The local-token architecture also makes sense for this kind of dashboard, since some of those signals are private enough that I’d hesitate to send them to a hosted service.
One outside observation: for a solo maintainer, Gitdeck is close to showing not just “what needs attention” but “who might be worth paying attention to” — e.g. someone maintaining an active fork, opening repeated issues, showing up in mentions, or depending on the repo.
Question: do you see Gitdeck eventually surfacing those contributor-followup signals directly, or is the intent to keep it as an observability/triage dashboard and leave contributor outreach outside the product?
A short reply is plenty.