[codemeta-pmc] Governance status update and opening vote from March 15th to 25th

[Morane GRUENPETER]

Dear CodeMeta PMC,

Today, with vlorentz, we have reviewed the PRs and Issues that are candidates for the v3.0 release, available here:

https://github.com/codemeta/codemeta/milestone/9

We have classified the elements into 3 options:

- Option A: If PR/issue needs discussion
- Option B: If PR looks good and changes the spec/schema (v3.0)
- Option C: If PR looks good and doesn't change the spec/schema (v2.1)

We have added comments on the issues and PRs with the mention that discussion will be open until March 15th and we will then proceed to a vote from March 15th to March 25th.

After this date we will move forward with the planing.

🚩Voting is open for the full community.

We have decided that 2 releases are needed with the current state of the repository:

1. release of the 2.1 for the crosswalk changes, which are not breaking the current usage of the v2.0

2. release of the v3.0 which directly changes the vocabulary specifications

👉 If you have comments on this decision please come forward before March 15th (voting day)

To keep on track, here are the items that remain as part of the planning with a few modifications:

(from https://hedgedoc.softwareheritage.org/codemeta-governance?both)

- [ ] 8. [February/March 2023] Governance (1 hour)
    - [ ] create repository codemeta/governance under the codemeta organization
    - [ ] Update the codemeta/codemeta repository (roles + governance documents) => see example here: https://github.com/swhid/governance

    - [ ] Move hedgedoc with governance planing into governance repository

- [ ] 9. [March 2023] Automate the Website CI and content (1PW = 1 person week work)
    - [ ] Update website with information about governance
    - [ ] send email on SciCodes and SCIWG and SSC IG to ask   **inform about policy**
    - [ ] verify with SWH about engineering time

   
- [ ] 10. Decide on an asynchronous meeting to vote on current issues & PR for v3(by all the community)
    - [ ] choose day for review of votes - March 25th 2023 
    - [ ] send email on SciCodes and SCIWG and SSC IG to **ask people votes** and inform about policy (Spread the word about the "voting day")
    - [ ] blog post about CodeMeta community

11. [April] merge PRs for v2.1 (into develop before merging to master)

12.  publish V2.1 release with crosswalk

13. [May/June 2022] merge PRs for v3

14. publish v3 release

15. If results from the voting day needs more discussion
- [ ] Organize an online workshop to finalize open discussions
    - [ ] Suggestion - April 13-14 (as part of the FC4E work)

👉If you have comments on this timeline you can answer this email or add comments in the hedgedoc document.

Any other comment on the content of issues and PR would be best in the codemeta repository.

I will send a PMC reminder to go and vote on the issues on March 15th.

Thank you for your help and engagement.

Kind regards,

--
Morane Ottilia GRUENPETER
Software engineer and project manager
Software Heritage http://www.softwareheritage.org
@INRIA Paris
personal website: http://moranegg.github.io/