Maneage - Tasks: task #16006, CodeMeta file for Maneage
You are not allowed to post comments on this tracker with your current authentication level.
task #16006: CodeMeta file for Maneage
Submitter: | Mohammad Akhlaghi <makhlaghi> | ||
Submitted: | Fri 02 Jul 2021 08:56:27 PM UTC | ||
Should Start On: | Thu 01 Jul 2021 11:00:00 PM UTC | Should be Finished on: | Thu 01 Jul 2021 11:00:00 PM UTC |
Category: | Documentation | Priority: | 5 - Normal |
Status: | In Progress | Privacy: | Public |
Percent Complete: | 20% | Assigned to: | None |
Open/Closed: | Open | Effort: | 0.00 |
Fri 02 Jul 2021 10:41:55 PM UTC, comment #1: |
Mohammad Akhlaghi <makhlaghi>![]() |
Fri 02 Jul 2021 08:56:27 PM UTC, original submission:
To help in preservation, discovery, reuse, and attribution of software, one of the most robust solutions so far is the CodeMeta project, which is also supported by Software Heritage, ASCL and many other initiatives, like the FORCE11. CodeMeta uses the JSON linked data (JSON-LD) notation to store metadata about the software project.
|
Mohammad Akhlaghi <makhlaghi>![]() |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
An alternative approach is to generate codemeta.json automatically from a Maneage'd project's own 'metadata.conf' and Git history. But will need to add all the possibly missing entries of codemeta.json that aren't in our own 'metadata.conf'.
I am just thinking out loud here, so please share your thoughts if you have any :-).