Please include weblabels for javascript

[gnusupport]

This is follow up of the issue wrongly filed here:
https://gitea.com/gitea/website/issues/99#issuecomment-119899

Solution on how to do it is here:
https://www.gnu.org/software/librejs/free-your-javascript.html

Many users of FSf endorsed distributions use LibreJS and many other GNU/Linux users. It is desirable for new users coming to the website to know that javascript is also free software. Those users may not be able to find licenses or crawl the site to find details, browser may warn them or give a green light.

It would be very nice if you include that as that may influence thousands of people in future and other projects as well. Thank you.

[lafriks]

Problem is that imho there is no way we can generate it with webpack automatically and keeping it updated manually for each javascript library we use takes too much work. If you can suggest any way to do that automatically we are open to PR on that

[6543]

ref https://forge.softwareheritage.org/source/swh-web/browse/master/swh/web/assets/config/webpack-plugins/generate-weblabels-webpack-plugin/

[realaravinth]

I use a hack-ish script in one of my projects and it seems to do the job. I could adapt it to Gitea, thoughts?

aside: the page @6543 linked to no longer exists, here's an old archive.org snapshot of the same.

[iambeingtracked]

Is there any progress on that? I really want gitea to be LibreJS compatible

[wolftune]

Even if complete LibreJS support isn't done, can some workaround be made to do something to make it easier for curious people to find the corresponding source code to the minified JS that Gitea serves?

Basically, some direction to the relevant source projects that facilitates this so that people don't have to struggle to search around to find obscure links…

[lunny]

I think we already have https://gitea.com/assets/licenses.txt , and a link has been displayed under footer of every Gitea instance. So we just need a tool do convert it the suitable format?

[wolftune]

I think we already have https://gitea.com/assets/licenses.txt , and a link has been displayed under footer of every Gitea instance. So we just need a tool do convert it the suitable format?

I have a hard time reading that and knowing: does it contain (or is it generated by something that has) all the info not just about license but about the source files? What I'm most obviously missing in licenses.txt is a way to find the associated non-minified source code. I only see stuff like brace-expansion@2.0.1 with a license, and that doesn't tell me where to find the source code for that.

[lunny]

All js package could be searched on npmjs.org, all go package can be visited directly with the package url. I know it's not convinent like a html and links. But we need a suitable tool to generate that format.

[wolftune]

Would it be easy enough for the licenses.txt file to have a note added to it that says that the source files are available on npmjs.org?

What about maybe changing the generated file so that brace-expansion@2.0.1 has a link to https://www.npmjs.com/package/brace-expansion/v/2.0.1 ?

Anyway, it seems indeed the full weblabels support would work with just a tool to convert licenses.txt appropriately. I guess it does have all the necessary information, yeah?