39 karma · joined October 8, 2016
Regarding projects which receive a grant, holding a PhD does not matter.
Title: Give open source a (tax) break
Cash that gets into FDL/LEF is then spent to sponsor existing FLOSS projects or to acquire intellectual property rights of existing works and change their license to FLOSS.
Case 1: https://bossanova.uk/jspreadsheet/v4/ got financed partly by FDL/LEF
Case 2: the radio hardware of the Open Radio Station (a 4G/5G vRAN base station based on Amarisoft stack and SlapOS) is in the process of being acquired and released as open source hardware. See https://shop.rapid.space/product_module/241/Resource_viewAsS...
The requirement for PhD is here to ensure that all projects that are financed by FDL/LEF have some kind of general interest or innovation, something which is useful to comply with Tax Law
It is now super easy to get 5G frequencies in Europe for private use. See for example https://campusnetzplaner.kn.e-technik.tu-dortmund.de/ where you buy your spectrum online in one click. In France, you can get your private N38 spectrum for 150€/month/km2
And the hardware is just as easy to build and run. With less than two cores of a low-end i5 CPU, Amarisoft stack and SlapOS edge OS, we could manufacture for Rapid.Space our own 5G base station which delivers 5G over N78. There is still enough room inside to run a software PLC next to the gNodeB. See the pictures of the assembly process and what's inside:
https://handbook.rapid.space/provider/rapidspace-ORS.Assembl...
The PC is a standard IPC from Taiwan (Commell) and the SDR is open source hardware from FDL https://www.fdl-lef.org/projects/
I hope we will see more open source hardware for 5G base stations with different sorts of CPUs doing the radio processing (AMD, Zhaoxin, ARM, RISC V) without the need of accelerator components. 5G radio signal processing can be nowadays entirely done in software and it is not so hard thnaks to SIMD instructions found in most CPUs. I have even seen recently a sample of a fully software defined array of antenas (32T32R) with 100 MHz bw, entirely implemented with software.
https://www.nexedi.com/NXD-Presentation.Status.Roadmap?porta...
Our story with /e/ is that we decided that it would make more sense to invest some cash in /e/ (we did it) than try to maintain NayuOS now that most ChromeOS users expect to run Android apps (and this part is not in ChromiumOS AFAIK).
Also, we observed a growing need for some kind of "desktop OS" for industrial applications (robotics, industrial automation) that does not depend on Google APIs (factories are often in China or do not have Internet access).
/e/ thus made a lot of sense.
Note: I the author of the post.
- support for flash movies
- support of certain video codecs
- support of sound hardware of many recent Chromebook models
- support of CJK input (at least in Guest Mode)
- support of Android apps
- support of Linux virtual machine subsystem
- support of certain Google APIs (but that is OK for me)
Lack of stable support of CJK input in guest mode (and the difficulty to find anyone capable of solving this problem or supporting us) was the biggest issue for me.
Some years ago, the difference was:
- support for flash movies
- support of certain video codecs
- support of certain Google APIs (but that is OK for me)
which was fine to me.
Note: I wrote the article on /e/ for Desktop
Lack of stable support of CJK input in guest mode (and the difficulty to find anyone capable of solving this problem or supporting us) was the biggest issue for me.
Some years ago, the difference was: - support for flash movies - support of certain video codecs - support of certain Google APIs (but that is OK for me) which was fine to me.
Note: I wrote the article on /e/ for Desktop