Improve OWASP Nest member ranking algorithm with calculated scores

Community & Support: [LinkedIn Group](https://www.linkedin.com/groups/14656108/) · [Slack #project-nest](https://owasp.slack.com/archives/project-nest)

Active project leaders: Arkadii Yakovets -- [GitHub](https://github.com/arkid15r/) · [LinkedIn](https://www.linkedin.com/in/arkid15r/) · [Slack](https://owasp.slack.com/team/U060W3NKLTF); Kate Golovanova -- [GitHub](https://github.com/kasya/) · [LinkedIn](https://www.linkedin.com/in/kate-golovanova/) · [Slack](https://owasp.slack.com/team/U07PWB1JZ6Z)

[Contributing](https://github.com/owasp/nest/blob/main/CONTRIBUTING.md) · [Code of Conduct](https://github.com/owasp/nest/blob/main/CODE_OF_CONDUCT.md) · [GSoC Mentors](https://github.com/owasp/nest/blob/main/MENTORS.md)

---

**Describe the solution you'd like**

The current OWASP Nest member ranking is based solely on the number of contributions. While this provides a simple metric, it does not fully reflect the variety of ways community members contribute to the OWASP ecosystem.

Many contributors support OWASP through leadership roles, cross-project involvement, and consistent activity over time. The ranking system should better represent these broader forms of impact.

This issue proposes improving the member ranking algorithm by incorporating additional OWASP community-related factors and adding technical support for a calculated score that can be used for sorting in both the API and Algolia search results.

**Areas to Consider**

* **Community leadership roles**

* Chapter leadership
* Project leadership
* Committee participation
* Board involvement

* **Contribution recency**

* Recent and consistent activity vs. large numbers of contributions made many years ago

* **Breadth of contribution**

* Number of repositories or projects contributed to
* Participation across multiple OWASP entities (chapters, projects, committees, etc.)

* **Contribution types**

* Code contributions
* Release creation (may carry higher weight than a regular contribution)
* Other meaningful project activities

* **Consistency over time**

* Regular contributors vs. one-time bursts of activity

**Technical Implementation Notes**

* Introduce a new field in the `Member` model (e.g., `calculated_score`) that stores the computed ranking score.
* Recalculate this score during each GitHub data sync.
* Use the `calculated_score` for sorting members in the API responses and in Algolia search results.
* Ensure the scoring algorithm is flexible to incorporate new weighting factors as the community provides feedback.

**Goal**

Develop a more balanced and meaningful member ranking approach that better reflects both technical contributions and broader community involvement within OWASP, while supporting consistent sorting in APIs and search.

**Discussion**

Community input is welcome to determine which factors should have the most weight and how recency, leadership, breadth, and contribution type should influence the final score.

**Are you going to work on implementing this?**

- [ ] Yes
- [x] No

**Additional context**

https://nest.owasp.org/members