UCL-ARC / UCL-ARC/python-tooling
Should we have a `codemeta.json` file in the project/template?
Open
Nobody has claimed this yet.
enhancement
p4-low
task
- Dominant language
- Python
- Stars
- 62
- Forks
- 10
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 6
Description
Is Your Feature Request Related to a Problem? Please Describe
Learnt about this project at RSLondon. You can read more at https://github.com/codemeta/codemeta. The general idea is to standardise the exchange of software metadata across repositories and organisations.
Describe the Solution You'd Like
No response
Describe Alternatives You've Considered
No response
Additional Context
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the Codemeta standard linked in the issue and reviewing how this Python project/template is structured. Determine whether codemeta.json belongs in the template and what metadata it would need. Done means the project has a documented decision and, if accepted, the file is included with suitable template metadata.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100