[New Process Improvement Need]: Best practices for external folks' product delivery
Open
Nobody has claimed this yet.
low complexity
requested
software lifecycle
- Dominant language
- JavaScript
- Stars
- 36
- Forks
- 14
- PR merge metrics
- No merged PRs in 30d
Description
Checked for duplicates
Yes - I've already checked
Category
Governance - people, personnel, organization, etc.
Describe the need
We have a need for:
- Process for delivery of algorithms from external Principal Investigators (PIs)
- Process for delivering large static auxiliary datasets from PI's
+1'd from @ira
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 reviewing the issue's two requested process areas: delivery of algorithms from external Principal Investigators and delivery of large static auxiliary datasets. No files, tests, or entry points are named, so first locate the repository's existing governance or lifecycle documentation. Done means agreed, documented processes for both delivery paths.
Written by the indexing model from the issue text.
Assessment
- Domain
- developer-experience, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100