[Improve Existing Best Practice Guide]: Python Starter Kit for Existing Projects
Open
Nobody has claimed this yet.
medium 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
Best Practice Guide Category
Software Lifecycle
Best practice guide URL
Describe the improvement
I'd like to adhere all of our guides, including the Python Starter Kit, to leverage our new infusion strategy "standards as code". See here.
For the Python Starter Kit, this means we should see which elements can be extracted and presented in a way that:
- An existing project can infuse the CI/CD aspects
- SLIM can use the leaderboard infrastructure to push out proposal pull requests for the Python starter kit elements
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 with the Python Starter Kit guide and the linked standards-as-code overview, then inspect the slim-leaderboard infrastructure. Identify which guide elements can support CI/CD infusion into existing projects and which can generate proposal pull requests; done means those extractable elements and integration boundaries are defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100