Add support for more plugins

I've created a merge request which is working just fine, please have a look.

There is a license limitation to a Drupal contribute module.

Details see

https://www.drupal.org/about/licensing#drupal-license →

I would recommend creating a custom module for your project for this purpose.

Please reconsider that. I'm very conscious about the licence and will do all I can, to never break that. In this case, the project and the code base will not contain any non-compliant code. It links to some external code which has a different licence, but that's not included in the code base. And that's allowed. Also, for non-commercial projects, the premium version of the fullcalendar library comes with a creative commons licence, see https://fullcalendar.io/docs/premium - and that's compatible with GPL with no issue at all.

The Fullcalendar premium and plugins required is not under GPL-incompatible license.
https://fullcalendar.io/license

And also as Drupal license said

Can Drupal projects include GPL-incompatible non-code assets? (e.g. fonts, icons, etc)

Yes, so long as the maintainer has the right to distribute the non-code assets, they may be packaged and/or distributed "in aggregate" with GPL code. Only works that are derivative of the original work are subject to the GPL license.

Quite frankly, I am not comfortable with that license.

It is not difficult to develop a custom module for your project. If you want, you can even create a contribute module that provides the plugin you want working with this module.

What you need to do, just two things.

1. Using hook_library_info_alter hook to add the plugin library to the blocks.
2. Using hook_form_BASE_FORM_ID_alter hook to add the additional plugin setting to the block configuration forms.

Sure, but we do NOT aggregate any code from fullcalendar.io into this module. Also, we do not distribute and code from fullcalendar.io.

Instead, we get the website to load external assets from a different source. Nothing in GPL prevents us from doing that. The GPL licence is only concerned about the code you package with your module and that you distribute. None of that is being done here. And also, the premium licence of fullcalendar is Creative Commons, which is even more permissive than GPL and therefore fully compliant.

It is not difficult to develop a custom module for your project.

I know, but I wanted to add value to your module here, as other users will benefit from that work too. If you don't want me to add that value, that's OK, and totally your decision.

jurgenhaas → closed merge request !9