I would say well deserved! I am not anymore into web design nor did I ever liked it much (I went low-level and to hardware design) but when I needed to do it I used webflow and it was delight. Easy, intuitive and really great tutorials were there.
Hi,
I have hard time to find the email where to apply and while browsing there seem to be many missing or broken links in your docs.
I really like what I read in general around the company's culture and I see I could fit in few roles, so I am eager to apply :)
Hi, sorry I missed your reply. The email was indeed missing and it was added short after posting it here. You can just email me at xavi at vocdoni.io.
The documentation is a big beast and our source of truth, I'll highly appreciate if you can point me to the broken links.
We still experiment with where we hire. If you look at my previous posts, we used to hire anywhere in US but trying to narrow it down to just couple of our physical offices.
While the Librem5 is step into right direction, it is far away from open hardware and will likely need even software proprietary bits - so I would recommend to stay in realistic zone and help the project in any way you can.
> The Corporation will release all software written by The Corporation under a free software license.
> The Corporation will release all hardware schematics authored by The Corporation under a free hardware license.
If you are talking about the IP blocks that are bought/licensed from third parties, then you are right, but I suppose that these are replaceable by equivalent blocks in future versions, without the user noticing. In other words, users don't depend on these blocks, so for all the user knows, these blocks are commodities.
I know the manifesto, I am among original ones proposing it.
And for things that might happen in future, I would leave them for future. Building hw takes time and proper dedication - all what I am saying is to be realistic towards current situation. The blocks are no commodities but some essential parts in today's use of smartphones. And no, things don't move that fast that you will just replace it.
If done right, things could finally go into right direction or at least have some new light on it.
They're not of course. They just treat the modem as walled off peripheral black box like all the other rest of the hardware. They may load firmware on boot for LTE/Wifi/Bluetooth like most Linux laptops do. Depending on your opinion on the topic that may be free enough or not but it should be safe as none of those can access the CPU/RAM directly.
I see. The question here is not if there will be proprietary software: there will be. The question is which of that proprietary software runs on the CPU.
Is the idea that all of the software in the kernel to interface with these devices is open source?
I also don’t get the hangup over PCIe (vs USB). DMA with an IOMMU can be made fairly secure (and has obvious perf benefits).
> I see. The question here is not if there will be proprietary software: there will be. The question is which of that proprietary software runs on the CPU.
I'm pretty sure no closed source software runs on the CPU. As for the hardware that depends on your definition. Hardware often has firmware in ROM. That you now feed that firmware on bootup instead of it being in ROM just allows you to update the firmware from the manufacturer. If that's running proprietary software depends on your definition.
I think the main reason is that powering off a device (for their hardware kill switches) connected via USB is more reliable than powering off a device connected via PCIe.
There's also just more layers of security when using USB as opposed to a single layer with PCIe (IOMMU -- which is secure as far as I know but I'd prefer to be safe rather than sorry in this case).
Besides IOMMU bugs, which silicon vendors often subtly add to their errata too much for my comfort; an IOMMU adds security against DMA attacks in theory. I specifically say in theory because oftentimes vendors either don't configure it correctly or leave it totally unconfigured. Additionally, things like multiplexing on the same bus further complicates things
I thought of the kill switch thing after commenting… eGPUs (necessarily) have the ability to be unplugged while running, but I think it was a lot of work on the part of the OSes to make that work well.
Debian gets sponsored by various ways but the money isn't used directly for developers nor their time. It is volunteer based project and money is usually used for hardware, sprints, conferences, outreachy etc.
That said Debian does take it seriously when it comes to privacy and security so you can always report bugs on such. Do note that Debian's Chromium builds have always disabled the infamous "mic always on" option which Chromium has (or had, didn't check) by default.
Btw, Debian now moved to gitlab hosting (their own instance salsa.debian.org) so it should be much easier to contribute to Debian now. :)
P.S. while Debian Developer myself, I stay away a lot from browser and especially Chromium, and I always suggest Firefox (it has really got better last year or so).
it should be much easier to contribute to Debian now
But aren't they constantly getting new versions of Chromium from Google? I think going into the Debian Repo of Chromium and changing it would not be a viable path, right? You either have to convince Google to accept your changes too (Good luck with them accepting the de-googling haha) or you would have to consider a life of constantly de-googling new versions of Chromium.
Debian maintains its set of patches often (quite easy to handle with quilt in debian/patches). We get upstream source from upstream of course and use our patches until they get accepted (we don't force upstream to do so) when we of course remove obsolete ones.
At my company we used Jitsi (and also tried with hosting our own instance) and Appear.in. Both worked kinda fine and appear.in has limit to number of people unless you go to pay option - with more people quality would simply drop and we do have 20+ people in company meeting.
We decided to try old school - we hosted our own Mumble and while maybe not nice UI/UX, it works perfectly for 20+ people. Also I recommend as well having good headphones (with integrated mic) to avoid potential echo (jitsi echo can be annoying without headphones).
KDE community is awesome and all they needed to revive things around plasma mobile effort is to have dedicated device and with Librem5 they would get exactly that.
Thanks Webflow team!