kedro-org / kedro-org/kedro-devrel
Strategy for Kedro developers and contributors
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/kedro-org/kedro/issues/2274 made me remember that not only we have Kedro users, but we also have potential contributors/developers (including both people who want to contribute to the core projects as well as people extending Kedro with plugins). We should have a distinct and explicit comms/docs strategy for contributors, and also think about in what circumstances a Kedro user could become a contributor or the other way around.
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 reading the linked Kedro issue #2274 and this issue's discussion. Define the contributor and developer audiences, including core contributors and plugin authors, and document how users and contributors may move between those roles. Done means an explicit communications and documentation strategy with agreed circumstances and next steps.
Written by the indexing model from the issue text.
Assessment
- Domain
- content, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100