Track and capture OWASP contributions across platforms beyond GitHub
- Dominant language
- Python
- Stars
- 451
- Forks
- 702
- Avg merge
- 22h 59m
- Merged PRs (30d)
- 91
Description
> Several years ago, the CycloneDX community used https://orbit.love. They have since been acquired, but their code is still on GitHub https://github.com/orbit-love. It allowed us to measure a wide range of ways that people contribute, including GitHub commits, PRs, issues, discussions, etc, Slack, LinkedIn, Twitter, and YouTube.
>
> It allowed us to see who was coming into our community and at what velocity, who was leaving our community, or was likely to leave. It mapped individuals across all social platforms and (mostly) attributed them to organizations if they worked for one. We could also see which orgs were engaging and disengaging over time.
>
> The only other things we really needed were the ability to monitor Google Docs, Google Meet, and Zoom, and to track contributions in those places. But in the CycloneDX community, many of our contributions do not result in any activity on GitHub. CycloneDX operates as a meritocracy, much like the ASF, and Orbit was a way to identify potential superstars, reward them, and identify where we need to focus some of our efforts.
>
> They were acquired, and the service was decommissioned. There were two other services in this space: one was acquired by LF, the public site was decommissioned, and it was repurposed specifically for LF use. Cannot recall the name of the other company in this space. The goal should be to get contributions from all social channels, including GitHub, Google Docs/Meet, Zoom, Slack, LinkedIn, YouTube, X, etc.
>
> As much as I love Nest, the GitHub-specific measurement approach is a disservice to projects with many forms of contributions and likely has a negative perception from top/core contributors whose contributions are not on GitHub.
_Originally posted by @stevespringett in [#4200](https://github.com/OWASP/Nest/issues/4200#issuecomment-4017572736)_
Contributor guide
Assessment
This issue has not been assessed yet.