Policy for adding data loader functions
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 3
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
In principle I think it is good to support as many formats as possible as getting data into the right format can be very frustrating for users. However there will be a limit of what we are willing to maintain as core team members.
Possible solutions
contriborexternalmodule for "community maintained" IO functions vs. "core-team maintained" functions.- ensure formats are reasonably popular (e.g. 5/10 upvotes on the respective issue)
- allow additional dependencies only in exceptional cases
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 by reviewing the issue's proposed approaches for community-maintained versus core-team-maintained IO functions, format popularity, and dependency limits. Done means reaching and documenting an agreed policy for adding data loader functions; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100