-
Notifications
You must be signed in to change notification settings - Fork 33
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
Why is this a plugin and not a pull request to ckan? #12
Comments
Parts of this code are being pulled into CKAN, however some of the features are more opinionated than should be in CKAN. Additionally maintaining a plugin over the short term is significantly easier than a series of patches to core CKAN. |
Awesome. Thanks!
…On Wed, 14 Mar 2018, 22:51 Lee Symes ***@***.***> wrote:
Parts of this code is being pulled into CKAN, however some of the features
are more opinionated than should be in CKAN. Additionally maintaining a
plugin over the short term is significantly easier than a series of patches
to core CKAN.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAOZGZiI_IjePl-HhhT8tuCWS5aJ85diks5teYLMgaJpZM4SqAr9>
.
|
I'm going to close this issue but feel free to pick the conversation back up in #2 |
Oh man I just totally looked past #2 when asking my question. Sorry :) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This sounds important.
Why is this a plugin and not a pull request to CKAN?
The text was updated successfully, but these errors were encountered: