-
Notifications
You must be signed in to change notification settings - Fork 133
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
De-vendor wagtail_flexible_forms #430
Comments
Feel free to take over |
@BertrandBordage that would be helpful. I know some users have commented that they are using coderedcms purely for the flexible form support, so that is something we plan on actively maintaining. I deleted our fork, so can you please transfer to repository to our |
I accepted the invitation, but I'm still getting the same error :\ |
@BertrandBordage I think it was related to some permissions. Can you give it a try now? |
Done! You can remove me from the organization now! |
Received, thank you. I added you as a contributor to that specific repo, so feel free to continue development if you get the itch :) |
Has there been any behind the scenes progress on this? |
Currently we have vendored
wagtail_flexible_forms
by @BertrandBordage in order to provide support and integration within CodeRed CMS.This is fine, however it is an ideal candidate to be split out into a separate pip package. This would be relatively trivial because it is already namespaced within coderedcms. The advantage here is that other wagtail sites could use it, and it could be an optional part of coderedcms.
While I wouldn't want to step on Bertrand's toes by taking over the project, we would have to fork and take over it in order to provide a pip package. Since a pip package was never created that would not technically be a problem.
If anyone has any input, please speak now!
Requirements:
wagtail_flexible_forms
repository (While I would normally want to provide a fork, the code would then not be searchable on github, etc., and the original does not seem to be maintained).The text was updated successfully, but these errors were encountered: