News for hackers. Stuff that matters.
Re:The GPL-Violations.org Project (2016) by phildenhoff on Friday February 12, 2021 @11:54PM (#26121500)
If you manage a website like this, I implore you to spend an hour and think about someones first-time experience when they land on your site.

- The logo goes to the homepage

- the "gpl-violations.org" link goes to the homepage

- the page title goes to the homepage

- About describes the goal of the project and who's behind it, but not how to access the project... or if that's even a thing.

- The GPL page lists the GPL itself

- FAQ has a drop down... for four pages that I don't have the context to pick from? Who is this site for? The categories also aren't the same. Some are people (Vendors) others are topics (Legal).

Beyond reading those pages, as an individual landing on the page I'm exhausted at trying to find out what gpl-violations.org does.

> The gpl-violations.org project tries to raise public awareness about past and present infringing use(r)s of GPL licensed software.

Yes, but _what do you do_? Email people? Run marketing campaigns?

> The project wants to act as information and communication platform between all parties involved with licensing of free software

Where is this platform? How do I access it? Is your selling point acting as a liaison? If so, why would you not put a big "contact us" button front and center?

Look, I get that you might not want to design your site to look like a brand-new Bay Area SaaS. I don't want you to do what you don't want! I just want you to think about how to best provide info to the people who visit your website (and who might want to join your cause). And, so far, this ain't it!

Re:The GPL-Violations.org Project (2016) by ISL on Saturday February 13, 2021 @01:19AM (#26121807)
My expectation from the URL would have been better served by a perpetually-maintained static html page enumerating GPL violators.
Re:The GPL-Violations.org Project (2016) by thih9 on Saturday February 13, 2021 @03:09AM (#26122179)
I think they intentionally avoid it, see FAQ:

> Beware the "public shaming" bomb. It's easy to let off, but very hard to defuse if you made a mistake or the issue turned out to be minor and is rapidly resolved.

[1]: http://gpl-violations.org/faq/violation-faq/

Re:The GPL-Violations.org Project (2016) by remram on Saturday February 13, 2021 @12:17AM (#26121602)
Agreed, this is empty of information.

There's a wikipedia page for the organization: https://en.wikipedia.org/wiki/Gpl-violations.org Among other things, it mentions that the website was offline for most of 2015, and while they recovered it, I am not sure if they have been in activity since (whatever their activity is).

Re:The GPL-Violations.org Project (2016) by john_moscow on Saturday February 13, 2021 @12:11AM (#26121577)
Last entry in the news section is from 2016. Looks dead in the water to me.
Re:The GPL-Violations.org Project (2016) by riedel on Saturday February 13, 2021 @03:01AM (#26122149)
I guess laforge is doing other things atm, but i guess he at least hasn't called it dead: http://gnumonks.org/~laforge/projects/license-compliance/
Re:The GPL-Violations.org Project (2016) by craigsmansion on Saturday February 13, 2021 @04:09AM (#26122424)
> I guess laforge is doing other things atm

Yes. Judging by the reactions here I think most commenters are unfamiliar with Harald Welte, prolific Free Software hacker and one-man GPL defender.

For all the noise out of kernel hackers about doing their own enforcement if needed, so any copyright assignment is not necessary, Harald is one of the very few who actually went through the trouble of doing something to keep the kernel GPL instead of "GPL as lipservice, BSD in practice."

You'd think the Linux Foundation would be all over this, but it looks like they prefer to keep the gravy train rolling (https://www.linuxfoundation.org/join/members/).

Re:The GPL-Violations.org Project (2016) by pabs3 on Saturday February 13, 2021 @09:35AM (#26123799)
His current focus is open source mobile communications networks:

https://osmocom.org/

Re:The GPL-Violations.org Project (2016) by MaxBarraclough on Saturday February 13, 2021 @08:42AM (#26123540)
One more minor point: http should redirect to https.
Re:The GPL-Violations.org Project (2016) by LaF0rge on Saturday February 13, 2021 @02:34AM (#26122060)
If you have so many comments, why raise it here and not mail the contact stated at the website? Do you think it is more productive in effecting a change to only post this here, rather than to whoever is responsible?
Re:The GPL-Violations.org Project (2016) by syockit on Saturday February 13, 2021 @02:44AM (#26122090)
The answer is in the first sentence

> If you manage a website like this

So it is and advice to whoever manages this kind of website, not just the webmaster of GPL-violations.org

Re:The GPL-Violations.org Project (2016) by bawolff on Saturday February 13, 2021 @05:48AM (#26122811)
Its a forum. The entire point is to post and discuss things, not to fix the world. If we wanted to do that we would be fixing the world instead of reading hacker news.