More generalized way of supporting people...
Open
Nobody has claimed this yet.
Feature request
High priority
- Dominant language
- JavaScript
- Stars
- 806
- Forks
- 434
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 32
Description
Is your feature request related to a problem? Please describe.
When it comes to people, we have situations like the following:
otherLinks: [{
key: 'Quality Assurance Lead',
data: [{
value: 'Wanming Lin (Intel)',
href: 'https://github.com/Honry'
}]
}],
Describe the solution you'd like
What might be nice it to just give people roles. Like:
participants: [
{w3cid: 12312, role: "editor"},
{w3cid: 4444, role: "author"},
{w3cid: 5555, role: "Quality Assurance Lead"},
]
Or:
participants: {
// standardized roles
"editors": [{w3cid: 1111}, {w3cid: 2222, retiredDate: ....}],
"authors": [{w3cid: 2222}],
// Custom roles
"Quality Assurance Lead": [{w3cid: 3333}]
}
These would all render consistently.
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
The issue names no files, tests, or entry points. Start by locating the current otherLinks handling and participant rendering, then choose and document a single participant and role model; done means standardized and custom roles render consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100