[codemeta-pmc][scicodes] CodeMeta v3.1 release before summer

[Morane Gruenpeter]

Dear PMC and SciCodes consortium,

First, I would like to thank you for your engagement in discussions and PRs on the CodeMeta repository.

We would like to proceed with a v3.1 release containing non-breaking changes before the summer, and plan a full v4.0 release later on to allow for a broader community review.
Given that multiple infrastructures are now using CodeMeta, it would be considerate to allow sufficient time for discussion — I know some of the proposed changes are awaited.

https://github.com/codemeta/codemeta/pulls

We have created two new labels:

- `breaking`

- `non-breaking`

To help quickly see what can be merged into v3.1 and what needs to wait for a proper v4.0 release.

Feel free to debate in the PRs and issues if a label is not correctly assigned.

You are very welcome to draft 'non-breaking' PRs for v3.1 :-) 

Thank you all for your contributions.

Kind regards, 

--
Morane Ottilia GRUENPETER
Head of Open Science Operations
Software Heritage http://www.softwareheritage.org
@INRIA Paris
personal website: http://moranegg.github.io/

GPG fingerprint  8E3F 627C BDCC 76C3 5C5E  D222 39E0 4DCF F4F2 C486

[Daniel Garijo]

Thanks Morane,

I will push a new PR with the non-breaking changes for https://github.com/codemeta/codemeta/issues/323.

Is there a date you are considering for 3.1?

Thanks,

Daniel

--
You received this message because you are subscribed to the Google Groups "codemeta-pmc" group.
To unsubscribe from this group and stop receiving emails from it, send an email to codemeta-pmc...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/codemeta-pmc/CAL8iZAx-%2BPBHiH67F9wZFXo8oW9UpQ2f03s0%3D3ip2W7QsoU%2Bow%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[Morane Gruenpeter]

Hi Anna, hi Daniel,

Thank you both for your engagement with CodeMeta. 

First for Daniel's question we would like to release 3.1 before summer. For that we need to identify the limite between a breaking and nonbreaking changes. I see there is already ongoing discussions on Open PR.

For Anna, since one of the issues is not about changing the vocabulary but documenting how to use fixed vocabularies, my first intuition would be to ask you to write the How To that could be added on the website. You can start a draft of the structure in the issue, or directly go for a PR on the website repo.

Generally speaking, the website wasn't updated recently and we lack the time to maintain it.

Any contribution there is very welcomed. 

For the process question, when we accept a proposal is is usually after we see some consensus in the issue or PR discussion.

Steps you can do to have that:

1. tagging PMC members or any CodeMeta community members would help get opinions into it. You have our GitHub username in the CodeMeta governance repo.

2. mentioning the issue at the next SciCodes meeting and get people to comment during the meeting.

3. sending email (seperated from this one) to call to action. 

After you see some consensus emerge, you should do a PR. 

I hope this process description helps.

Let me know if something is not clear.

Best,

--
Morane@Tokyo

Might not be with you on the next SciCodes 

I'm not sure what time it is here..