Make WordPress Core

Opened 17 months ago

Closed 3 months ago

#22534 closed enhancement (worksforme)

Make bundled JavaScript LibreJS compatible

Reported by: micahflee Owned by:
Milestone: Priority: normal
Severity: normal Version:
Component: General Keywords:
Focuses: Cc:


Many free software advocates don't want to run proprietary JavaScript code in their browsers. The Free Software Foundation has releases a Firefox extension called LibreJS that blocks non-free JavaScript from running: https://www.gnu.org/software/librejs/

WordPress is released under the GPLv2 license, but LibreJS still blocks WordPress JavaScript files because they don't have the appropriate license blocks.

To fix this, we can either add comments to the top of each .js file with the license, or we can use JavaScript web labels to define the license for each js file in HTML.

Here are instructions for marking your JavaScript as free so that LibreJS users will execute it:

Change History (5)

comment:1 toscho17 months ago

  • Cc info@… added

Why is that a WordPress problem? Their white-list approach will fail on almost any other website anyway. I don’t see much value maintaining a document with such list.

Plus, any script in WordPress can be replaced by a plugin – with a proprietary script under the same handle.

comment:2 rmccue17 months ago

  • Keywords close added

-1, I'm not sure why this is something we should be really caring about.

comment:3 nacin17 months ago

In May of this year, I offered this private assessment of LibreJS to someone who asked. I am posting it here, as I think the points still stand:

Based on my reading, RMS/FSF essentially want everyone to document in the page and script sources the individual licenses of all JavaScript running on the page. Only their particular format (which is a few paragraphs long and includes @licstart and @licend tags) will pass their LibreJS add-on, which I've tried out.

In February, they made a push for HTML table markup on every page that must be "displayed prominently" to declare the license of the code running on it. See http://www.gnu.org/licenses/javascript-labels.html. It is rather absurd. You can see Stallman's article, "The JavaScript Trap," here: http://www.gnu.org/philosophy/javascript-trap.html. The table markup is linked in Appendix B. The chunk of license text is in Appendix A.

We clearly meet the language and spirit of the license by declaring the entire software as GPLv2 (or later) and by providing a written offer. Alas, it seems the FSF is trying to make things difficult for projects that are A) clearly properly licensed and B) support the FSF, mainly to make a point to everyone running non-free code. The WordPress package is free software, but he also wants to ensure that every browser in the world only executes free JavaScript too, which is unnecessarily burdensome and not very practical for everyone involved -- especially people already playing by the rules. I'm not sure I recommend we play along.

The irony was not lost on me that FSF apparently invented their own format (correct me if I'm wrong — I've never seen anything quite like this before), rather than, at the very most, encourage some kind of simple, standard license marker that many projects were already doing.

comment:4 nacin16 months ago

  • Keywords close removed

Removing the keyword that suggests this ticket be closed. This ticket is fine to remain open while we wait for a response from the FSF.

comment:5 nacin3 months ago

  • Milestone Awaiting Review deleted
  • Resolution set to worksforme
  • Status changed from new to closed
Note: See TracTickets for help on using tickets.