# contribution Published articles for contribution. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## CoreOS 45 Test Week DevFeed: [CoreOS 45 Test Week]() Original publisher: [Read original article]() Author: Lukáš Růžička Published: 2026-09-16T08:00:00Z Content type: news Language: en Sources: [Fedora Magazine]() Topics: [Fedora](), [Testing](), [Wiki]() Tags: [2026](), [bugs](), [community](), [contribution](), [coreos](), [download](), [event](), [fedora-linux-45](), [fedora-project-community](), [qa](), [release](), [test-week](), [testing]() ### AI overview Fedora CoreOS and QA teams are organizing a Test Week beginning September 21, 2026, to help the community test Fedora CoreOS based on Fedora 45 content before it reaches the testing and stable streams. ### Source excerpt The Fedora CoreOS and QA teams are gearing up for Fedora 45, and we need your help! We are organizing a Fedora CoreOS Test Week starting on September 21, 2026. This event is a great opportunity for the community to test Fedora CoreOS (FCOS) based on Fedora 45 content before it officially reaches the testing [...] ## Behind the scenes: debugging a pool join failure DevFeed: [Behind the scenes: debugging a pool join failure]() Original publisher: [Read original article]() Author: Marc Pezin Published: 2026-07-20T09:48:38Z Content type: article Language: en Sources: [XCP-ng Blog]() Topics: [debugging](), [TLS (Transport Layer Security)](), [DevOps](), [Server]() Tags: [analysis](), [contribution](), [debugging](), [devblog](), [error-reporting](), [ntp](), [root-cause-analysis](), [tls]() ### AI overview This article follows the investigation of an XCP-ng pool join failure after an upgrade from version 8.2 to 8.3. The debugging process reproduced the issue, ruled out common TLS causes, identified the root cause, and resulted in an upstream contribution that improved error reporting. ### Source excerpt A user reported a pool join failure after upgrading to XCP-ng 8.3. What started as a forum discussion led to a root-cause analysis, an upstream contribution, and a better error message for everyone. ## Google Cloud: PostgreSQL community contribution updates DevFeed: [Google Cloud: PostgreSQL community contribution updates]() Original publisher: [Read original article]() Author: Google Open Source (noreply@blogger.com) Published: 2026-07-10T18:30:00Z Content type: article Language: en Sources: [Google Open Source Blog]() Topics: [PostgreSQL](), [Google Cloud Platform (GCP)](), [Google](), [Open Source](), [Replication]() Tags: [architecture](), [collaboration](), [community-contribution](), [conference](), [consensus](), [contribution](), [google](), [google-cloud](), [open-source](), [postgresql](), [replication](), [technical](), [updates]() ### AI overview Google Cloud recaps its participation in 2026 PostgreSQL community events, including discussions of logical replication, global index architecture, DDL replication, and AI-assisted development workflows. ### Source excerpt by Dilip Kumar, Cloud SQL for PostgreSQL & Matt Cornillon, Sales EMEA Google Cloud is deeply committed to the long-term success of the PostgreSQL ecosystem. Our involvement goes beyond providing PostgreSQL managed services; it's also about active participation in the open source communities through technical contributions, leadership in conference committees, and sharing architectural insights that benefit all users. Following is a recap of recent events Google Cloud participated in. PGConf.dev 2026 Serving as a vital developer-centric hub, PGConf.dev provides a unique opportunity for collaboration with the full assembly of senior PostgreSQL committers. This gathering is essential for aligning technical efforts and shaping the future project roadmap. Key Highlights Participation focused on strategic coordination with PostgreSQL committers regarding logical replication development, and a consultation on global index architecture. High community interest confirms the Global Index feature solves a vital architectural requirement for enterprises. Established community consensus to pursue a deparsing-based architectural approach for DDL replication. Google Cloud Sessions Dilip Kumar, a PostgreSQL contributor from Google Cloud, presenting "Experimenting with a Global Index in PostgreSQL" at pgconf.dev 2026 in Vancouver. He is speaking at a podium next to a presentation slide detailing the Global Index storage architecture and PartitionIdentifier management. Session Title Session Type Speakers/Led by Experimenting with a Global Index in PostgreSQL: Design, Implementation, and Challenges Technical Talk Dilip Kumar Unconference: Global Indexes Unconference Session Dilip Kumar Unconference: Logical Replication: Warts and Missing Pieces Unconference Session Hannu Krosing PGConf India 2026 Key Highlights The three-day conference was divided into a training day followed by two days of sessions. More than 580 participants attended the conference over three days. The conference se ## The Community Champions Program DevFeed: [The Community Champions Program]() Original publisher: [Read original article]() Author: Joseph Lyons Published: 2026-06-02T00:00:00Z Content type: opinion Language: en Sources: [Zed Industries - Blog]() Topics: [GitHub](), [Open Source](), [Pull Request](), [Code review](), [dashboards](), [Discord](), [Atom]() Tags: [2026](), [code](), [code-review](), [community](), [contribution](), [contributors](), [dashboards](), [discord](), [github](), [open-source](), [organization](), [people](), [pull-requests](), [quality](), [review](), [workflow]() ### AI overview Zed describes its Community Champions program, which formally recognizes active contributors who improve the project through code, issues, code review, and community engagement. The article explains how champions are identified and how their status helps signal contributions for prioritization. ### Source excerpt How we recognize our frequent contributors. ## 2024 Wrapped: Newsletter, Coaching, Books DevFeed: [2024 Wrapped: Newsletter, Coaching, Books]() Original publisher: [Read original article]() Author: Denis Čahuk Published: 2025-01-10T15:58:20Z Content type: opinion Language: en Sources: [Crafting Tech Teams]() Topics: [engineering-culture](), [CI/CD](), [Microservice](), [Testing](), [Publishing]() Tags: [articles](), [continuous-delivery](), [contribution](), [engineering-culture](), [software-architecture](), [testing]() ### AI overview A 2024 retrospective covering the author's newsletter, coaching, training, video and streaming activity, conference participation, book contribution, and community projects. It reports audience and activity metrics, including 63 Substack posts, 125,000 Substack views, 223 coaching sessions, and increased video watch hours. ### Source excerpt Big wins in 2024: Coaching and Training, Meeting Kent Beck, Dave Farley, Sander Hoogendoorn, Speaking at conferences, Book Contribution, Youtube Channel Success, groCTO ## Wrapping up the KZG Ceremony DevFeed: [Wrapping up the KZG Ceremony]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2024-01-23T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Transactions](), [Bot](), [GitHub]() Tags: [bots](), [contribution](), [contributors](), [cryptographic](), [devcon](), [ethereum](), [github](), [hash](), [open](), [research-development](), [transactions]() ### AI overview The article documents the 2023 KZG Ceremony, a 208-day multi-party computation that produced the cryptographic foundation for Ethereum's EIP-4844. It reports 141,416 contributions, explains participation and spam-prevention requirements, and provides the final transcript hash and availability information. ### Source excerpt The KZG Ceremony was the largest multi-party computation of its kind (by number of participants). Through an open, accessible process, it produced a secure cryptographic foundation for EIP-4844. Learn more about how the Ceremony worked in Carl Beekhuizen's Devcon talk: "Summoning the spirit of the Dankshard" As the... ## KZG Ceremony Special Contributions DevFeed: [KZG Ceremony Special Contributions]() Original publisher: [Read original article]() Author: Carl Beekhuizen; Trent Van Epps Published: 2023-08-02T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Software](), [Hardware]() Tags: [3d](), [contribution](), [contributions](), [ethereum](), [hardware](), [music](), [research-development](), [sensors](), [software](), [space](), [usb]() ### AI overview This post documents the Special Contribution Period of the KZG Ceremony, held from 1-16 April 2023. It explains how participants used varied methods, hardware, software, entropy-generation techniques, and group contributions to provide additional assurances, and links to records and media documenting the contributions. ### Source excerpt The Special Contribution Period for the KZG Ceremony ran 01-16 April 2023. This allowed participants to contribute in ways that may not have been possible in the Open Contribution period. While the Ceremony only needs a single honest participant to provide a secure output, Special Contributions provide additional assurances... ## Making Better Pull Requests DevFeed: [Making Better Pull Requests]() Original publisher: [Read original article]() Author: Eevis Panula Published: 2023-01-03T08:57:47.653000Z Content type: tutorial Language: en Sources: [Eevis Blog]() Topics: [pull-requests](), [Open Source](), [Maintainers]() Tags: [best-practices](), [context](), [contribution](), [discussion](), [maintainers](), [open-source](), [pull-requests](), [review](), [scope]() ### AI overview A tutorial on improving pull requests for open-source projects. It recommends keeping changes in scope, giving reviewers context, including pictures of changes, and using pull requests for discussion while checking each project's contribution guidelines and templates. ### Source excerpt Hactoberfest is here! Time to find those issues and participating repositories, write some code, and create pull requests! I've been eagerly waiting for October, mostly because of Hacktoberfest. Last year, I participated in Hacktoberfest by being a contributor and a maintainer. If you're interested, you can read about my blog post about last year's experiences: Eevis Panula - Story of an accidental open source maintainer This year, I decided to take it a bit easier. I mean, as mentioned in the blog post, last year we bought a house and were moving during October. Another challenging thing from last year was the maintainer part. I loved it, but it really, really stressed me out. So I'm not going to do it this year. And there's another piece to the puzzle this year as well: I'm switching jobs, so that's another reason to take it easy during this Hacktoberfest. One big part of Hacktoberfest is creating pull requests. I remember the first time I made a PR in an open-source repository. I didn't know the repository's maintainers, and it didn't have any guidelines for pull requests, such as a pull request template. I had no idea what the maintainer expected from a PR. I felt super anxious. If I had known back then what I know now, it would've been easier for me. So that's why in this blog post, I'm sharing some tips on how to make better PRs. These are the best practices I've picked up along the way. However, note that there might be some other conventions in the project you're contributing. Be sure to check them. There might be a pull request template or contribution guidelines. The tips I'm going to give are the following: Keep the pull request in scope Give context to the reviewer Add a picture of the changes Pull request is a place for discussion Keep the Pull Request in Scope One reason for keeping the PR in scope is that smaller PRs are always easier to review than those with lots of changes. Sometimes, of course, the feature you are working on is a big one, and thus ## New Keycloak maintainer: Michal Hajas DevFeed: [New Keycloak maintainer: Michal Hajas]() Original publisher: [Read original article]() Author: Stian Thorgersen Published: 2022-09-16T00:00:00Z Content type: article Language: en Sources: [Keycloak Blog]() Topics: [Keycloak](), [Authorization](), [Server](), [JavaScript]() Tags: [authorization](), [code](), [community](), [contribution](), [idm](), [issue](), [javascript](), [kerberos](), [keycloak](), [ldap](), [legacy](), [openid-connect](), [review](), [saml](), [server](), [sso]() ### AI overview Keycloak welcomes Michal Hajas as an official maintainer. The article highlights his contributions across Keycloak components, including Hot Rod storage and the new map storage, along with his work reviewing community contributions and helping with project discussions and issue triage. ### Source excerpt We are pleased to welcome Michal Hajas as an official maintainer of Keycloak. Michal has been with the Keycloak project since September 2015, and since that period has contributed to almost every component of Keycloak - core server, authorization services, adapters, javascript, code auto-generation, legacy operator - either by review or code contribution. Since his first involvement, he has steadily contributed code, currently ranked as #8 highest contributor. Lately, he has designed and co-developed Hot Rod storage and has been instrumental in overall establishing the new map storage. He reviews community contributions and offers help to finalize PRs, as well as participates in community discussions and issue triaging. He understands and respects the code of conduct, and in reviews helps maintaining it. ## Announcing the KZG Ceremony DevFeed: [Announcing the KZG Ceremony]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2022-01-16T00:00:00Z Content type: release Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Protocol (disambiguation)](), [Development](), [Network]() Tags: [collective](), [community](), [contribution](), [cryptographic](), [development](), [ethereum](), [network](), [protocol](), [research-development](), [scale](), [upgrade]() ### AI overview Ethereum announces the KZG Ceremony, a coordinated multi-party trusted setup intended to provide the cryptographic foundation for scaling efforts such as EIP-4844, also known as proto-danksharding. Participants contribute secrets to produce a structured reference string for KZG Commitments, with security depending on at least one participant keeping their secret concealed. ### Source excerpt High fees have made life difficult for travelers through these Dark Forests. The Pools of Mem once clouded, now clarified by the filter of 1559, reveal that they are not deep enough to sustain. Legends tell of a society flourishing under the abundance brought about by DankShard, of giant... ## EF-Supported Teams: Research & Development Update DevFeed: [EF-Supported Teams: Research & Development Update]() Original publisher: [Read original article]() Author: Ethereum Foundation Published: 2020-12-09T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [zero-knowledge](), [Zero-knowledge proof](), [Application Development]() Tags: [application-development](), [audit](), [contribution](), [development](), [ethereum](), [organizational](), [privacy](), [research](), [research-development](), [teams](), [update]() ### AI overview This Ethereum Foundation update reviews progress from EF-supported teams, including research and development related to Ethereum. It highlights the Applied ZKP team's Perpetual Powers of Tau ceremony, its participation and verification model, and related work on Semaphore and other Ethereum projects. ### Source excerpt Friends, Leaves have fallen for those in the global north, Summer is on the way in the south, and ETH is staked across the globe. The jolliest of holidays has arrived, the birth of the beacon chain. Moreover, incredible progress has been made in recent months by all EF... ## Refining the Gradle issue backlog DevFeed: [Refining the Gradle issue backlog]() Original publisher: [Read original article]() Author: Benjamin Muskalla Published: 2020-06-09T04:00:00Z Content type: article Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Pull Request]() Tags: [bugs](), [community](), [contribution](), [features](), [gradle](), [issue]() ### AI overview This article explains that Gradle's influx of community issues, feature requests, defects, and contributions has outgrown the team's capacity to manage the backlog regularly. It discusses the need to focus triage and engineering work on the issues and features that provide the most value to users. ### Source excerpt One of the biggest success factors of Gradle is its community. There is no day that goes by without users suggesting new features, finding and reproducing defects or opening a pull request with a contribution. We appreciate every single issue that users create. Thank you! Working on a successful project like Gradle comes with challenges, be it the number of questions and contributions or deciding which aspect has the highest priority for the team. Even though we don't like to accept it, we don't have infinite capacity. We want our teams to be able to focus on producing the most value for our users. That means fixing the right bugs and implementing the best features. Given the diversity of our community, this is not an easy task to do. We want to find the right features/defects to do together with our users and not be paralyzed by the sheer volume of things we could potentially do. Rationale As part of our daily work, we triage new issues that you create, decide which ones should go into the next release, and check which issues are the most voted by the community. All while actually fixing existing issues and implementing new features. We're quite happy and feel productive with our current workflow. One aspect we're not very good at right now is managing the rest of our backlog. The sheer volume of ideas and contributions coming from the outside outweighs the number of tasks we can tackle within a reasonable timeframe. Given how many issues there are on our backlog, be it features, bugs or questions, it is really tough to find the time to go through all of them regularly. We need to determine which bugs are still reproducible in more recent versions of Gradle and which use cases have been implemented (maybe by just using one of the new features). Approach As engineers, we sometimes struggle to close a defect even though it is not fixed. Several years ago, exactly that happened to myself. In a former life, my company had just hired our first product manager. She close ## Ember 2018 Priorities DevFeed: [Ember 2018 Priorities]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2018-05-19T02:26:19Z Content type: opinion Language: en Sources: [Edward Faulkner]() Topics: [Ember](), [Framework](), [Web Development](), [JavaScript]() Tags: [contribution](), [contributors](), [docs](), [ember](), [events](), [framework]() ### AI overview An Ember community contributor outlines 2018 priorities: complete major in-progress framework features and give newer contributors more ownership and leadership opportunities. ### Source excerpt We need to ship what we started and let our newer contributors shine and lead. ## A formal introduction to Ionut Goldan - Mozilla's new Performance Sheriff and Tool hacker DevFeed: [A formal introduction to Ionut Goldan - Mozilla's new Performance Sheriff and Tool hacker]() Original publisher: [Read original article]() Author: elvis314 Published: 2017-10-18T19:57:53Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Mozilla](), [toolchain](), [build times](), [Python](), [Front end](), [Material Design]() Tags: [build-times](), [community](), [contribution](), [developers](), [mozilla](), [performance](), [toolchain]() ### AI overview A Q&A introduces Ionut Goldan, Mozilla's performance sheriff and tool hacker. It describes his work handling Talos alerts and related performance data from Autophone, Build Metrics, AWSY, and platform microbenchmarks, followed by discussion of his background and earlier programming projects. ### Source excerpt About 8 months ago we started looking for a full time performance sheriff to help out with our growing number of alerts and needs for keeping the Talos toolchain relevant. We got really lucky and ended up finding Ionut (:igoldan ... Continue reading -> ## trivago Announces a $10,000 Monthly Sponsorship of Webpack DevFeed: [trivago Announces a $10,000 Monthly Sponsorship of Webpack]() Original publisher: [Read original article]() Author: Patrick Gotthardt Follow Published: 2017-08-02T00:00:00Z Content type: release Language: en Sources: [Trivago]() Topics: [Webpack](), [Open Source](), [Front end](), [Web Development]() Tags: [contribution](), [frontend](), [money](), [open-source](), [sustainability](), [webpack]() ### AI overview trivago announces that it will contribute $10,000 per month to the Webpack Open Collective to support the project's continued sustainability and innovation. ### Source excerpt trivago has decided to sponsor Webpack with a monthly contribution of $10,000 ($120,000/year). We hope that this will help to secure the continued innovation of the project. ## Making 20% Time Work DevFeed: [Making 20% Time Work]() Original publisher: [Read original article]() Published: 2016-01-29T00:00:00Z Content type: article Language: en Sources: [Joe Nelson]() Topics: [Open Source](), [Maintainers](), [GitHub](), [Code]() Tags: [apply](), [blog](), [blog-post](), [contribute](), [contribution](), [developers](), [experiments](), [github](), [how-to](), [maintainers](), [open-source](), [project](), [projects](), [teamwork](), [work]() ### AI overview The article explains how companies can structure employee "20% time," a weekly period for self-directed projects, so that it produces useful tools and open-source projects instead of becoming unproductive. It introduces a contribution matrix for coordinating teamwork and begins describing the BASEDEF contribution categories, including blogging about a project and applying it in another project. ### Source excerpt 2016-01-29 Following Google's lead many companies have instituted "20% time" for their employees. This is one day per week in which employees can work on projects of their own choosing. The practice keeps developers motivated and sharp, produces tools to solve company problems, and in the best case creates open source which builds prestige and helps recruitment. But there's one problem with twenty-percent time: it takes discipline to pull it off. ## mozregression - Engineering Productivity Project of the Month DevFeed: [mozregression - Engineering Productivity Project of the Month]() Original publisher: [Read original article]() Author: parkouss Published: 2016-01-11T14:47:05Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Firefox](), [Mozilla](), [Tool]() Tags: [bug](), [contribution](), [debug](), [documentation](), [engineering-productivity](), [firefox](), [firefox-for-android](), [irc](), [maintainers](), [mozilla](), [mozregression](), [regression](), [reporting](), [tool]() ### AI overview This article presents mozregression, a Mozilla Engineering Productivity project for finding regressions in Firefox and Firefox for Android. The tool downloads pre-built builds between known good and bad dates or changesets and uses bisection to identify the smallest range where a regression appears. It also describes its graphical interface, ongoing work, maintainers, contribution opportunities, and bug reporting. ### Source excerpt Hello from Engineering Productivity! Once a month we highlight one of our projects to help the Mozilla community discover a useful tool or an interesting contribution opportunity. This month's project is mozregression! Why is mozregression useful ? mozregression helps to find regressions in Mozilla projects like Firefox or Firefox on Android. It downloads and runs ... Continue reading mozregression - Engineering Productivity Project of the Month ## mozregression - new way for handling merges DevFeed: [mozregression - new way for handling merges]() Original publisher: [Read original article]() Author: parkouss Published: 2015-11-14T09:42:48Z Content type: article Language: en Sources: [Mozilla Automation]() Topics: [Testing](), [Mozilla]() Tags: [automation](), [contribution](), [integration](), [mozilla](), [mozregression](), [python](), [regression](), [taskcluster](), [test]() ### AI overview This article proposes improving mozregression's handling of merge commits during regression bisection. The approach uses Taskcluster builds to narrow the range, identifies the branch containing the merged commits, and bisects that push range. ### Source excerpt I am currently investigating how we can make mozregression smarter to handle merges, and I will explain how in this post. Problem While bisecting builds with mozregression on mozilla-central, we often end up with a merge commit. These commits often incorporate many individual changes, consider for example this url for a merge commit. A regression ... Continue reading mozregression - new way for handling merges ## mozregression 1.0.0 and GUI 0.4.0 updates DevFeed: [mozregression 1.0.0 and GUI 0.4.0 updates]() Original publisher: [Read original article]() Author: parkouss Published: 2015-09-12T10:23:57Z Content type: release Language: en Sources: [Mozilla Automation]() Topics: [releases](), [Mozilla]() Tags: [automation](), [contribution](), [mozilla](), [mozregression](), [mozregression-gui](), [release](), [updates]() ### AI overview This update announces mozregression 1.0.0 and a 0.4.0 release of its GUI. New capabilities include launching a single build, selecting a build after a skipped build, automatic update checks, and integration of the command-line tool as a Mozilla mach command. ### Source excerpt A lot of new things have been added in mozregression recently, and I think this deserve a blog post. I released mozregression 1.0.0! Plenty of new cool stuff in there, the ability to launch a single build, to choose the build to test after a skipped build (allowing to go back faster in the good/bad ... Continue reading mozregression updates! ## Contributing DevFeed: [Contributing]() Original publisher: [Read original article]() Published: 2015-05-24T12:00:00Z Content type: opinion Language: en Sources: [Jake Yesbeck]() Topics: [Open Source](), [Development](), [Pull Request](), [test-coverage](), [GitHub](), [Learning]() Tags: [contribute](), [contribution](), [contributors](), [github](), [learning](), [open-source](), [pull-request](), [test-coverage]() ### AI overview A personal account of learning to contribute to open source projects. The author describes adding test coverage to the pluck to hash project, having a pull request accepted, overcoming intimidation about open source contributors, and using GitHub Explore to find projects that may welcome contributions. ### Source excerpt Since starting this 365 day adventure, I have done a mixture of contributing to my own projects and to others. At the on-set, I made an assumption that it would be an even distribution of commits between my own projects and existing ones. However, this proved much harder than I originally thought. After a sizable amount of effort, I did find a few projects to contribute to. 28 days into this endeavor and seems like I might actually be able to accomplish my goal. One of the existing projects, pluck to hash, was a very young project when I found it. The project was released without any test coverage so I attempted to rectify that. Thankfully my pull request was accepted! It felt great to finally contribute to a project that wasn't my own. I also learned a few things by doing so. The first important learning from making a contribution was understanding that the caliber of contributors to open source software was not vastly superior to "normal" software engineers. I had previously thought of people who wrote open source libraries to be some sort of battle-tested, hardened, bug-resistant demi-gods sent here from Krypton in order to write code for us mortals. This was a very debilitating thought. For years it was a wall between me and open source software development. I didn't even entertain the idea of surpassing that wall and inevitably gave up on making meaningful contributions. Alright, that is probably a little dramatic but I think it makes my point for me. It was intimidating to contribute! Then, like a breath of fresh air, my pull request was accepted and these preconceptions vanished. It was awesome. It was super awesome (and objectively I didn't even do that much). A second learning from finding projects to contribute to was how to find them. It seems like an important thing to know, right? There are a few tools one can use to find projects that are ripe for the commit-in. Using the explore function on Github, you can find the top trending projects on a per langu