Morane Gruenpeter

Hi @Nosferican, In the [MARC Code List for Relators](http://www.loc.gov/marc/relators/relaterm.html) I only found the following roles that are relative to different roles in the software creation process: > Programmer [prg] >...

@mbjones, @cboettig, I think that the proposition in https://github.com/codemeta/codemeta/pull/241 is good for the v3 as is, do you have any comments on that? It might be a good time for...

Today, during the CodeMeta task force call which is part of the FORCE11 Software Citation Implementation working group we have discussed this issue, including @mfenner, @tmorrell, Shelly Stall, Qian Zhang...

I agree with having the longer term `continuousIntegration`. I would suggest the following definition with an example: > Link to the instance of the continuous integration service for automation workflows...

## open issues that might be suited for V3 evolution - add `review` or `reviewedBy` : https://github.com/codemeta/codemeta/issues/177 - API entry point: https://github.com/codemeta/codemeta/issues/183 - mailing list or `contactPoint` :https://github.com/codemeta/codemeta/issues/166 - link...

When we are ready to move to the CodeMeta v3 or v2.1 we need to add a crosswalk between `v2 -> v3`, like the already existing crosswalk from `v1 ->...

Hi @mbjones I'm very excited about the v3.0. I will review the open issues and try to propose PRs during this month (October 2020). Very interesting links on SOSO and...

I agree both script and table should be in the repository. The idea was to stop accepting PRs on the table itself which can cause major changes in other mappings.

Thank you @RichardWallis for your input, I really like your proposal. Let's keep `developmentStatus` as the name of the CodeMeta term and prepare a proposal for schema.org with an enumeration.

I actually prefer solution A. As a consumer it is easier to identify the contexts used than the CodeMeta terms that were added. So having first the set of contexts...