Changing how we develop Ladybird
ladybird.org
Changing how we develop Ladybird
1–10 of 602 posts
Re: Changing how we develop Ladybird
#2[deleted]
Re: Changing how we develop Ladybird
#3It saddens me to see the communities surrounding free software projects going dark because of the threat posed by AI tools, but I don't know what other solutions there are that would mitigate the threat, particularly when browsers are such a compelling target. Perhaps some kind of trust system a la arxiv.org, where existing users have to vouch for new submissions before a user is themselves trusted? Definitely still vulnerable to abuse, but perhaps less so.
Re: Changing how we develop Ladybird
#4I feel like the project just died.
Re: Changing how we develop Ladybird
#5"Gain trust through plausible contributions" is a new angle on AI-produced PRs I haven't seen yet.
Though in retrospect we should have seen it. It's been an angle of attack since forever, it only took a lot of effort.
Re: Changing how we develop Ladybird
#6Zig is moving to this direction is well.
Re: Changing how we develop Ladybird
#7We need stricter verifications / credentials behind GitHub accounts and PRs.
And this we should have had already before AI.
Re: Changing how we develop Ladybird
#8Why don’t they take the Linux approach? A browser is like an OS. Linux continues to accept public contributions, through an esoteric process that discourages lazy contributors: https://www.kernel.org/doc/html/latest/process/submitting-pa...
Re: Changing how we develop Ladybird
#9Stuff like this makes me wish AI had never happened.
An open-source projects losing the ability to find and mentor new maintainers is so disappointing.
Re: Changing how we develop Ladybird
#10For every person wanting to do good in the world there are ten windup merchants of which at least one has darker motives