Use bobtemplates.plone to create Plone addon structure

[erral]

Fixes #20

I had to do the following:

• Add bobtemplates.plone as a dependency of this package so that it is installed to call it.
• Use {{python_package_name}}.addon as the addon name, because bobtemplates.plone requires to use namespaced package names. If this changes in the future, we can change it here too @MrTango

[ericof]

@erral, thanks for this PR.
I was discussing with @jensens about the following:

• Use pipx to run cookiecutter and then mr.bob
• Create a new mr.bob template that follows the same structure we have in cookiecutter (i.e.: one level, no namespaces, already provide sane defaults for languages, and so on...)
• Double check mxdev and Docker integration (as we had small problems with the new plone.org today)

[erral]

regarding the 2nd one, I would modify the actual bobtemplate.plone addon template to remove the namespace requirement and for the sane defaults, perhaps add there in bobtemplates.plone a subtemplate providing them

@MrTango

[MrTango]

@erral i just merged today the fixes from @mamico
namespaces are no longer enforced and also multiple namespaces are working better.
I'll do a release soon.
I still have a PR for forms in the queue, i would like to merge before.

[erral]

Thanks! When the release is ready, I will work on using it in this package, and I will also try to work on a subtemplate following Erico's suggestion

[erral]

See plone/bobtemplates.plone#526 for the starter template.

Right now this package only sets 2 values in the default Plone site it creates: the site title and the default language.

All other things that are created in the generated plone addon package are just empty folders for behaviors, serializers, services, content types, etc. which are already handled by bobtemplates.plone so can be ditched.

[erral]

before merging this, we need to agree in the approach and have the bobtemplates.plone PR merged and a new version released, this way I will update the requirement version for bobtemplates.plone

@MrTango @jensens @ericof

[jensens]

First: thanks a lot!
Some changes before I would merge from my POV:

• use plonecli and avoid using mr.bob directly. We want people to work with plonecli (and improve plonecli for Plone 6).
• use pipx run plonecli create addon instead of adding bobtemplates.plone to the requirements.txt.
• add pipx as the only new to requirements.txt (plan is to use pipx for other tools like isort/black/... in future, so it is good there for now.

[erral]

right now it looks like it is not possible to pass the --config parameter that mr.bob uses to provide default answers in a non-interactive way to plonecli 😕

I'll keep looking at it.

[jensens]

LGTM now. If the other parts are merged and released (plonecli/bobtemplates.plone) this one can be merged too from my POV.

[jensens]

Whats the state here?

[ericof]

I would suggest we sprint on plonecli during Alpine sprint, then merge this

[erral]

There is indeed a PR on plonecli to add a Plone site initializer subtemplate. But it just adds 2 settings site title and languages, and may be it is a bit poor subtemplate to add it to bobtemplates.plone, don't know...

We can neglect that, or improve it if more settings can be added to a site initializer... But I don't see what more can be added there...

[MrTango]

I'll be there too, happy to help ;)

[stevepiercy]

LGTM.

[erral]

Wait for plone/bobtemplates.plone#526 to be merged before this.

[erral]

I have rebased on top of the changes last months... I will need a release for bobtemplates.plone to test this properly.

[jensens]

A bobtemplates.plone release sounds like a task for @MrTango ;-)

[MrTango]

@erral bobtemplates.plone is released in version 6.3.2 now, please test ;)