# A question on GPL licensing and the current WordPress debacle

**URL:** <https://meta.discourse.org/t/a-question-on-gpl-licensing-and-the-current-wordpress-debacle/3355>\
**Category:** General\
**Created:** [2013 年2 月 18 日 19:14 UTC](https://meta.discourse.org/t/a-question-on-gpl-licensing-and-the-current-wordpress-debacle/3355 "2013-02-18T19:14:17Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

作者： ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
发布日期： [2014 年6 月 13 日 22:51 UTC](https://meta.discourse.org/t/a-question-on-gpl-licensing-and-the-current-wordpress-debacle/3355/4 "2014-06-13T22:51:20Z")

</div>

I guess what you are asking is, will Discourse ever allow closed source plugins? (where CSS, JS or whatever is close source), combined with allowing distributions of said plugins via the “Discourse Store”

I don’t know. This is a complicated question. As it stands the ecosystem is quite small, the easiest way for people to learn how to make plugins is actually look at plugin source code. By allowing closed here we would make it harder to get started.

That said, I understand the concerns here.

---

_[View the full topic](https://meta.discourse.org/t/a-question-on-gpl-licensing-and-the-current-wordpress-debacle/3355)._