From One Contributor to an Open Knowledge Network: Building MyZubster's Knowledge Graph, Contributor Passports, and Independent Nodes

Description and use

MyZubster built a public knowledge graph linking GitHub contributions, evidence, and contributor identities to make technical knowledge transparent and reusable.

Problem

Open‑source contributions generate knowledge that is not captured beyond merged pull requests, leaving gaps in understanding what was learned, how it was achieved, and how it can be reused.

Outcome

A public Knowledge Graph now visualizes verified knowledge, contributor identities, and GitHub contributions, enabling transparent discovery and reuse of technical expertise while preserving evidence integrity.

Workflow

• 1. Define Knowledge Card schema with fields for knowledge, declarer, supporting work, evidence, tests, and unverified claims.
• 2. Build Knowledge Card Builder to create and publish cards.
• 3. Deploy MyZubster Node Bridge (Docker + HTTPS) to enable remote contributor environments to exchange structured work.
• 4. Implement API endpoint /api/knowledge-evidence/public to expose only published, public Knowledge Cards.
• 5. Construct graph relationships (Domain–Contributor–Card–Evidence).
• 6. Add public GitHub contributions layer via PR #1453, linking merged or closed PRs to GitHub accounts and domains.
• 7. Curate snapshot of public contributions and maintain selection as projects evolve.

Evidence

A merged pull request tells us that a contribution was integrated into a repository. It does not necessarily explain everything the contributor learned, which methods they used, which challenges they encountered, or how that knowledge might become useful to someone else.

Source

We integrated an interactive public Knowledge Graph through Pull Request #1438.

Source

Today, we integrated an additional contribution layer through Pull Request #1453.

Source