DragonFly 6.4.2

.
Read the full article on GamingOnLinux.
.
Read the full article on GamingOnLinux.
La licence professionnelle « CoLibre » (Métiers de la communication, conduite de projets et logiciels libres) ouvre sa seconde session de candidature jusqu’au 25 août 2025.
Pour mieux connaître ce parcours de formation, pour y candidater, pour proposer des alternances ou des projets tuteurés, des visios sont organisées pendant l’été.
Elles auront lieu le 24 juillet et le 18 août à 18h.
La licence pro forme en un an au métier de chef·f de projets en communication à l’ICOM (Université Lyon2) pour des personnes ayant acquis un bac+2 quelque qu’il soit.
Pendant une année, la formation organise un parcours varié pour acquérir et affirmer des compétences professionnelles dans les domaines de la communication, de la conduite de projet et les pratiques numériques.
Au fil du parcours, les étudiants et étudiantes vont aussi approfondir au choix une spécialisation : création numérique (PAO, infographie, audio-visuel, multimédia…), organisation (ressources humaines, pratique du changement, didactique, comptabilité…), développement (programmation, développement web, administration système…), événementiel (mercatique, planification, réseaux sociaux, gestion événement…).
Chaque fois que l’on utilise des logiciels ou des applications, elles sont systématiquement libres pour ajouter une connaissance approfondie et choisie du numérique en plus d’une approche éthique et inclusive.
Ce parcours est ouvert à toute personne ayant un bac+2 et elle peut être suivi en alternance, en formation continue ou en parcours classique.
À l’issue de la formation, les étudiantes et étudiants sont diplômés à Bac+3.
Attention la formation est réalisée en présentiel à l’Université Lyon2.
Commentaires : voir le flux Atom ouvrir dans le navigateur
MZLA Technologies Corporation has released an update to its open-source desktop email client Thunderbird.
Thunderbird 141 adds a small set of improvements for users of the monthly feature releases. While the tweaks aren’t substantial enough to tempt Extended Support Maintenance (ESR) users to switch, they’ll be a welcome addition for current users.
The preceding Thunderbird 140 release made it possible to customise the actions shown in new mail notifications on the desktop. Thunderbird 141 expands on that by making it possible to show an Archive action, alongside Mark as Read, Delete, Mark as Starred, and Mark as Spam.
A warning is now shown in the Composer if your configured OpenPGP key is due to expire in the next 31 days, which you can choose to ignore (but as a reminder, it’s likely to be helpful).
Exchange support in Thunderbird adds support for on-premise password authentication. The feature remains early, experimental and incomplete experience and for email only (adding accounts, managing folders, and writing, sending and reading email).
Thunderbird 141 fixes plenty of bugs and quirks, ranging from startup crashes to async errors, mis-named emoji and issues creating an event or task from an e-mail if the mail was opened in a tab.
A crop of security vulnerabilities get patched, including a snafu which allowed circumventing CORS with DNS rebinding, and a flaw in the “Copy as cURL” feature that (potentially) could be used to trick a user into executing unexpected code.
You can download Thunderbird for Linux, Windows and macOS from the official website. The downloads default to the monthly releases, so that will get you Thunderbird 141 (and that will update to 142, 143, and so on).
Existing users of the monthly release—the Thunderbird snap in Ubuntu tracks ESR releases—can update through the method they installed from, which for the standalone binary build (linked above) happens in-app, automatically when it’s open.
You're reading Thunderbird 141 Adds ‘Archive’ Notification Action & Fixes, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.
GitHub (and thus its owner, Microsoft) is calling for a new EU tech fund to ensure critical open source software can be maintained.
Its proposal, detailed in a report, stresses that our the economy relies on open source software (OSS) for digital infrastructure, but that maintenance ‘continues to be underfunded, especially when compared to physical infrastructure like roads or bridges’.
GitHub’s research says 96% of all codebases contain open source code, and OSS contributes an estimated $8.8 trillion to the global economy.
Yet, most open source projects get little-to-no funding. A third of projects, many linchpin dependencies in billion-dollar operations, are maintained by just a single person. Others get by on drive-by donations and volunteer contributors – goodwill for the greater good.
Given how widely many OSS components are, and how vulnerable they are to developer burnout, abandonment, or socially-engineered hijacking, the costs in not ensuring open source is in a healthy states are, in a sense, greater.
Infrastructure underpinning day-to-day life, powering the modern economy, balances on precarious foundations. Sustainable open source maintenance will ensure ongoing improvements and all-important security diligence for everything resting on top.
The solution, per Github’s report, is to scale up Germany’s Sovereign Tech Fund (STF) to a pan-European level.
Regular readers will be familiar with the STF since it has, in recent years, provided money to fund important initiatives within the GNOME project, ranging from accessibility work to new privacy and wellbeing features on the desktop.
This proposed EU-STF would give cash to widely-used, critical components to help sustain and support open source maintenance.
GitHub’s report recommends a starting budget of €350 million carved out of the bloc’s 2028-2035 budget, and using the money to action 5 key areas:
The funding would require the creation of a new, centralised EU institution (a ‘moonshot model’), or a group of EU member states willing to provide initial funding and then seek further resources from the EU budget (a ‘pragmatic model’).
As GitHub itself puts it: “The flip side of everybody benefiting from this open digital infrastructure is that too few feel responsible for paying the tab.”
The proposed fund would be directed at the ecosystem’s most critical, underfunded dependencies
Cold hard cash is the answer, and GitHub thinks the European Union should step in to spend public money to fill in the OSS funding gap.
Others in the Linux community already take a more direct approach.
Canonical is donating £120,000 in 2025 to the smaller open source projects it relies on to maintain the infrastructure, tooling and triage mechanisms in Ubuntu and adjacent projects.
The GitHub Secure Open Source Fund (and formerly, Microsoft’s FOSS Fund) do similar things.
The proposed EU-STF fund would not be a free-for-all (you couldn’t pitch a desktop widget and expect a wedge of polymer in return). Rather, it’d be strategically directed at the ecosystem’s most critical, underfunded dependencies for maintenance, security and improvement.
Github suggests the EU-STF start with a €350 million pool, but adds that this amount “…would not be enough to meet the open source maintenance need”, merely “form the basis for leveraging industry and national government co-financing that would make a lasting impact.”
While €350 million is a huge portion of EU’s budget it is veritable chump-change if viewed against the profits that big tech companies—remember those stats from earlier—generate each year.
I don’t disagree with the idea of funding OSS with public money since it open source is a public good. And the idea that a co-ordinated, centralised and (ideally) transparent funding process is needed is, to my mind, the logical approach – no self-beneficial backhanders.
But the cynic inside me is giving this proposal some side-eye.
If open source gets funding from the EU, it must happen lock-step with the EU pushing for adoption of open source in the public sector
Microsoft, like all of the big tech giants, relies heavily on OSS to keep its own profits ever-inflating. The idea that national governments—i.e., taxpayers—must stump up “or else” is a little (pardon the pun) rich given the rich benefit from them doing so.
The Scrooge McDuck money pits were dug out with the labour of hundreds of thousands of open source developers, and each coin clattering down to fill it up part-earned in the same way.
Open source maintainers deserve monetary support. Absolutely. It is vital that valuable talent and critical software is rewarded. I worry the creation of an EU fund at the behest of big tech might be a way for big tech to offload its own responsibilities to fund OSS.
So if open source is to get sustainable funding from the EU, it should happen in lock-step with the EU pushing the use of open-source in the public sector. This fund shouldn’t act as a sleight-of-hand subsidy for big tech to coast on.
What’s interesting from its blog post is that GitHub (and Microsoft) is not paying lip service to this idea. It’s pushing for it. It plans to meet with EU legislators to advocate for such a fund, and warn of the risks of inaction in not creating one soon.
Something has to be done, and an EU Sovereign Tech Fund is one way to address it — but those who milk the community cow for profit ought to pay most for its feed.
You're reading GitHub Wants the EU to Fund Open Source, a blog post from OMG! Ubuntu. Do not reproduce elsewhere without permission.