Neil Chue Hong

For example: - Volunteers: useful for doing initial versions of new features, or maintaining specific non-critical components - Grants: useful for initial stages of development, but harder to use for...

The [DOAP schema](http://usefulinc.com/ns/doap) supports both "mailing-list" and "support-forum" (as well as "developer-forum". In the schema.org [SubscribeAction definition example](http://schema.org/SubscribeAction) of subscribing to a mailing list, the mailing list is identified as...

I think this is one case where I think we just need to try this out in implementations and see what does or doesn't work? I agree that we don't...

I think from a citation point of view, language version is not important when referencing software. In fact I might go as far as saying that programming language is not...

I think it makes sense to have it as a role, under author. In many cases, knowing the list of authors is enough, but this enables information around roles (and...

It feels to me that Solution C is conceptually the right approach - particular if we see CodeMeta as sitting in a larger ecosystem of description for research objects and...

Ideally, the `codemeta.json` file would be the record, and a `CONTRIBUTORS.md` human-readable version would be auto-generated from this via appropriate tooling / scripting (with appropriate note that new entries revisions...

I note that this is a good test (eating our own dog food) of whether the barrier to editing `codemeta.json` for small tasks likely to be done by non-core contributors...

@mikej888 did some work for the Software Sustainability Institute looking at citing software in traditional outputs: http://software.ac.uk/so-exactly-what-software-did-you-use This includes a summary of what various journals ask for, as well as...

_Disclosure: I work for the Software Sustainability Institute, which has been working on best practice for citation of software and as part of this I collaborate with DataCite, one of...