Skip to content
This repository was archived by the owner on Jun 15, 2026. It is now read-only.
This repository was archived by the owner on Jun 15, 2026. It is now read-only.

Question on finding early technical contributors for Joggr #41

Description

@flyoung588

Hi — Ray here, founder working in an adjacent devtools/AI-agent space. This is a genuine question, not a pitch.

I was reading through Joggr’s public roadmap/issues. The set of issues around “Secure Agent Access to MCP Integrations,” “Safe Dependency Installs for AI Agents,” “Run AI Agents in Remote Sandboxes,” and “GG: Configurable Workflow Engine” stood out because they are not just feature tickets — they imply a fairly specific mental model of how coding agents should be constrained, configured, and trusted.

My outside read: for a project like Joggr, the hard part in attracting early contributors may not be exposing the roadmap, but getting the right technical people to understand why these constraints matter before they can contribute useful thinking or code.

One question: when you try to find early builders/contributors around Joggr, are GitHub issues and the public roadmap enough, or do you still end up manually looking for people in adjacent repos/communities and explaining the context one-by-one?

A short reply is plenty.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions