UCL-ARC / UCL-ARC/python-tooling
Feedback from the 2nd Python Tooling Workshop at the ARC festival.
Open
Nobody has claimed this yet.
enhancement
help wanted
investigate
question
- Dominant language
- Python
- Stars
- 62
- Forks
- 10
- Avg merge
- 7d 6h
- Merged PRs (30d)
- 6
Description
Just noting down comments from attendees so we don't lose/forget them.
- could we do all of this in
brewor something? - should we make the
ghcommand private by default (I think no) - if no (above) should we add a warning about making code public?
- should we have a GUI for
cookiecutter(I don't know of one already) - #559
- #560
- should we add an option to Dockerise the package?
- should we remove the
ghinstall from the tutorial?
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 workshop feedback and linked issues #559 and #560, then inspect the tutorial's use of the gh command and cookiecutter workflow. Separate the brew, GUI, Docker, warning, and gh-install questions into scoped decisions; done requires maintainer agreement and actionable follow-up for each accepted change.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, github, python
- Domain
- devops, documentation, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100