This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/OpenBSC@lists.osmocom.org/.
Keith keith at rhizomatica.orgHi Harald, Stefan. I'd just chime in here to say that this is something I've been thinking about recently and trying to discuss when I get a chance. The topic of said discussion is whether the time may have come to revise the FOSS "ethic"; Is there just too much "evilcorp" out there now to justify continuing to hand them our labour on a plate? - A reference I sometimes use here is the linux kernel as a base for a certain "evil" surplus collecting and behaviour modifying robot that was first hawked to the world as a "liberating" "open-source" project. Once it had it's evil robot paw on our hearts and minds and those of our children, it somehow felt the need to become somewhat less open. While I myself have never added a single line of code or even submitted a bug report on the linux kernel, I think I would feel somewhat strange about the above if I had. Of course, one could point to a lot of projects that retroactively benefit from open development communities and developers in the pay of some evilcorp or other have indeed contributed a lot of FOSS! Still, evilcorp will work in evilcorp's interests and nobody else's. Yes, there's a type mismatch in that sentence, ( type corp cannot be compared with type person ), but the point is that as long as FOSS is good for corp, corp will support it, but corp is getting VERY big these days and so the days for FOSS (or maybe I should say FOSS that is not in corp's interest) might be numbered. So for what it's worth, in principal I'm with Harald, especially given that I recognise that if I am to continue development on osmocom, I need to start contributing to the test suites! I have NO IDEA about the actual licensing issues or what the eventual license would/should look like. Luckily there are people around here who are quite expert in that field. K.