dandi / dandi/dandi-infrastructure
Tune and unify copyright statement(s) across components
Open
maintenance
- Dominant language
- HCL
- Stars
- 0
- Forks
- 11
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Description
brought up in https://github.com/dandi/dandiarchive/pull/698
Years: use full range for relevant component development, not just last year.
Copyright "owner": DANDI is too vague. Quite comment accepted (not sure how much legally tested though) practice is to use `{project} Team`. Used IIRC by numpy, jupyter and many others (datalad ;-) ). So I would vote for "DANDI Team"
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.