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

Repository Clean Up #153

Open
germonprez opened this issue Dec 4, 2021 · 2 comments
Open

Repository Clean Up #153

germonprez opened this issue Dec 4, 2021 · 2 comments
Assignees

Comments

@germonprez
Copy link
Contributor

germonprez commented Dec 4, 2021

Hi everyone,

I've been updating the speadsheet that we use to track the develop and release of CHAOSS metrics. I recommend that the DEI WG take on the following tasks to get the work in the repository aligned with the speadsheet and how the other WGs work.

Spreadsheet is available at: https://docs.google.com/spreadsheets/d/1tAGzUiZ9jdORKCnoDQJkOU8tQsZDCZVjcWqXYOSAFmE/edit#gid=0

Ultimately, the workflow should be:

  1. All metrics, in development and releases, should be tracked in the CHAOSS spreadsheet
  2. Any metric that is in progress should only be worked on in a Google Doc (or comparable shared doc). The Google Doc reference is included in the metric's row in the tracking spreadsheet.
  3. Once the metric is ready for release, at GH markdown file is created and the tracking spreadsheet is updated with the GH markdown reference (removing the google doc reference)
  4. If a metric is being reviewed, a new google doc should be created to work on. This new google doc can be tracked in the 'remarks' column of the tracking spreadsheet.

As a result of this, a few things that Risk should attend to:

  • Remove the following metrics from the Security focus area as they should be developed via Google Docs
    o Language Declaration README
    o Language Source Proportion
    o Also, update the table to reflect that these metrics have not been released (just delete the table)

  • Under Licensing, please remove ‘License Count’. It is claimed to be moved on the spreadsheet and it is not listed in the main release.

  • Please update the spreadsheet to reflect any moved dependency metrics from Evolution

@TejasMate
Copy link

Issues Solved:
Removed Language Declaration
Removed Language Source Proportion
Updated README - remove above metrics in table row (not deleted because of OpenSSF Best Practices metric)
Removed License Count and updated Licensing's README

Not solved:
update the spreadsheet to reflect any moved dependency metrics from Evolutiona

@TejasMate
Copy link

TejasMate commented May 11, 2022

@germonprez, dependency metrics going to move in Dependency Risk Assessment or need to create new dependency focus area in Risk spreadsheet?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants