plone / plone/container-backend
Do not use own skeletons here, but use `cookiecutter-zope-instance`
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 18
- Forks
- 18
- Avg merge
- 1h 32m
- Merged PRs (30d)
- 2
Description
This cookie-cutter were made for this task, here we have everything twice in several skeleton files.
I think this could be much more streamlined using the cookiecutter-zope-instance - and while at it improve it (I can move it to plone or collective).
The cookie-cutter would need to be installed in the build step together with cookiecutter script.
At startup it can generate the configuration (it takes only some millis).
It is documented (vs. the current READMe has many bugs and is consfusing)
This could probably also help using the image for development.
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
Review the current skeleton files, build step, startup path, and README alongside cookiecutter-zope-instance. Done means removing duplicated skeleton configuration, installing and using the cookiecutter during the build or startup flow, and making the documentation accurate and clearer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, python, shell
- Domain
- build-system, devops, documentation
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100