Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

✨Creating the Scorecard Universe ✨ #4073

Open
10 of 17 tasks
justaugustus opened this issue May 1, 2024 · 3 comments
Open
10 of 17 tasks

✨Creating the Scorecard Universe ✨ #4073

justaugustus opened this issue May 1, 2024 · 3 comments
Assignees
Labels
area/community Used for adding contributors, community outreach, etc. kind/docs Improvements or additions to documentation

Comments

@justaugustus
Copy link
Member

justaugustus commented May 1, 2024

With the recent adoption of the Scorecard project charter, we as @ossf/scorecard-maintainers / Steering Committee have a few administrative tasks that need to be completed.

Each heading here will be broken into separate tracking issues, but consider this the umbrella issue for the Scorecard Universe (affectionately coined by @SecurityCRob).

(Note that this items are a rough copy/paste from this week's maintainer's meeting (2024-04-30) and are subject to change as we build out the governance story.)

Project & Steering Committee formation

Adopting Allstar

Adopting Monitor and API Visualizer

  • Turn on DCO
  • Relicense Monitor to Apache 2.0
  • Rename repos, develop naming conventions?

OpenSSF Project Lifecycle

  • Apply for appropriate status in OpenSSF project lifecycle

cc: @afmarcum

@justaugustus justaugustus added kind/docs Improvements or additions to documentation area/community Used for adding contributors, community outreach, etc. labels May 1, 2024
@justaugustus justaugustus self-assigned this May 1, 2024
@justaugustus
Copy link
Member Author

Follow-up items from today's Scorecard meeting:

  • Will anyone be joining from Scorecard Monitor and Scorecard API Visualizer? Yes, once the tasks outlined in the issue are underway, those maintainers will be pulled in more.
  • Approval and permissions will be separated by area of expertise (re: GitHub permissions)

@afmarcum
Copy link
Contributor

afmarcum commented May 8, 2024

Adopting Allstar
How do we make this official?

From Slack discussion with @justaugustus and @SecurityCRob: Informing the WG is all that is needed.

Once the group is ready, submit issues in the Best Practices WG and Securing Critical Projects WG repos informing of the change. Probably need one in the Allstar repo too, if there isn't one already referencing this issue.

Notify operations@openssf.org to update foundation content as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/community Used for adding contributors, community outreach, etc. kind/docs Improvements or additions to documentation
Projects
Status: In Progress
Development

No branches or pull requests

2 participants