I had the same thought, as an OpenStack developer as well (TBH I don't remember if my username here identifies me or not). Yeah, we can apply as an exceptional case, but realistically us being excluded shows the criteria is very much directed towards "github style" open source.
I used to go to a members-only bar in Apex, NC (in NC, at least at the time, if >50% of your sales was alcohol, you had to be a "club"). The last time I ever went there was when someone called the bartender and "reported" a DUI checkpoint down the road and they announced it in the bar.
Why do some folks think it's OK to put other people at risk to this level?
Hard agree. I have their doorbell and some of the wifi light fixtures (that go into mains power). They integrate great with home assistant and record locally.
Thanks for posting this! It's been a nice first year as a Gentoo developer. Everyone has been kind and helpful to me as I've been figuring things out.
I want to highlight something: Gentoo's developer onboarding system is EXCELLENT. Starting as an active member of the general community, you talk an existing developer into being your mentor and fill out an open book test ( https://projects.gentoo.org/comrel/recruiters/quizzes/ebuild... ) which later is graded/corrected in a couple of meetings which I'd equate to the "job interview". I wish more open source projects (including my own) had such well-documented, straightforward processes to gain commit access. I appreciated the process of doing the quiz as it helped me close gaps in my knowledge.
With Red Hat, Anaconda is the installer.
With Ubuntu, ubiquity.
etc ...
With Gentoo -- YOU are the installer. This means you have to be ready to perform -- more or less manually -- many of the tasks automated in other distributions. I sorta see this as the same as a tutorial level in a video game: you learn how to read and follow the wiki which is essentially the key to success in Gentoo.
Gentoo is often at the forefront of identifying and helping resolve integration issues between different software projects, particularly when it comes to compiler tech (e.g. fixing packages so they can be built properly with LTO, or with LLVM as well as GCC) or other backend-detail-minutia which makes the whole system better without always being visible to the end user.
Honestly this is just sorta a Tuesday for an advanced Gentoo user? There are lots of ways to do this documented on the Gentoo wiki. Ask in IRC or on the Forum if you can't find it. "Catalyst" is the method used by the internal build systems to produce images, for instance https://wiki.gentoo.org/wiki/Catalyst.
This is called "digital sovereignty", and it has been a major topic for OpenInfra foundation and other open source cloud foundations. Open source, and open cloud software, is the way to ensure your data can stay inside your own borders and be governed by your local laws. https://www.youtube.com/watch?v=Lvz2PcHq0yY is one example of folks talking about this, but realistically you can find talks from OpenStack/OpenInfra going back 4/5 years on this topic.
In OpenStack, we explicitly document what our log levels mean; I think this is valuable from both an Operator and Developer perspective. If you're a new developer, without a sense of what log levels are for, it's very prescriptive and helpful. For an operator, it sets expectations.
FWIW, "ERROR: An error has occurred and an administrator should research the event." (vs WARNING: Indicates that there might be a systemic issue; potential predictive failure notice.)
Thank you, this (and jillesvangurp's comment) sounds way more reasonable than the article's suggestion.
If I have a daily cron job that is copying files to a remote location (e.g. backups), and the _operation_ fails because for some reason the destination is not writable.
Your suggestion would get me _both_ alerts, as I want; the article's suggestion would not alert me about the operation failing because, after all, it's not something happening in the local system, the local program is well configured, and it's "working as expected" because it doesn't need neither code nor configuration fixing.
Agreed, I don’t get the OPs delineation between local and non-local error sources. If your code has a job to do it doesn’t matter if the error was local or non-local, the operator needs to know that the code is not doing its job. In the case of something like you cannot backup files to a remote you can try to contact the humans who own the remote or come up with an alternative backup mechanism.
reply