14 ms·
So "Open Source development model" (developing in the open) is not the same thing as "Open Source Code" (developing in closed doors, then throwing code to the o
by dyingkneepad 6y ago
So "Open Source development model" (developing in the open) is not the same thing as "Open Source Code" (developing in closed doors, then throwing code to the other side of the wall once in a while). Intel has a history of doing both depending on the project and internal groups involved, where only really the Open Development projects are actually successful and long-term. OneAPI uses a lot of components and I am not entirely sure they all follow the Open Development model. There's a lot of Open Source stuff out there that you basically can't contribute to: your contributions are ignored because source code is open but development isn't. Does anybody here know about how this is done for the OneAPI-related projects?
- BadInformatics 6y agoMy sense is that they're somewhat better than, say, AMD at keeping development work in the open instead of just throwing code over the wall. Hence the choice of "development model" instead of just "FOSS". It's a low bar though, IIRC a lot of ROCm is just periodic code dumps with no visible PR strategy.