# 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:** [18 فبراير 2013، 7: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:** 9

<div class="post-metadata">

**Author:** ![rpglover64](https://avatars.discourse-cdn.com/v4/letter/r/7ba0ec/32.png) [@rpglover64](https://meta.discourse.org/u/rpglover64)\
**Post date:** [27 أغسطس 2014، 2:17م UTC](https://meta.discourse.org/t/a-question-on-gpl-licensing-and-the-current-wordpress-debacle/3355/9 "2014-08-27T14:17:47Z")

</div>

> [@cpradio](#):
>
> If you need to alter the Discourse core code, that is where things get sticky. You are modifying code that is under the GPL, therefore all modifications you make should be made publicly and sent as a PR back to Discourse so they can include them in future releases

I think your interpretation here is incorrect; according to the [GPLv3](http://www.gnu.org/licenses/gpl-3.0.txt):

> You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force.

That is, as long as you don’t give someone your modified copy of Discourse, you have no obligation to share the code.

---

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