3rd party files in in Panelli Git repo [#2764555]

The Drupal.org git repo of the theme Panelli contains the following items which appears to be third party materials:

https://github.com/necolas/normalize.css
Copyright © Nicolas Gallagher and Jonathan Neal (MIT)
http://960.gs/
Copyright © 2008 Nathan Smith (MIT and GPL)
overlay.js
Author badlyDrawnToy (CC BY-SA 3.0)
https://github.com/nathansmith/formalize
Authors Nathan Smith, Mike Wille and Ryan Florence (MIT and GPL)

Third party materials is not generally allowed in Drupal.org git repos, and should be deleted from the repo.

An exception to host third party code must be explicitly approved by the LWG. The conditions for granting an exception is described in: 3rd party libraries and content on Drupal.org.
However, in this case, no exception has been requested.

The preferred mechanism for adding 3rd party dependencies without directly including the code in the Drupal.org repo is to make use of the Libraries API module can be used for adding 3rd party dependencies without directly including the code in the Drupal.org repo.

Please note:
This policy is described in the 3rd party libraries and content on Drupal.org. It also appears in the Drupal Git Repository Usage policy you agreed to when you signed up for Git access, which you may want to re-read, to be sure you're not violating other terms.

This notice is also sent to the project owner (Lioz) through the Drupal.org contact form.

Comments

Comment #1

12 July 2016 at 05:03

gisle created an issue. See original summary.

Comment #2

Jeff Burnz CreditAttribution: Jeff Burnz commented 13 July 2016 at 07:37

normalize.css should just be whitelisted, it's in Drupal 8 core.

Comment #3

gisle

he/him

Norwegian Bokmål

Norway

CreditAttribution: gisle at Hannemyr Nye Medier AS commented 13 July 2016 at 08:38

Drupal core contains a lot of third party code, as documented in:
https://api.drupal.org/api/drupal/core%21COPYRIGHT.txt/8.2.x

These materials exists in the core repo under an exception to the Git Repo Policy (all exceptions for core were granted informally and before the LWG were set up, but as long as they're not disputed, the LWG will not intervene or invalidate the exceptions that were granted before we existed).

But, yes - I agree - it should be whitelisted - but I am not allowed to do that by our current rules.

I want these stupid rules to change, but so far I haven't been able to make this change happen.

As a member of the LWG, I have been specifically instructed by the Drupal Association to enforce the rules - so that is what I do. Perhaps somebody notices that the present rules may need revision, and as a result put pressure on the Drupal Association to move the Git Repo Policy revamp process forwards on their agenda?