<unnamed>

Public Key

npub1gcf8zwxgqpnl08gwnancjvvv0pggt5wgpphtjxpgrtzsz0tf6f6s4el3rh

Profile Code

nprofile1qqsyvyn38ryqqelhn58f7eufxxx8s5y968yqsm4erq5p43gp845ayagpz3mhxue69uhhyetvv9ujuerpd46hxtnfduqs6amnwvaz7tmwdaejumr0dsc6z0pe

Publishing to

relay.primal.net

relay.damus.io

nos.lol

Last Notes

2024-08-20 12:36:05 UTC

- reply

> > You can fork Apache licensed software and decide that new contributions will be under a proprietary license. You can decide that on a fork you already run. That's what they did.
That's sublicensing (which Apache 2.0 allows), not relicensing.
Permissive licenses generally require to credit the authors/project or anything similar. Even if you make a proprietary fork, you must follow that clause. For example, Chrome has chrome://credits. iOS and Android derivatives should have an equivalent somewhere in Settings, etc. However, in Sourcegraph's case, they don't have to (anymore).

2024-08-20 12:03:02 UTC

- reply

I don't think I can give any "official" source, but I think this post explains it fairly well:
> > The copyright holder (or, more commonly, holders) can release a version of the software that uses a totally different license. Everyone who uses earlier versions of the software can continue to use it under the terms and conditions of the previous license, but from that new version forward the new license applies to anyone who uses the software.
> >
> > [...]
> >
> > It requires getting the copyright holders to agree that their contributions can be released under the new license, and for some projects that can mean tracking down hundreds or thousands of individuals. However for other projects—especially projects with a primary corporate sponsor or those with a Contributor License Agreement that includes copyright assignment—there typically are considerably fewer copyright holders, making the overall relicensing process much easier.
https://anonymoushash.vmbrasseur.com/2022/10/27/open-source-relicensing-business-risk
They name several examples, all of which are relicensed from permissive licenses.
I looked at that person's [resume](https://www.vmbrasseur.com/resume.pdf ), which states that they were previously a member of SPDX Legal Project

2024-06-24 11:30:48 UTC

- reply

I don't think anybody disagrees with ableism - I too agree that leaving the screen reader broken for 8 years is ableist.
Once again, the problem we have with Aral is he dogpiles volunteers without contributing anything himself. Good accessibility is extremely difficult to achieve, and to some extent the only people who can improve it is have the ones relying on it fix it themselves, because they understand what these tools are supposed to do.
You can't expect us to fix something if we don't even know what to do or where to start.
@npub1smw…7lhy @npub1p09…m5vl

2024-06-23 15:58:27 UTC

- reply

don't get me wrong, I agree with Aral's accessibility takes, but I don't appreciate the way he approaches with these issues, especially when all he does is talk and shame us without helping us isolate. Literally everybody knows that Linux accessibility has a long way to go, but almost nobody is talking about the how, including him.
@npub1jed…zzat @npub1p09…m5vl

2024-06-22 13:34:51 UTC

- reply

> Worse, when features are designed without it as a baseline, it's very difficult to add later.
Yeah... we're currently experiencing this in Calendar 🙃
@npub1jed…zzat @npub1p09…m5vl

2024-06-22 13:25:35 UTC

- reply

I don't agree, but I respect the sentiment. Accessibility is extremely difficult to achieve, because accommodating those you literally cannot relate to takes a lot of energy. I would argue that learning to accommodate others takes exponentially more time and energy than creating a mockup, planning the code structure, and writing it combined.
As someone who has some ADHD traits, sudden and subtle movements easily distract me, but unfortunately my curse is not something everyone can relate to, so it's hard for them to properly accommodate me when they don't even know if they're addressing it correctly. It's especially hard when the codebase typically becomes much more complex than it was to begin with.
An anecdotal example, but one I think is relevant, is GNOME Calendar. Accessibility in Calendar is, to put it in the nicest way possible, almost nonexistent: Many widgets cannot be interacted with using a keyboard and can only be triggered using a pointer. I'd go so far as to say that it's literally unusable for anyone who absolutely relies on their keyboard. And believe me, I *want* to make it accessible. I *am* serious about it, but I have no idea where to start, and even the maintainer doesn't know what to do.
Maybe GNOME Calendar is an ableist application because of this, I don't know, but I don't want to throw "ableist" around because many developers and maintainers don't even know what to do to accommodate those kinds of people.
@npub1jed…zzat @npub1p09…m5vl

2024-06-22 12:26:11 UTC

- reply

if that was the case, individuals from different groups (System76, KDE, elementary, etc.) wouldn't have stood up for us (GNOME) and/or have shared their fair share of experience with Aral:<li><a href="https://fosstodon.org/@soller/112646375569571307" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://fosstodon.org/@soller/112646375569571307</a></li><li><a href="https://fosstodon.org/@soller/112648742151686315" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://fosstodon.org/@soller/112648742151686315</a></li><li><a href="https://chaos.social/@karolherbst/112656291406890211" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://chaos.social/@karolherbst/112656291406890211</a></li><li><a href="https://eepy.moe/notes/9usfmv3h36ro006v" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://eepy.moe/notes/9usfmv3h36ro006v</a></li><li><a href="https://scalie.zone/@aks/112645251302738578" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://scalie.zone/@aks/112645251302738578</a></li><li><a href="https://scalie.zone/@aks/112616015522811492" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://scalie.zone/@aks/112616015522811492</a></li><li><a href="https://chaos.social/@karolherbst/112621784417214274" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://chaos.social/@karolherbst/112621784417214274</a></li><li><a href="https://hachyderm.io/@fizzyizzy05/112616628161997951" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://hachyderm.io/@fizzyizzy05/112616628161997951</a></li><li><a href="https://mamot.fr/@thibaultamartin/112615456157531012" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://mamot.fr/@thibaultamartin/112615456157531012</a></li><li><a href="https://mastodon.online/@danirabbit/112621338824093319" target="_blank" rel="nofollow noopener noreferrer" translate="no">https://mastodon.online/@danirabbit/112621338824093319</a></li>
But that's not the case. He may not have attacked individuals, but he certainly attacked groups of individuals. It doesn't change in any way that he's attempted to dogpile by trashing projects publicly without opening issues first.
@npub1p09…m5vl

2024-06-15 19:13:18 UTC

Oh FFS, #GNOME #developers are so #dumb and #stupid, they can't fix their #bugs and always refuse to add #features. So much for a #FOSS / #OpenSource / #OSS project
*le sigh*
Wait, why is everybody against me? Surely I'm not the problem right?! I was just criticizing 🙄 🙄 🙄