# Maintainers People who maintain open-source software projects and review contributions. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Reconnecting with the heart of open source: Highlights from our 2026 GSoC India tour DevFeed: [Reconnecting with the heart of open source: Highlights from our 2026 GSoC India tour]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-09-17T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [Open Source](), [Developer Events](), [Maintainers](), [Learning](), [pull-requests](), [systems]() Tags: [community](), [developer](), [developer-events](), [developers](), [events](), [google-summer-of-code](), [gsoc](), [maintainers](), [mentor](), [mentoring](), [mentorship](), [open-source]() ### AI overview Google's 2026 GSoC India tour brought together contributors, mentors, and open source maintainers in Bengaluru and Delhi. The article highlights how mentorship helps developers tackle difficult codebases, grow into community leaders, and build local open source ecosystems, while discussing the continuing importance of human context and maintainer attention in an AI-assisted world. ### Source excerpt by Mary Radomile, Stephanie Taylor & amanda casari, OSPO For over twenty years, Google Summer of Code (GSoC) has welcomed new developers into open source by pairing them with experienced mentors on real projects. This spirit is especially vibrant in India, which is home to more than 55% of all global GSoC participants over the last decade. This July, our team traveled across Bengaluru and Delhi to host a series of developer events and debut our first-ever GSoC Alumni CAMP, bringing together members of India's vibrant GSoC alumni community. We engaged directly with current and former GSoC Contributors, Mentors, and project maintainers, experiencing firsthand the passion and energy of the Indian developer ecosystem. Community stories: Learning to think and lead as an engineer In both Bengaluru and Delhi, a highlight of the trip was hearing directly how open source and GSoC have fundamentally changed how developers think and work. For many attendees, having a dedicated open source mentor through GSoC took the fear out of tackling new and intimidating codebases. One former participant told us they almost walked away from a distributed storage project because it felt too overwhelming: "Storage systems felt impossible. But great mentors taught me how to think, not just how to code." Another echoed that shift in perspective: "Why am I spending so much time thinking rather than coding? Then I realized that building products is actually about thinking more than coding. GSoC taught me to think like an engineer." That shift in mindset turns first-time contributors into long-term open source community leaders. We met one developer who submitted their very first pull request in 2023, started mentoring in 2024, and is now a lead maintainer for a major open source Android app. We also saw how new contributors to global projects can spark entire local ecosystems--like the Indian compiler community, which started with a few GSoC alumni and has rapidly grown into a 3,500+ member netwo ## Your Donations at Work: One Year of Sponsored Servo Development DevFeed: [Your Donations at Work: One Year of Sponsored Servo Development]() Original publisher: [Read original article]() Author: The Servo Project Developers Published: 2026-09-15T00:00:00Z Content type: article Language: en Sources: [Servo Blog]() Topics: [servo](), [Maintainers](), [pull-requests](), [Development]() Tags: [contributions](), [development](), [documentation](), [flaky-tests](), [maintainers](), [pull-requests](), [rust](), [servo](), [servo-engine](), [servo-rendering-engine](), [sponsored](), [web-browser](), [web-browser-engine](), [web-engine](), [web-rendering-engine]() ### AI overview A Servo maintainer reviews a year of part-time work funded by monthly donations, including nominating new maintainers, reviewing pull requests, filing contributor-focused issues, writing documentation, improving flaky tests, and supporting JavaScript engine integration work. ### Source excerpt Last September, the Servo project announced that long-time maintainer Josh Bowman-Matthews (@jdm) would work part-time on improving the Servo contributor experience, entirely funded by the monthly donations on OpenCollective and GitHub. In his own words, here is a look back over the past year! First of all, I am enormously grateful to everyone who financially supports Servo, as those donations have enabled me to devote significant time to a project that I care a lot about. Some highlights from that funded work that I'm proud of: I nominated 8 new maintainers I reviewed 1150 pull requests I filed 114 issues targeted at newer contributors (92% of them have been fixed) I wrote new documentation about borrow hazards, experimental features, the AI policy, finding things to do, and fixing stable and intermittent test failures On top of that, I spent time diagnosing unexpected failures in others' PRs and fixed numerous intermittent test failures that made merging PRs more difficult for everyone. A few pieces of work from this period that stand out to me: supporting a large scale rewrite of Servo's JS engine integration to address intermittent panics related to garbage collection--I reviewed lots of pull requests, but also filed many issues that enabled the work addressing the panics to be spread across many other contributors getting tagged in to help understand test failures, uncovering our broken window.open behaviour, and eventually making a lot of flaky tests more stable supporting another contributor's grant proposal to work on Servo that was approved! This role I've carved out means a lot to me--I've found a healthy balance that allows me to spend time with my family as well as make meaningful contributions to Servo, and I get to spend a lot of time looking for ways to make the project more accessible for others. A big thank you to everybody supporting the project and my work; each individual monthly donation makes a big difference! I'm excited to see what's possible i ## Emacs arbitrary code execution flaw DevFeed: [Emacs arbitrary code execution flaw]() Original publisher: [Read original article]() Author: jzb Published: 2026-09-14T15:20:00Z Content type: news Language: en Sources: [LWN.net]() Topics: [Lisp](), [vulnerability](), [Maintainers]() Tags: [cve](), [emacs](), [maintainers](), [release](), [vulnerability]() ### AI overview An incomplete fix for the Emacs arbitrary code execution flaw CVE-2024-53920 has been identified. Viewing or editing untrusted files in modes other than Emacs's Lisp mode can also trigger arbitrary code execution. The issue affects Emacs 24 and newer, with a minimal fix queued for Emacs 31.2; upstream maintainers do not expect to backport it to older releases. ### Source excerpt Sean Whitton has announced that the original fix for an arbitrary code execution flaw in Emacs (CVE-2024-53920) was incomplete. Bas Alberts discovered that viewing or editing untrusted files in modes other than Emacs's Lisp mode can also result in arbitrary code execution. This problem affects all Emacs versions affected by CVE-2024-53920. This means Emacs 24 and newer, and possibly also older versions. A minimal fix, attached, is queued up for release with Emacs 31.2. We (the Emacs upstream maintainers) don't expect to backport the fix to older Emacs releases ourselves. LWN covered the original vulnerability in December 2024. ## Security through obscurity is dead, and AI delivered the fatal blow DevFeed: [Security through obscurity is dead, and AI delivered the fatal blow]() Original publisher: [Read original article]() Author: Jessica Lyons Published: 2026-09-13T11:21:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Vulnerabilities](), [Maintainers](), [Chromium]() Tags: [ai](), [ai-agents](), [ai-and-ml](), [black-hat](), [chromium](), [exploits](), [maintainers](), [microsoft](), [open-source](), [security](), [vulnerabilities]() ### AI overview AI-driven bug discovery is exposing long-hidden vulnerabilities in commercial and open-source software, undermining security through obscurity. The article also notes that attackers can use AI to reverse-engineer patches and rapidly develop exploits. ### Source excerpt RIP, you won't be mourned ## Built for agents: Omarchy's pipeline moves to DigitalOcean DevFeed: [Built for agents: Omarchy's pipeline moves to DigitalOcean]() Original publisher: [Read original article]() Author: Paddy Srinivasan Published: 2026-09-09T15:30:15Z Content type: release Language: en Sources: [DigitalOcean]() Topics: [Digital Ocean](), [Linux](), [Open Source](), [Maintainers](), [Pull Request](), [Testing]() Tags: [agentic](), [agents](), [compute](), [digitalocean](), [infrastructure](), [linux](), [maintainers](), [news](), [open](), [open-source](), [qa](), [review](), [upgrade]() ### AI overview DigitalOcean is becoming the agentic compute provider for Omarchy, a keyboard-first Linux desktop built on Arch and Hyprland. Omarchy's production pipeline, packaging builds, pull request review agents, and QA testing now run on DigitalOcean infrastructure. ### Source excerpt Omarchy is a keyboard-first Linux desktop built on Arch and Hyprland by David Heinemeier Hansson (DHH), and its production pipeline, packaging builds, PR review agents, and QA testing, now run on DigitalOcean. Agent workloads don't behave like a typical web server. They're bursty and parallel: an agent spins up, does one job, and shuts down. Omarchy's pipeline is a real example of that pattern, and DigitalOcean infrastructure complements its needs. A single doctl command can provision a Droplet, run the job, call separately configured inference services, and destroy the Droplet when the work is done. Alongside the infrastructure move, DigitalOcean is joining the Omacom Foundation, the nonprofit that funds Omarchy's infrastructure and the open source projects it depends on, as a Founding Corporate Patron, and will serve as Omarchy's agentic compute provider. "I'm thrilled to have DigitalOcean become a Founding Corporate Patron of the Omacom Foundation, and our new agentic compute provider as well. We have such grand ambitions for Omarchy, and it's time we upgrade our technical infrastructure to match. Whether it's build servers for packaging, agent runners for PR reviews, or Droplets for QA testing, DigitalOcean simply has everything we need. They also have the right mindset for the future and our new age of agents. Couldn't imagine a better fit!" -- David Heinemeier Hansson, creator of Omarchy What's Next Coming soon, DigitalOcean and Omarchy plan to release a 1-click Omarchy Droplet available through the DigitalOcean Marketplace, enabling developers to quickly deploy the same environment used by the maintainers. ## The First Ever Zephyr Maintainers Forum DevFeed: [The First Ever Zephyr Maintainers Forum]() Original publisher: [Read original article]() Author: Zephyr Project Published: 2026-09-09T11:51:29Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Maintainers](), [Open Source]() Tags: [2026](), [blog](), [contributors](), [europe](), [event](), [events](), [industry-conference](), [location](), [maintainers](), [open-source](), [open-source-summit](), [summit](), [technical]() ### AI overview The Zephyr Maintainers Forum will take place on October 6, 2026, at the Prague Congress Centre alongside Open Source Summit Europe. Zephyr maintainers, contributors, and technical leaders will discuss the project's technical strategy, including testing, security, AI and LLMs, safety, performance, release planning, and maintainer workflows. The in-person sessions will not be recorded. ### Source excerpt On Tuesday, October 6, Zephyr maintainers, contributors and technical leaders will meet at the Prague Congress Centre for the first ever Zephyr Maintainers Forum. Co-located with Open Source Summit Europe, this forum offers the opportunity for the Zephyr community to discuss and decide strategic directions for the project. ## The First Ever Zephyr Maintainers Forum DevFeed: [The First Ever Zephyr Maintainers Forum]() Original publisher: [Read original article]() Author: Zephyr Project Published: 2026-09-09T11:51:29Z Content type: news Language: en Sources: [Zephyr Project]() Topics: [Maintainers](), [Open Source]() Tags: [2026](), [blog](), [community](), [contributors](), [czech-republic](), [event](), [events](), [industry-conference](), [location](), [maintainers](), [meetings](), [open-source](), [open-source-summit](), [summit](), [technical]() ### AI overview The first Zephyr Maintainers Forum will take place on October 6, 2026, in Prague alongside Open Source Summit Europe. Zephyr maintainers, contributors, and technical leaders will discuss the project's technical strategy, including testing, security, AI and LLMs, safety, power management, build systems, and platform scaling. ### Source excerpt On Tuesday, October 6, Zephyr maintainers, contributors and technical leaders will meet at the Prague Congress Centre for the first ever Zephyr Maintainers Forum. Co-located with Open Source Summit Europe, this forum offers the opportunity for the Zephyr community to discuss and decide strategic directions for the project. ## An RTOS for Ages Two and Up -- Zephyr Podcast #049 DevFeed: [An RTOS for Ages Two and Up -- Zephyr Podcast #049]() Original publisher: [Read original article]() Author: Benjamin Cabé Published: 2026-09-04T20:01:01Z Content type: article Language: en Sources: [Zephyr Project]() Topics: [Embedded Software Dev](), [Testing](), [Arduino](), [Hardware](), [Maintainers](), [GitHub](), [Robotics](), [Wi-Fi]() Tags: [arduino](), [blog](), [engineering](), [firmware](), [github](), [halow](), [hardware](), [harness](), [maintainers](), [open](), [podcast](), [robotics](), [test](), [zephyr]() ### AI overview Zephyr Podcast episode 049 covers open-firmware hardware that does not yet run Zephyr, hardware-in-the-loop testing with Twister's pytest harness, project growth and contributors, Arduino Core for Zephyr 1.0, maintainer news, new drivers and subsystems, Wi-Fi HaLow support, and Zephyr's robotics community. ### Source excerpt The Dato DUO and the Teenage Engineering catalogue: lovely open-firmware noise machines that do not run Zephyr ...yet! Using the pytest harness in Twister to coordinate a device under test... ## How we closed 1,500 GitHub issues in one month DevFeed: [How we closed 1,500 GitHub issues in one month]() Original publisher: [Read original article]() Author: Marcos Hernanz Published: 2026-09-04T04:00:00Z Content type: article Language: en Sources: [Next.js Blog]() Topics: [GitHub Issues](), [Next.js](), [AI-assisted coding](), [issue tracker](), [Maintainers](), [bug]() Tags: [agent](), [ai](), [bug](), [github-issues](), [issue-tracker](), [maintainers](), [next-js](), [sandbox](), [vercel]() ### AI overview The Next.js team describes using an AI research agent to help maintainers review an issue backlog, close outdated reports, and retain issues that still matter. ### Source excerpt How the Next.js team used an agent to research old reports and work through the issue backlog. ## Zephyr Project Welcomes Seven New Silver Members as Global Embedded Ecosystem Continues to Grow DevFeed: [Zephyr Project Welcomes Seven New Silver Members as Global Embedded Ecosystem Continues to Grow]() Original publisher: [Read original article]() Author: Maemalynn Meanor Published: 2026-09-03T09:00:07Z Content type: release Language: en Sources: [Zephyr Project]() Topics: [Embedded Systems](), [Embedded Software Dev](), [Open Source](), [linux foundation](), [real-time](), [Maintainers]() Tags: [announcements](), [collaboration](), [community](), [connectivity](), [deployment](), [ecosystem](), [embedded](), [firmware](), [linux-foundation](), [maintenance](), [news](), [open-source](), [security](), [summit](), [support](), [testing](), [zephyr]() ### AI overview The Zephyr Project announced seven new Silver members--Canonical, Dojo Five, GigaDevice, Morse Micro, Northern.tech, Siemens and Space Cubics--during its 10th anniversary. The project also introduced its first Community Awards, with winners to be announced at the Zephyr Developer Summit in Prague in October. ### Source excerpt The project celebrates its 10th anniversary with new member growth and the recipients of the first-ever Community Awards at Zephyr Developer Summit in Prague Summary The Zephyr Project marks its... ## Zephyr Project Welcomes Seven New Silver Members as Global Embedded Ecosystem Continues to Grow DevFeed: [Zephyr Project Welcomes Seven New Silver Members as Global Embedded Ecosystem Continues to Grow]() Original publisher: [Read original article]() Author: Maemalynn Meanor Published: 2026-09-03T09:00:07Z Content type: release Language: en Sources: [Zephyr Project]() Topics: [Embedded Systems](), [Embedded Software Dev](), [Open Source](), [linux foundation](), [Maintainers]() Tags: [2026](), [announcements](), [awards](), [community](), [ecosystem](), [embedded](), [linux-foundation](), [news](), [open-source](), [zephyr]() ### AI overview The Zephyr Project announced seven new Silver members--Canonical, Dojo Five, GigaDevice, Morse Micro, Northern.tech, Siemens, and Space Cubics--as it marks its 10th anniversary. The announcement also covers the first Zephyr Community Awards and the upcoming Zephyr Developer Summit in Prague. ### Source excerpt The project celebrates its 10th anniversary with new member growth and the recipients of the first-ever Community Awards at Zephyr Developer Summit in Prague Summary The Zephyr Project marks its... ## Djangonaut Space - Session 7 Accepting Applications DevFeed: [Djangonaut Space - Session 7 Accepting Applications]() Original publisher: [Read original article]() Author: Djangonaut Space Mission Control Published: 2026-09-01T17:13:15Z Content type: news Language: en Sources: [The Django weblog]() Topics: [Maintainers](), [Code](), [Pull Request]() Tags: [applications](), [community](), [discord](), [django](), [framework](), [leadership](), [learning](), [maintainers](), [open-source](), [pull-request](), [python]() ### AI overview Djangonaut Space is accepting applications for its seventh cohort, a free eight-week group mentoring program that helps people contribute to Django and potentially develop future leadership roles in its community. ### Source excerpt We are thrilled to announce that Djangonaut Space, a mentorship program for contributing to Django, is open for applicants for our next cohort! 🚀 Session 7 launches October 12th, 2026. We are currently accepting applications until September 6th, 2026 Anywhere on Earth. More details can be found in the website. Djangonaut Space is a free, 8-week group mentoring program where individuals will work self-paced in a semi-structured learning environment. It seeks to help members of the community who wish to level up their current Django code contributions and potentially take on leadership roles in Django in the future. Rodrigo Vieira, Djangonaut Session 6 "Participating as a mentee in the Djangonaut Space was a highly valuable experience. The program provided clear, step-by-step guidance on how to navigate the core framework, find the right issues to tackle, and confidently send my PRs. Beyond the code, the community on Discord was very active, sharing experiences, wins and support. We had access to regular talks, Django Fellows and long-time maintainers who generously shared their time and expertise. It was a welcoming environment to connect with other newcomers from all over the world, allowing us to share our journeys and learn together. The highlight of the program for me was seeing my first pull request finally merged and mentioned in Django News. I'm looking forward to keep involved as an alumni and help others now." Eliana, Djangonaut Session 1 "I'm so grateful to have been a part of the Djangonaut Space program. It's a wonderfully warm, diverse, and welcoming space, and the perfect place to get started with Django contributions. The community is full of bright, talented individuals who are making time to help and guide others, which is truly a joy to experience. Before Djangonaut Space, I felt as though I wasn't the kind of person who could become a Django contributor; now I feel like I found a place where I belong." Enthusiastic about contributing to Django but ## What's new in Astro - August 2026 DevFeed: [What's new in Astro - August 2026]() Original publisher: [Read original article]() Author: Sarah Rainsberger Published: 2026-08-31T00:00:00Z Content type: news Language: en Sources: [The Astro Blog]() Topics: [Astro](), [releases](), [GitHub](), [Maintainers]() Tags: [astro](), [community](), [event](), [github](), [maintainers](), [releases](), [web]() ### AI overview Astro's August 2026 ecosystem update highlights Astro 7.2, new community and support initiatives, an Astro Playground powered by a real Astro Compiler instance, upcoming maintainer events, and examples of sites built with Astro. ### Source excerpt August 2026 - Project Steward announcement, new Astro Playground, Astro Germany, and more! ## OpenClaw went viral. Meet the maintainers building and securing it. DevFeed: [OpenClaw went viral. Meet the maintainers building and securing it.]() Original publisher: [Read original article]() Author: Gregg Cochran Published: 2026-08-27T16:00:00Z Content type: article Language: en Sources: [GitHub Engineering]() Topics: [OpenClaw](), [Maintainers](), [pull-requests](), [GitHub](), [Code review](), [supply-chain-security](), [Security](), [Artificial Intelligence]() Tags: [agent](), [agents](), [ai](), [ai-agents](), [blog](), [code](), [contributors](), [developers](), [development](), [github](), [maintainers](), [open-source](), [openclaw](), [pull-request](), [pull-requests](), [review](), [security](), [supply-chain]() ### AI overview OpenClaw maintainers discuss the project's rapid growth, the resulting flood of pull requests, contributor trust, code review, software supply chain risks, and security. They describe welcoming contributions from first-time contributors, non-developers, and people using AI agents while refining promising changes. ### Source excerpt OpenClaw is the fastest-growing project in GitHub history. Peter Steinberger and several maintainers share what they learned in the project's first six months. The post OpenClaw went viral. Meet the maintainers building and securing it. appeared first on The GitHub Blog. ## Announcing our first Maintainers in Residence DevFeed: [Announcing our first Maintainers in Residence]() Original publisher: [Read original article]() Author: Lori Lorusso, Jakub Beránek Published: 2026-08-26T00:00:00Z Content type: article Language: en Sources: [Rust Blog]() Topics: [Rust](), [Maintainers](), [Amazon Web Services](), [Google](), [OpenAI]() Tags: [aws](), [blog](), [contributors](), [google](), [maintainers](), [openai](), [rust](), [support]() ### AI overview The Rust Project announces its first Maintainers in Residence and Maintainer Grant recipients, with funding for at least 12 months through the Rust Foundation Maintainers Fund. The article explains the program's support categories, selection process, and focus on strengthening critically underfunded, high-impact Rust teams. ### Source excerpt We are very happy to announce the Rust Project's first round of Maintainers in Residence: Gen Li (@rami3l), Chris Denton (@ChrisDenton), Alejandra González (@blyxyas), León Liehr (@fmease), and Maintainer Grant recipients: Jason Newcomb (@Jarcho) and Jonas Böttiger (@joboet). These contributors will be funded for their rust-lang maintenance activities for (at least) the following 12 months! The funding of the Maintainer in Residence (MiR) and Maintainer Grantee roles is possible thanks to generous donations to the Rust Foundation Maintainers Fund (RFMF) from Google, AWS, OpenAI, the Rust Project Leadership Council and also individual sponsors. We also want to thank the people who advocated for maintainer funding within their companies; Tyler Mandry from Google, Niko Matsakis and Jess Izen from AWS and Predrag Gruevski from OpenAI, and also the whole Rust Leadership Council and our funding advisors. If you would like to help us support even more Rust contributors, consider donating to RFMF. The Rust Foundation has published a press release and a blog post, where you can learn more about the sponsors and the supported contributors. Read more below to learn about the MiR program, how we chose the funded contributors, and of course who they are! Background The Maintainer in Residence program, established in RFC 3931, is designed to provide stable financial support for Rust contributors, so that they can truly focus on crucial maintenance activities. Currently, there are three categories of support that we offer: Full-time MiR: funded for 5 days/week of Rust Project work Half-time MiR: funded for ~2.5 days/week of Rust Project work Maintainer Grant: funded for ~1 day/week of Rust Project work Funding for this program comes from the Rust Foundation Maintainers Fund, which was launched recently, and the whole program is managed by the Rust Funding team. When deciding who to fund, we took a systematic approach. First, we looked at Rust teams to understand their maintenance ## AI Made Code Generation Cheaper, but Developer Judgment Still Depends on Context DevFeed: [AI Made Code Generation Cheaper, but Developer Judgment Still Depends on Context]() Original publisher: [Read original article]() Author: Paweł Ostromecki Published: 2026-08-24T15:52:12Z Content type: opinion Language: en Sources: [Daniel Glejzner]() Topics: [Code](), [Artificial Intelligence](), [Angular](), [Maintainers](), [Dependency injection](), [Testing]() Tags: [agent](), [ai](), [angular](), [code](), [dependency-injection](), [developer](), [maintainers](), [testing]() ### AI overview This opinion article argues that AI has made code generation, syntax recall, and familiar implementations less scarce, but has not eliminated the value of developer knowledge. The author emphasizes that evaluating solutions for a real system still depends on product, codebase, team, failure costs, and future changes. It also notes that productivity findings vary by AI tool, developer experience, and task, citing differing METR results. ### Source excerpt When implementation becomes abundant, selection becomes the work. For roughly eight years, I had a simple model of becoming a better developer. Read the documentation. Learn Angular properly. Understand RxJS, dependency injection, change detection, testing, state management, architecture. Look at how other people solve problems. Make enough mistakes to understand ## Turn a framework roadmap into an application decision record DevFeed: [Turn a framework roadmap into an application decision record]() Original publisher: [Read original article]() Published: 2026-08-18T00:00:00Z Content type: tutorial Language: en Sources: [Koin - Cloud-Inject.io -Kotzilla]() Topics: [Framework](), [Maintainers](), [Documentation]() Tags: [framework](), [guide](), [maintainers](), [roadmaps](), [validation]() ### AI overview A practical guide to turning framework roadmap items into application decision records. It recommends classifying roadmap items by availability and stability, evaluating them against concrete problems and current documentation, recording fallbacks and constraints, and setting a review trigger before considering architectural changes. ### Source excerpt Framework roadmaps are useful because they show where maintainers expect the design to move. They are not release guarantees and they do not replace an application's own constraints. Convert roadmap items into explicit questions before changing architecture. Classify each item Place a roadmap item in one of four groups: available and documented; available but experimental; announced but not released; or directional only. Only the first group should normally support a production decision without added risk controls. For experimental work, record the fallback and the boundary that contains it. ## From Search to Search & Apache Lucene: Growing the heart of OpenSearchCon DevFeed: [From Search to Search & Apache Lucene: Growing the heart of OpenSearchCon]() Original publisher: [Read original article]() Author: Kris Freedain Published: 2026-08-14T21:57:12Z Content type: article Language: en Sources: [OpenSearch]() Topics: [Library](), [Maintainers]() Tags: [2026](), [apache](), [blog](), [community](), [event](), [opensearch](), [search]() ### AI overview Community feedback led OpenSearchCon to expand its Search track into Search & Apache Lucene, creating a dedicated forum for Lucene practitioners, maintainers, and search relevance experts. The article describes the revised track and the strong response to its call for presentations for OpenSearchCon North America 2026. ### Source excerpt Learn how community feedback transformed OpenSearchCon's Search track into a dedicated home for Apache Lucene practitioners. Discover the new Search & Apache Lucene track at OpenSearchCon North America 2026, September 22-24 in San Jose. The post From Search to Search & Apache Lucene: Growing the heart of OpenSearchCon appeared first on OpenSearch. ## The Nixpkgs core team has disbanded DevFeed: [The Nixpkgs core team has disbanded]() Original publisher: [Read original article]() Author: qyliss Published: 2026-08-07T21:39:34Z Content type: opinion Language: en Sources: [Announcements - NixOS Discourse]() Topics: [Maintainers](), [GitHub](), [incident]() Tags: [github](), [governance](), [incident](), [maintainers](), [nixpkgs-core-team]() ### AI overview The Nixpkgs core team announces its dissolution, citing an unsustainable workload, attrition, insufficient recruitment, and governance and communication problems with the Steering Committee. The team also describes work completed during its 10-month tenure. ### Source excerpt The Nixpkgs core team has unfortunately decided to disband. We're proud to have had the opportunity to lead by example in bottom-up, consensus-focused governance for Nixpkgs, and of our achievements over the past 10 months, including reforming the committer delegation process and onboarding 19 new committers, empowering maintainers by extending the merge bot, re-establishing contact with GitHub and securing the sponsored Enterprise Cloud upgrade, helping triage GHSA-67f2-674w-6g63 and track the GitHub security risks exposed by that incident, and establishing an initial automation/AI policy, as well as helping resolve many incidents that were escalated to us. However, it has sadly not turned out to be the lightweight role compatible with active technical contribution that we had originally hoped it would be, and two weeks ago we reached the conclusion that stepping down is necessary for our health. We believe that it's unsustainable for the team to continue, as demonstrated in part by our attrition to date. With only one person actively applying in response to our call for new members and mixed response to outreach, recruiting sufficiently to keep things healthy looks untenable. Therefore, especially with a Steering Committee election due imminently, we think the best way forward for Nixpkgs governance is to be honest about the circumstances that have made dissolving the team unavoidable, in the hopes that it may help future efforts. Our experience is that the Steering Committee as an institution lacks a native instinct for the delegation envisioned by the constitution, while also not being sufficiently engaged and cohesive to handle individual decisions at those levels itself. This manifests as unnecessary micromanagement of teams below them and chronically poor communication, including lack of clarity from SC members about when they're speaking for themselves or representing a joint position, matters brought to our attention with desired outcomes already attached, ## Python 3.15.0 candidate 1 is here! DevFeed: [Python 3.15.0 candidate 1 is here!]() Original publisher: [Read original article]() Author: Hugo van Kemenade Published: 2026-08-04T00:00:00Z Content type: release Language: en Sources: [Python Insider]() Topics: [Python](), [releases](), [Maintainers](), [Compiler](), [JIT](), [Linux](), [macOS](), [Windows]() Tags: [documentation](), [jit](), [linux](), [macos](), [maintainers](), [performance](), [python](), [release](), [releases](), [windows]() ### AI overview Python 3.15.0rc1 is the first release candidate in the Python 3.15 series. The article asks third-party maintainers to test the release, publish compatible wheels, report issues, and complete documentation before the final release. ### Source excerpt Get those wheels rolling! ## curl Maintainers Report on a Month-Long Pause in Vulnerability Reporting DevFeed: [curl Maintainers Report on a Month-Long Pause in Vulnerability Reporting]() Original publisher: [Read original article]() Author: Daniel Stenberg Published: 2026-08-03T06:42:19Z Content type: opinion Language: en Sources: [Daniel Stenberg]() Topics: [cURL](), [Maintainers](), [Open Source](), [Vulnerabilities]() Tags: [curl](), [curl-and-libcurl](), [maintainers](), [open-source](), [pull-requests](), [security](), [vulnerability]() ### AI overview curl maintainers describe the results of pausing vulnerability reporting for the month of July 2026. They report receiving no actionable vulnerability reports during the pause, feeling relief, and using the time to review pull requests, improve documentation, and recharge. ### Source excerpt At this exact moment curl's summer of bliss 2026 ends. We (the maintainers of curl) took the entire month of July off from vulnerability reporting and in this post I will try to explain how this went. (If you feel like skipping the wordy blab below, the single word answer is: fine) This was possibly ... Continue reading What the bliss taught us -> ## From Campus to Community Part 4: How Academia Plugs In DevFeed: [From Campus to Community Part 4: How Academia Plugs In]() Original publisher: [Read original article]() Author: Nithya Ruff Published: 2026-07-28T13:37:36Z Content type: article Language: en Sources: [Linux Foundation - Blog]() Topics: [Open Source](), [linux foundation](), [Linux](), [Kernel](), [Maintainers]() Tags: [linux](), [linux-foundation](), [maintainers](), [mentoring](), [open-source]() ### AI overview This fourth and final article in a Linux Foundation series explains how students can enter the open-source ecosystem through programs including LFX Mentorship, Linux Kernel Mentorship, and Google Summer of Code. It highlights practical contributions, mentorship, and preparation before applications open. ### Source excerpt This is a series from Linux Foundation Board Chair, Nithya Ruff. Read Part One, Part Two and Part Three. ## Linus Torvalds's Shift from Writing Linux Code to Leading the Project DevFeed: [Linus Torvalds's Shift from Writing Linux Code to Leading the Project]() Original publisher: [Read original article]() Published: 2026-07-25T11:20:55Z Content type: article Language: en Sources: [Antirez]() Topics: [Linux](), [Kernel](), [Maintainers](), [Open Source](), [Unix](), [C](), [ESP32](), [Raspberry Pi](), [Rust]() Tags: [c](), [esp32](), [linux](), [linux-kernel](), [maintainers](), [open-source](), [raspberry-pi](), [rust](), [unix]() ### AI overview The article argues that Linus Torvalds's distinctive contribution was not only writing the first Linux kernel, but also shifting early to project leadership, coordination, and delegation. ### Source excerpt (This blog post was adapted from the transcription obtained from my YouTube video at https://www.youtube.com/watch?v=l6lxgYeVZqs) When Linus Torvalds developed the first Linux kernel, he had studied the Minix sources, he had studied computer architecture, he had the base knowledge needed, and he was obviously a very brilliant programmer. But that operation of writing a minimal yet working Unix kernel for the 386 (at the beginning Linux was, let's say, mono-architecture) was something within the reach of many other programmers and students. Many in the sense of, I don't know, 0.1%, one in a thousand, one in ten thousand. Obviously most people are not able to do this kind of feat, but a lot of people are. If you look at Hacker News in the latest years, you'll see how many projects of kernels written in C, microkernels implemented from scratch, kernels written in Rust, kernels made in all sauces and manners, small Unix systems created vertically for the Raspberry Pi, operating systems for the ESP32 and so forth. Writing a kernel is not something within everybody's reach, but it is something that many can complete, if they put enough effort into it. Then, of course, not everybody will do it well. He is a genius programmer, without any doubt, so he did it better. And yet, of Linus there is only one. This implementative capacity of his, in fact, would not tell us much about him: what we should focus on, instead, is what happened later. ## He stopped writing code Among the maintainers of the famous open source projects, he was one of the very few that, very early in the history of the development of Linux, almost completely stopped writing code in order to concentrate on the leading of the project. On being the leader, the coordinator, the single mind holding the clarity about what the goals of the project must be, and so on. And this is a rare thing. Many maintainers (myself included, for a long time) continue instead to implement things directly, to not delegate much, an ## Get Ready: 2026 Python Packaging Council Nominations Opening Soon! DevFeed: [Get Ready: 2026 Python Packaging Council Nominations Opening Soon!]() Original publisher: [Read original article]() Author: Pradyun Gedam Published: 2026-07-23T00:00:00Z Content type: article Language: en Sources: [Python Insider]() Topics: [Python](), [interoperability](), [Maintainers]() Tags: [community](), [interoperability](), [maintainers](), [python](), [user-experience]() ### AI overview The Python Packaging Council's inaugural election opens for nominations on July 28, 2026, and closes on August 11. The council will guide interoperability specifications for building, distributing, and installing Python packages, while coordinating maintainers, the Python core team, and the wider community. ### Source excerpt The inaugural Python Packaging Council election nomination period opens on Tuesday, July 28th, 2:00 pm UTC and closes on Tuesday, August 11th, 2:00 pm UTC. [Next page]()