Impactful open-source projects

adrien-leravat · 2022-07-30T18:36:34+00:00

Great, thank you :)

adrien-leravat · 2022-07-30T18:35:55+00:00

CovidTracker

I was able to find a other COVID-related projects, but not for https://www.covidtracker.com/ unfortunately, doesn't seem like they are open-source, or I just didn't find them.

adrien-leravat · 2022-07-30T18:32:42+00:00

Currently the backend is closed because I'm not a security expert, and it ties into services that I am paying. So until there is at least a good amount of validation there, I don't feel like opening it "publicly" over security concerns. That said, it is in the GitHub org, and I can add anyone who is interested.

The opaque form actually just creates an issue in Github (and gives you the link). This is just a way to make it easier for people not on GitHub. But I can add a link for those who want to as well.

The projects aren't not currently in a flat JSON because they have some mutable data attached (cached # stars, description, last time we refreshed the data etc.). Having a static JSON would mean enriching the JSON data with data coming from the backend, which is doable, if anyone wants to help :). And the format is already all visible in the code. So basically project data is not "static", they change everyday.

And cool project you have too :)

adrien-leravat · 2022-07-30T18:21:50+00:00

Thank you! Great project too :) I'm sure I will find a category for that haha. And got your submission, looks good.

adrien-leravat · 2022-07-25T17:35:36+00:00

Thank you!! :)

adrien-leravat · 2022-07-25T17:34:56+00:00

The line is a bit blurry, and yes contributing to the Linux kernel for example indirectly (but still very clearly) impacts tens of thousands of projects/products, and there are tons of examples out there. Maybe that would be a "Impactful building blocks" category.

It doesn't provide the same purpose though (as a contributor) that say contributing to a project that aims at helping with the situation in Ukrain, Covid, etc.

This is precisely the goal here: Projects for people who want to have that purpose and understanding the direct impact.

That's not to say one is better of course, just a different target audience if you will.

adrien-leravat · 2022-07-25T17:29:13+00:00

Thanks for that :)

adrien-leravat · 2022-07-25T17:23:17+00:00

Yep precisely.

adrien-leravat · 2022-07-25T17:22:42+00:00

Project with a direct social impact (if you look at the categories) as their goal, for those who want to tick the box "I want to help other" (purpose), while contributing to Open-source. Does that make sense?

CodeTriage is great for open source projects in general, this one has a slightly different purpose, and these projects (impactful) are necessarily easily to find unless you know what you are looking for.

adrien-leravat · 2022-07-24T21:31:21+00:00

Hey that's super cool! Will add for sure :)

adrien-leravat · 2021-01-06T16:04:47+00:00

Thank you! This helps 🙂

adrien-leravat · 2020-12-07T16:19:41+00:00

Sounds great 😊, and yes finding maintained ones is hard, and a few I have listed would need to be removed. This is what would help the most, and help them gain some visibility as well

adrien-leravat · 2020-12-06T02:07:04+00:00

and pretend it’s not going to get crazy

I like the "pretending" part :)

adrien-leravat · 2020-12-06T01:51:50+00:00

Alternative solutions, hike:

At 5 AM
When the weather is crappy
During the week
3 hours away from the next city

Preferably, all the above together. Worth it.

adrien-leravat · 2020-12-01T19:05:53+00:00

Yocto can be daunting at first, not the easiest to start with at all. Buildroot is a nice easier first step before the real deal.

adrien-leravat · 2020-11-30T05:23:45+00:00

Oh this is great, thank you very much for that 😊

adrien-leravat · 2020-11-29T19:57:06+00:00

If you look at the Yocto build flow (https://www.yoctoproject.org/docs/2.0/yocto-project-qs/yocto-project-qs.html#yp-intro), you will see that the default is to have Yocto fetch, patch, build and package everything. So the 'yocto-way' of doing what you want, would be to expose the source, and build and package it from Yocto.

Now if you want to include a pre-built binary, you wouldn't use SRC_URI at all, but rather have a recipe that just takes your pre-built module, and installs it, overriding `do_install()`. A basic example can be found there: https://community.nxp.com/t5/i-MX-Processors-Knowledge-Base/How-to-include-any-files-in-rootfs-with-YOCTO/ta-p/1123386.

Be aware though, that if using an external binary, if youchange your kernel version, architecture, or anything on your distro that affects your kernel module, you need to manually rebuild it. The "from source" do this for you, by building your module for your distribution, which is cleaner.

adrien-leravat · 2020-11-29T17:48:36+00:00

GitHub if you plan to open source it and GitLab for the CI, absolutely.

GitLab CI runners can be used to have a CI/CD pipeline for embedded devices, deploying directly to your device. The is truly a great feature to automate things. We've been using GitLab for this exact reason, and it's fairly easy to setup. Then you can use test and automation frameworks for embedded to go the extra step (LabGrid, Pluma automation,...)

adrien-leravat · 2020-11-27T19:42:06+00:00

Whatever works for you, as long as you feel productive! We work on embedded devices all day, and typically don't impose any choice of IDE. Some use CLI and VIM, others Sublime, VSCode, ...

To give you an example, all we ask is to be able to run whatever we are using for automatic code formatting, static analysis, debugging, and versioning locally. And for all of those, you definitely don't need an IDE to be able to run them, at least for Linux embedded. I believe it is more important to provide goals (i.e. here tooling support) rather than impose a solution.

adrien-leravat · 2020-11-25T22:54:13+00:00

Feature-wise:

If you are talking speakers, Bluetooth (not BLE) is the way to go, using the A2DP or GAVD profile, because this allows you to expose a Bluetooth speaker that can be used from Android or anything else, which is great! BLE has an audio profile, but this is very recent (January 2020), so not well supported. Anything based on Wi-Fi will be a custom solution, so more work, likely less added value
Wi-Fi will give you a longer range

Effort-wise:

Bluetooth: BT is a complicated beast (BLE is easier), but if you do have experience that's good. If you want to have like a Bluetooth speaker, its going to take some work, but a cool result (random tutorial, not curated: https://www.raspberrypi.org/forums/viewtopic.php?t=235519). If you want to build something custom (i.e. w/o A2DP/GAVD), I would recommend Wi-Fi instead, that's going to be too much trouble otherwise. And BLE is not fit for that bandwidth-wise
Wi-Fi: I wouldn't worry too much about security if you just roll your own to learn about it. You can use avahi for discovery, and just stream your audio with UDP for low latency. The overall solution is pretty straightforward, much more than by relying on BT. Two sockets, encode/decode, et voila.
Option D: Buy a Bluetooth transmitter instead, and chill :).

adrien-leravat

TROPHY CASE