-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Move this repository to the Plone organisation? #104
Comments
+1 from me |
I'm not aware of a reason not to, unless we wanted to be able to accept contributions from people who have not signed the contributor agreement. Who originally created this repo here? Perhaps they have some thoughts. |
It did for me. Yes, it's easier to create repos in collective, but it is also not super clear what to do once you get to this repo. If you are intuitive, you might go to the GitHub organization page: https://github.com/collective/ There you might see a tiny link in the description to go to https://collective.github.io/ where you can learn what is this collective thing. You will not get this information in the repo's readme: https://github.com/collective/cookiecutter-plone-starter The only potential issue I see is that this repo is under the MIT license https://github.com/collective/cookiecutter-plone-starter/blob/main/LICENSE versus Plone's GPL https://plone.org/foundation/copyright-licensing-logo/license-faq. I know diddly squat about licensing issues when transferring ownership. |
GPL is the default choice for repositories owned by the Plone Foundation, but there is precedent for some repositories being MIT licensed: https://github.com/orgs/plone/repositories?q=license%3AMIT&type=all&language=&sort= -- IIRC that requires approval by the board. |
+1 for me. |
I agree with the move, and I will plan it over the next few days (as we need to make sure the move is well documented and has deprecation warnings for people that still point here) |
I just created the new repository on plone/cookiecutter-plone, which will consolidate all templates. |
This template seems to have or is becoming the offical tool to create a new Plone 6 Setup. Shouldn't we move it to the plone organisation on github? I'm not sure if keeping this in the collective is beneficial to contributions vs. stability.
It could also make people who follow the docs wonder why and what this collective is?
As a comparison, https://github.com/plone/cookiecutter-zope-instance is already under plone (and as essential as this template, because called).
cc: @ericof @sneridagh @mauritsvanrees @davisagli @gforcada @tkimnguyen
The text was updated successfully, but these errors were encountered: