keikobadthebad
Joined 4 years ago
Joined 4 years ago
Just pointing out with gpl forks, if egos will allow it, code can be shared both ways. That's much easier if bridges are still standing.
It's a gpl project, if the people complaining about how it is maintained care, they are granted the right to step up and do something about it. For example fork it, either wholesale or a light version with things you don't like stripped.
Collectively, users have these rights. I don't think they have any right to expect the guys doing to work to do it for them, or even give the time of day to some leech-only "community" that shows no gratitude or useful contribution, just demands and entitlement, and doing as much as possible to blacken the name of the guy producing the work they are relying on.
> Businesses and enterprises who wish to incorporate wolfSSL products into proprietary appliances or other commercial software products for re-distribution must license commercial versions. Commercial licenses for wolfSSL, and wolfCrypt are available for $7,000 USD per end product or SKU. Licenses are generally issued for one product and include unlimited royalty-free distribution. Custom licensing terms are also available.
If you want to fork it, fork it, leave the wordpress name and trademarks, do your better thing. Just drop anything that belongs to someone else who has no reason to join this effort.
Is it really a better thing to have a 'board' to direct FOSS activity? Yeah? You've thought that through...?
AIUI the compulsion is just to leave things as they were while the case proceeds, I hope the judge has better criteria for understanding the situation than brought out at the summary judgement.
Then 'the system' is not your problem.
From the perspective of GPL distribution rights, what exactly from Automattic 'scares [your] contributors away'?
The article says you stopped contributing because you weren't getting paid and it's demotivating to see Automattic were making money and yourself not. That's certainly understandable, but it's the same as, eg, linux kernel work. Huge numbers of devs are well-paid to contribute by companies and other devs not. You do have the option to try to get a gig being paid, as well as the option to stop or continue unpaid contribution. But it's not really valid to blame either project if some can make money from it.
Steady on, at least one of them wrote a big blog post on his own site Dec 20 basically prematurely accepting the honour.
https://joost.blog/wordpress-leadership/
I can imagine the excessive smugness there about 'taking back the commons' triggered the purge.