-
Notifications
You must be signed in to change notification settings - Fork 172
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
Publish DKAN on Drupal.org #226
Comments
requested leaflet.markercluster to be whitelisted https://www.drupal.org/node/2367231 |
requested showdown to be whitelisted https://www.drupal.org/node/2367281 |
thanks! |
@acouch you bet! will put some more whitelist requests in over the weekend as applicable. |
fantastic |
put four more whitelist-requests in:
still todo: whitelist requests for moment and timeline. |
I reviewed the whitelist requests this morning. Unfortunately Flotr2 and showdown have issues and cannot be whitelisted as they are now. Some of these issues could be solved if the DA starts reducing the restrictions on requiring a GPL license for all code and assets and prohibiting 3rd part libraries from being committed to Drupal's git repo. It has taken years to get to the point they are reviewing a charter for a licensing working group (https://groups.drupal.org/node/445098). Once that is approved, the group will actually have the authority to start making small changes like allowing "GPL friendly" licenses like SIL OFL for fonts and Create Commons for content as well as allowing 3rd party code that can't be used without modification (in this case, removing Apache2 libraries). This group will not have the authority to allow distributions the option of distributing Drupal core w/ a GPLv3 (thus allowing them to include Apache2 code). Currently it is perfectly legal to do that on GitHub, but not Drupal.org. That change will require approval from Dries himself, but we need to both track the distributions using alternatives to maintain a distribution as well as show that those maintainers are interested in using Drupal.org. Adding the reasons why you want to use Drupal.org to package your distribution to https://www.drupal.org/node/1449452 will only help move that forward. |
@kreynen thanks for the feedback! |
Just tried to publish. Here are the errors:
|
Following the logic here, these errors aren't from the distribution .make, but the recline .make in dkan_dataset .make include at https://github.com/NuCivic/dkan/blob/7.x-1.x/drupal-org.make#L12. Looking at I think the "The top-level attribute '#..." error message itself might be caused by "The URL for project 'recline' is invalid ALL URLs included in any .make have to be whitelisted or the Drupal validation will fail. It is going to take awhile to get the all of these projects whitelisted, but I can save you some time on a few... FontAwesome - SIL OFL is not strictly GPL compatible. It is now labelled as GPL friendly and can not be whitelisted until the revisions to the Drupal.org git and licensing policies the LWG proposed are approved. As soon as that happens, FontAwesome will be whitelisted. If you absolutely need FontAwesome to be included on install, take a look at https://www.drupal.org/node/2427075. A number of other distributions are using FontAwesome via a CDN while we've been waiting for the changes to Drupal.org. Some of the libraries that are failing validation may just need updates made to the regex, but several need to be reviewed before they can be whitelisted. If you add those requests to https://www.drupal.org/project/issues/drupalorg_whitelist, I'll do what I can to get those published this week. |
Yes, backbone is whitelisted https://www.drupal.org/packaging-whitelist?title=backbone but the regex isn't picking it up correctly. Looks like someone will need to work through those.
Also true.
FANTASTIC! |
This is the most recent report when trying to create a release on drupal.org:
|
Closing this ticket as it has not been updated recently and is not on our near-term roadmap. Please re-open if you would like to discuss further or are actively working on it. |
We can't publish DKAN on Drupal.org because some of the libraries are not GPL2 compatible. See: https://www.drupal.org/packaging-whitelist . This issue can track that:
The text was updated successfully, but these errors were encountered: