New API's for Allinopensource project badging
- Dominant language
- Python
- Stars
- 13
- Forks
- 17
- Avg merge
- 6h 59m
- Merged PRs (30d)
- 1
Description
> [!NOTE]
> Migrated from [augurlabs/augur#2439](https://github.com/augurlabs/augur/issues/2439)
> Originally opened by `@sgoggins` on 2023-06-13
---
**Is your feature request related to a problem? If so, please describe the problem:**
An Augur API (Missouri) is hit by the web system, to submit the repository for report generation (CHAOSS-Africa) Data passed to Augur:
- Project Badging application ID (new "dei_badging" table)
- Project Badging Application Level (new dei_badging" table) [bronze, silver, gold, platinum]
- Repository Link (new dei_badging table AND the usual tables for adding a repo)
- [add a report path column to dei_badging table]
(Put these at the top of collection priority)
(Machine learning workers need to be triggered after collection)
- Clustering
- Discourse Analysis
- Message Insights
- Insight
(Need some kind of flag to know when its done)
```
( In between, Augur performs analysis, and generates a report that makes suggestions based on:
Criteria for the badge level
Analysis of discourse inclusivity compared to similar projects. These comparisons are not shared directly, however, they influence specific recommendations. )
```
When the report is complete, it is made available through a **different** Augur API (Missouri) that is hit by the web application (CHAOSS-Africa). The data will include
- Badging Application ID
- A secure link to the badging application report. [stored in the dei_badging table]
Contributor guide
Assessment
This issue has not been assessed yet.