Repository and Spreadsheet Clean up

[germonprez]

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 checking out this workflow, I found a few things that need fixed in Evolution:

Code Changes Commits has broken a few things:

• The overview table at https://github.com/chaoss/wg-evolution/tree/main/focus-areas/code-development-activity is not properly pointing to the correct markdown file.
• The metric (old or new) is not displaying on the website o https://chaoss.community/metric-code-changes/

Change Request Iteration

• The link to the google doc is not accessible – please update

Change Request Comments

• The link to the google doc is not accessible – please update

Change Request Comments Diversity

• The link to the google doc is not accessible – please update

New Contributing Organizations

• The link to the google doc is not accessible – please update

Community Growth Focus Area

• Includes metrics that are marked as ‘considering’ and are crossed out. What does this mean?

[ElizabethN]

@germonprez I'm going to close this, as I think we have addressed this. If this still needs to be tackled, we can re-open!