research-software-ecosystem / research-software-ecosystem/content
Entry ownership and editing rights (preservation of)
Open
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 48
- Forks
- 35
- Avg merge
- 19m
- Merged PRs (30d)
- 887
Description
One of many issues around GitHub-based content management for bio.tools.
Contributor guide
No contributing guide indexed for this repository
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 with the linked GitHub-based content management issue (#1) and the repository description of a metadata commons for research software. Determine the intended ownership and editing-rights model for entries, then document the agreed behavior and how it should be enforced; the issue provides no files or tests to run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authorization, content
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100