-
Notifications
You must be signed in to change notification settings - Fork 9
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
RFC: Write GPL compliant plugin called Secure Custom Fields #9
Comments
Thank you for writing this up and I appreciate the thought and consideration here. IMO, in an ideal space, such a solution would live in Core rather than as a separate plugin, even if it is behind some constant (e.g. multisite). In the Site Editor world, there is quite a bit that people could build without any plugins if they could register their own post types and meta fields, then use the site editor to add template items as needed. Some of the points above are out of the scope of my station, though, I think many are very attainable. |
Seems like the main point of this ticket is to try and be a thorough, positive and constructive way of saying that - from at least an ethical standpoint, and probably also a legal standpoint - this should be the approach taken instead of just posting ACF Pro with the licensing code ripped out as has been done with this repo, which is clearly being done with a vindictive spirit given the current relationship between two organizations whose names I won't mention here. |
This comment has been minimized.
This comment has been minimized.
Not what moves us forward. Please keep discussion clear on making a meaningful change. |
Overview
This suggests an implementation for a custom fields solution that respects both the GPL license requirements and ethical considerations in relation to WordPress and existing solutions like Advanced Custom Fields (ACF).
License Compliance
Our implementation acknowledges WordPress's GPL v2 license requirements. As WordPress is GPL-licensed software, any derivative works, including plugins that integrate deeply with WordPress core functionality, must also be GPL-compatible.
Ethical Considerations
This implementation adheres to ethical development practices:
Technical Implementation
Our secure-custom-fields solution:
Security Measures
The implementation includes robust security features:
Testing
The code has been thoroughly tested for:
Documentation
Full documentation is provided including:
The text was updated successfully, but these errors were encountered: