Feedback from the 2nd Python Tooling Workshop at the ARC festival.
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?
About this one:
should we have a GUI for cookiecutter (I don't know of one already)
... my feeling is almost certainly "no" unless someone makes a cookiecutter GUI. Googling around for "cookiecutter GUI" --perhaps obviously-- leads to a lot of templates for making a GUI, but no actual GUI for the cookiecutter tool.
The main points of opinion voiced in the workshop: researchers and research software developers are going to need to become familiar with the terminal anyway, it's not necessarily "simpler" than just asking questions at a prompt.
If we manage to get
- https://github.com/UCL-ARC/python-tooling/issues/533
I reckon that would satisfy this.
Re: GUI
It would be nice to keep an eye on https://github.com/aryamanjeendgar/CopyCuTTer (TUI for the cookiecutter and copier projects). The project was created as an IRIS-HEP (Scikit-HEP is an IRIS-HEP project) fellow project, but I guess it went unmaintained once the fellow moved on. I see some recent revival activity/efforts in the repository by Henry (scientific-python/cookie's lead maintainer).
It will still be a terminal-based thing, but at least it will be more closer to a GUI.
@all-contributors please add @Saransh-cpp for talk tutorial eventOrganizing. please add @samcunliffe for tutorial. please add @matt-graham for tutorial.
Well my attempt to add multiple people as contributors in a single message failed - not sure if I'm missing something as seems to follow suggested format in docs though.
Just noticed when reviewing contributions list after #575 was merged that Saransh should have additional contributions listed and that we also are missing credits for tutorial development. There are also additional people who should be added for contributing to helping at workshop (not sure if talk or eventOrganizing or both is best?) but wasn't exactly sure who else was there as I didn't manage to make it along 😢.
🫠 yeah Paddy and I found the issue in allcontributors. The docs are lying.
@allcontributors please add @matt-graham for tutorial
How about tagging @allcontributors for each?
@allcontributors please add @samcunliffe for tutorial @allcontributors please add @p-j-smith for tutorial @allcontributors please add @K-Meech for tutorial
Well, this is going to be noisy. Sorry, Kimberly and Paul.
@allcontributors please add @p-j-smith for tutorial
aaaaaaand finally:
@allcontributors please add @K-Meech for tutorial
@samcunliffe
@K-Meech already contributed before to tutorial