|
|
|
|
|
|
by bsder
1118 days ago
|
|
|
> Whilst PlatformIO come across as the villains in this story I find this to be a bit misleading. My take is that the RPi foundation wants PlatformIO to do support work for RPi for free. At no point do I see the RPi foundation saying "Hey, we'll allocate programmers and resources to maintain this code for our chip." Open source means that you get the code and that's it--open source doesn't mean that you get any say whatsoever over the developers. When did everybody start being so damn entitled that everybody thinks they can tell maintainers what to do? Don't like it? Shut your piehole and roll up your sleeves. Quit bitching, fork the PlatformIO stuff and do the work yourself. If the fork is sufficiently popular, it will yank enough people away from the original that they'll cave. And if it isn't sufficiently popular, well then that's an answer, too. |
|
|
How did you arrive at this take when the original code and the PR aren’t related to the Raspberry Pi foundation at all? This is a community contribution, not something the Raspberry Pi foundation tried to push throug.
> At no point do I see the RPi foundation saying "Hey, we'll allocate programmers and resources to maintain this code for our chip."
They didn’t write this code, and this isn’t what PlatformIO is asking for. PlatformIO wanted the Raspberry Pi foundation to pay substantial recurring fees so PlatformIO could merge this PR by someone else.
> Don't like it? Shut your piehole and roll up your sleeves. Quit bitching, fork the PlatformIO stuff and do the work yourself.
That’s quite literally what they did. This was developed by someone in a fork. That person didn’t even submit this PR. None of the people involved appear to be related to the Raspberry Pi foundation, but PlatformIO tried to bill Raspberry Pi for it anyway.