# contributions Published articles for 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. ## Mojo 1.1 Released, Now Accepting Community Contributions To The Compiler DevFeed: [Mojo 1.1 Released, Now Accepting Community Contributions To The Compiler]() Original publisher: [Read original article]() Author: Michael Larabel Published: 2026-09-17T16:26:41Z Content type: release Language: en Sources: [Phoronix]() Topics: [releases](), [Compiler](), [Code](), [Development](), [Nvidia](), [Qualcomm](), [GitHub]() Tags: [ai](), [amd](), [code](), [compiler](), [contributions](), [desktop-linux](), [development](), [github](), [language](), [linux-benchmarking](), [linux-hardware-benchmarks](), [linux-hardware-reviews](), [linux-how-to](), [linux-performance](), [linux-server-benchmarks](), [nvidia](), [open](), [open-source-graphics](), [performance](), [phoronix](), [phoronix-test-suite](), [qualcomm](), [releases](), [standard-library](), [ubuntu-benchmarks](), [ubuntu-hardware]() ### AI overview Mojo 1.1 and MAX 26.6 have been released. Mojo 1.1 adds inferred member references, improved compile times, better generated code performance, and more stable standard-library APIs, while the development process now accepts community contributions to the compiler. MAX 26.6 adds audio generation support and kernel speedups across AMD and NVIDIA GPUs. ### Source excerpt Last month Modular's Mojo language was open-sourced following the acquisition of Modular by Qualcomm. Modular was the AI startup founded by Chris Lattner of LLVM and Swift fame. Released today was Mojo 1.1 and also marks the project recently now beginning code contributions from the community to its compiler... ## Honoring #IconsOfQuality: Ash Winter DevFeed: [Honoring #IconsOfQuality: Ash Winter]() Original publisher: [Read original article]() Author: Rajrupa Roychowdhury Published: 2026-09-16T08:21:31Z Content type: opinion Language: en Sources: [BrowserStack Blog]() Topics: [Testing](), [Artificial Intelligence](), [Large Language Model](), [Development]() Tags: [contributions](), [icons-of-quality](), [testing](), [thought-leadership]() ### AI overview BrowserStack highlights Ash Winter as an influential figure in software testing and quality. The article describes Winter's work in testability, exploratory testing, community collaboration, and the use of automation pipelines and LLMs to support testers. ### Source excerpt To celebrate the relentless passion and invaluable contributions of leaders in software quality, BrowserStack is proud to honour Icons of Quality. ## Ruby 4.0.7 Released DevFeed: [Ruby 4.0.7 Released]() Original publisher: [Read original article]() Published: 2026-09-15T00:25:58Z Content type: release Language: en Sources: [Ruby-lang]() Topics: [Ruby](), [releases](), [bug]() Tags: [2026](), [bugfixes](), [contributions](), [download](), [release](), [release-schedule](), [releases](), [ruby](), [sha256](), [xz](), [zip]() ### AI overview Ruby 4.0.7 has been released as a routine update containing bugfixes. The article says Ruby 4.0.8 is planned for November, with earlier release possible if a significant user-impacting change arises. ### Source excerpt Ruby 4.0.7 has been released. This is a routine update that includes bugfixes. Please see the GitHub releases for further details. Release Schedule We intend to release the latest stable Ruby version (currently Ruby 4.0) every two months following the most recent release. Ruby 4.0.8 will be released in November. If a change arises that significantly affects users, a release may occur earlier than planned. Download https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.7.tar.gz SIZE: 23937964 SHA1: 730d4f8cebb60a1f5b556e7b58d86d0301772558 SHA256: 911ace20f90d068ca0e4dda6d0e4f0f81e52e52f2dd4f4004c721e253412e82d SHA512: ca6fb2df4b39967f1a92399ab70579216f2a87e600d127a616d4a81a3c92b25ebf35849502a2c12e2251d69e67eade3888af4a41b8844054d5c774f07c237c6d https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.7.tar.xz SIZE: 17995980 SHA1: 7d2307f975b1fef4e0ffe5cfe13067f993b5a4c2 SHA256: 47ef59413f7a4587ba6a6b78b14036eb5e36eec2ec0b90964801e88d56a3d375 SHA512: d1d345c25bff43aa86f536b22cd04746a7d3372077bf47ec75ef1820c0b43d0dbe3573dd5e5c55ee517796f46f0cdbd22c7506aebd06581241eefb5ffd9d2e5f https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.7.zip SIZE: 29248954 SHA1: 82b1bce8abb650e3080b96a0beff810b690dafa4 SHA256: c6f889c6dccd2625ae8d595bdee8e92afb3ddae3a1669bad67bb9f24d6af30ab SHA512: 5456ee1260921589cad5f0c57e84715e9c26b1f438a4c141157093c8e37e7e5d499a96c0ed35641f3cea1b741ecda2d72bfa3ce79fdbd5491784d9e6d181ac09 Release Comment Many committers, developers, and users who provided bug reports helped us make this release. Thanks for their contributions. Posted by k0kubun on 15 Sep 2026 ## 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 ## Ruby 4.0.4 Released DevFeed: [Ruby 4.0.4 Released]() Original publisher: [Read original article]() Published: 2026-05-11T21:41:38Z Content type: release Language: en Sources: [Ruby-lang]() Topics: [Ruby](), [releases]() Tags: [2026](), [bugfixes](), [contributions](), [developers](), [download](), [release](), [release-schedule](), [releases](), [ruby](), [sha256](), [xz](), [zip]() ### AI overview Ruby 4.0.4 has been released as a routine update containing bug fixes. The article provides download links, checksums, the planned Ruby 4.0 release schedule, and acknowledgments to contributors. ### Source excerpt Ruby 4.0.4 has been released. This is a routine update that includes bugfixes. Please see the GitHub Releases for further details. Release Schedule We intend to release the latest stable Ruby version (currently Ruby 4.0) every two months following the most recent regular release. Ruby 4.0.5 will be released in July, 4.0.6 in September, and 4.0.7 in November. If a change arises that significantly affects users, a release may occur earlier than planned, and the subsequent schedule may shift accordingly. Download https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.4.tar.gz SIZE: 23816838 SHA1: 3633db75e6b4848b509ecccc64704d8f4467f068 SHA256: f35f6edfa3dabb3f723f9d0cf1906c6512ae77f4e412ab1e68cc6e91d230fa80 SHA512: b0cc9af75ee25628483a32ecd5ea6477d637ee3c75795f411bc4ebde7d86ab754fddf96385cfc5955b9dbd016418cbd7178c82dad7876b2b7119238f5159ed3a https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.4.tar.xz SIZE: 17899740 SHA1: 9e070a8a78e6faa35382360b47526042657b236d SHA256: 6ff9d2d6e75f5a6f997222ecc45f79209d663737eceb3689d1f42ab952673fb7 SHA512: cccc041379fd4e46a736a5c10ccf81627766a7175113c34754797b915bebcd0ce821d9cd7b42cc616b0a1f9ee38eee5ab7560c1840fa6672819c293e498a3f6f https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.4.zip SIZE: 29122429 SHA1: 5edc7ce0adc2851a355673a5bb42b75efd4cf2b2 SHA256: 508bc83baed022c20671d69dd264e6783d61b89767b5d387c0f8efea00b62219 SHA512: b5db7ba616c56bdac9a61362d88d6350c8a8b59b5d812c1395476db73cb60fb403994e0bc3285aa2f57acbef3e30bcfce4bee4c5c8433b39d8f0a7c6dbb9bd29 Release Comment Many committers, developers, and users who provided bug reports helped us make this release. Thanks for their contributions. Posted by k0kubun on 11 May 2026 ## Ruby 4.0.3 Released DevFeed: [Ruby 4.0.3 Released]() Original publisher: [Read original article]() Published: 2026-04-21T08:45:44Z Content type: release Language: en Sources: [Ruby-lang]() Topics: [Ruby](), [bug]() Tags: [2026](), [contributions](), [cve](), [download](), [release](), [release-schedule](), [ruby]() ### AI overview Ruby 4.0.3 has been released as a security-focused update containing ERB 6.0.1.1, which fixes CVE-2026-41316. The article advises affected applications using Marshal.load on untrusted data with erb and activesupport loaded to update ERB. ### Source excerpt Ruby 4.0.3 has been released. This release only contains ERB 6.0.1.1, which fixes CVE-2026-41316. If your application calls Marshal.load on untrusted data AND has both erb and activesupport loaded, please update your ERB to 4.0.3.1, 4.0.4.1, 6.0.1.1, 6.0.4 or later. You may use this Ruby 4.0.3 release to do so. Release Schedule We intend to release the latest stable Ruby version (currently Ruby 4.0) every two months following the most recent regular release. Ruby 4.0.4 will be released in May, 4.0.5 in July, 4.0.6 in September, and 4.0.7 in November. If a change arises that significantly affects users, a release may occur earlier than planned, and the subsequent schedule may shift accordingly. Download https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.3.tar.gz SIZE: 23806898 SHA1: 619db0f25713a8f007d5889ae6e66ba0d31118e8 SHA256: 77964acc370d5c8375b9502e5ba6c13c03ef91ab9eb9f521c84fb42b9c9a6b0f SHA512: 6fd12620869a9a36fa2e1cce302de42f429ab9e9fae1fe3b0901ca1a1b3a606a83feed87f4b76935beb715e8a750cf718f88afef2de4e866ad574b33abb12dbe https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.3.tar.xz SIZE: 17878572 SHA1: faf1f3df171d2160116d190ca32b6b00e0338bfa SHA256: 22cf6005d25bbe496b5ebe9224d63a1aaabfbfe02591bb5d612517c5a7836f29 SHA512: 5816fb264ce76df59f4bfe0cadceb45025fada2e61f2c14024d6b03f63d304820cddf94afcf82a4951fd12f3b0d9148683f856f3f2245d56042fc8407b6cbff5 https://cache.ruby-lang.org/pub/ruby/4.0/ruby-4.0.3.zip SIZE: 29109899 SHA1: d19d91723d7a19a34b860eee8544093f64c9d92f SHA256: a80f1a3162950cfc1ef70f066132005efbb817f7ab6f16dcc244e5f015aabbc2 SHA512: 48b18fc578b5d7cd362a549ff5091c749d0460122f5dc3701fd6dada8016253fe0e85c498e20943e1a7f360b1e9fd073939da00df4b0c8a1afdddc16c43e43bc Release Comment Many committers, developers, and users who provided bug reports helped us make this release. Thanks for their contributions. Posted by k0kubun on 21 Apr 2026 ## Handling unreasonable expectations DevFeed: [Handling unreasonable expectations]() Original publisher: [Read original article]() Author: Sergio Visinoni Published: 2026-04-08T07:03:03Z Content type: opinion Language: en Sources: [Sudo Make Me a CTO]() Topics: [Artificial Intelligence](), [digital]() Tags: [ai](), [article](), [bug](), [contributions](), [launch](), [leadership](), [open-source](), [phishing](), [self-hosted](), [stakeholder-management]() ### AI overview The author discusses how to manage unreasonable expectations about AI-driven productivity improvements in digital companies, drawing on a conversation with a former client and offering practical tips. The article also includes a personal update about Rushomon, an open-source self-hosted project, including phishing-related abuse, community contributions, a paid tier, and a Product Hunt launch. ### Source excerpt A lot of unreasonable expectations are thrown around these days. In this article I offer concrete tips and examples that will help you manage them. Results are not guaranteed. At least I don't lie. ## Opening Proprietary Code to Contributors Checklist DevFeed: [Opening Proprietary Code to Contributors Checklist]() Original publisher: [Read original article]() Author: Daniel Doubrovkine (dblock@dblock.org) Published: 2026-04-08T00:00:00Z Content type: tutorial Language: en Sources: [Daniel Doubrovkine]() Topics: [ai-coding](), [pull-requests](), [Open Source](), [ci](), [GitHub]() Tags: [ai](), [ai-coding](), [ci](), [contributions](), [engineering](), [github](), [how-to](), [open-source](), [pull-request](), [tests]() ### AI overview The article presents a checklist for making proprietary software repositories easier and safer for newcomers and customer contributors to use. It recommends a discoverable CONTRIBUTING.md, a simple getting-started path, automated tests in CI, locally runnable minimum versions, documented deployment processes, and a GitHub fork-and-pull-request workflow. It frames AI coding tools as lowering barriers to meaningful contributions. ### Source excerpt Before AI coding assistants, a typical engineering team built expertise with the years: new team members joined, contributed small bug fixes, then were given more ambitious tasks over time as they became more comfortable in a codebase, to ultimately become experts. This process took years. In contrast, today, almost every engineer, and many non-engineers, have access to tools that can gather context from any codebase, and produce a large volume of high-quality code in a day. This lowers the bar for contributing meaningful changes to the software we build and enables many more individuals without domain or codebase expertise with good ideas to see them to light. At work, I asked my team to actively seek contributions from our customers with an active engagement for our proprietary code. Inspired by the open-source model, we are reviewing our systems from the angle of a newcomer easily contributing to them. Here's a checklist to apply to any repo. Create a single landing CONTRIBUTING.md that welcomes contributors and encourages them to contribute while insisting on higher standards, such as needing to write automated tests with every contribution. Make your source code repo discoverable. Your source code README, and your product or tool should have a visible link to your single CONTRIBUTING.md. Include a simple to follow "Getting Started" checklist in CONTRIBUTING.md that enables any developer at the company to make a trivial change in the application and submit a pull request. Ensure that your project has an automated test suite that runs in CI, is trivial to run locally, has few to no dependencies, and has enough coverage to give confidence to any new contributor that they did not break key functionality. Evolve every project to a state where a minimum viable version of it can run locally without the need to ask for permissions, certificates, or keys, install or get access to unnecessary dependencies, removing those barriers from the new contributor path. Describe h ## Mintlify agent upgrade improves documentation workflows with file processing and multi-page updates DevFeed: [Mintlify agent upgrade improves documentation workflows with file processing and multi-page updates]() Original publisher: [Read original article]() Author: Ethan Palm Published: 2026-02-16T00:00:00Z Content type: opinion Language: en Sources: [Mintlify Blog]() Topics: [Documentation](), [pull-requests](), [Slack]() Tags: [agent](), [article](), [best-practices](), [contributions](), [documentation](), [faster](), [pull-requests](), [quality](), [slack]() ### AI overview Mintlify describes an upgrade to its agent that processes files and images, updates multiple documentation pages, and addresses pull request feedback. The article reports that these capabilities help more employees contribute documentation and reduce the backlog of smaller documentation tasks. ### Source excerpt The improved agent means better contributions from my team and fewer docs tasks stuck in the backlog. ## How Our Community Shipped 66 Git Improvements In Under 2 Months DevFeed: [How Our Community Shipped 66 Git Improvements In Under 2 Months]() Original publisher: [Read original article]() Author: Katie Geer, Esther Trapadoux, Cole Miller Published: 2026-02-05T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [Git](), [Pull Request](), [ssh](), [Windows Subsystem for Linux]() Tags: [bug-fixes](), [community](), [contributions](), [contributors](), [git](), [improvements](), [ssh](), [wsl]() ### AI overview Zed describes an eight-week community challenge that improved its Git experience through contributor pairing, project planning, and demos. The program shipped 66 contributions, including five major features, 28 bug fixes, and 33 other improvements. The article highlights file Git history and a directory-based tree view as examples. ### Source excerpt A celebration of the Zed community's eight-week sprint to make Git in Zed better than ever. ## Who Contributed to PostgreSQL Development in 2025? DevFeed: [Who Contributed to PostgreSQL Development in 2025?]() Original publisher: [Read original article]() Author: Robert Haas (noreply@blogger.com) Published: 2026-01-19T15:29:00Z Content type: article Language: en Sources: [Robert Haas]() Topics: [PostgreSQL](), [Development](), [Code](), [Statistics]() Tags: [2025](), [blog](), [blog-post](), [code](), [contributed](), [contributions](), [development](), [postgresql](), [statistics]() ### AI overview An annual analysis of PostgreSQL code contributions in 2025 counts 266 principal authors and reports the concentration of new lines of code and commits among contributors. The author notes that the methodology has significant limitations and does not capture all important work. ### Source excerpt Here is another annual blog post breaking down code contributions to PostgreSQL itself (not ecosystem projects) by principal author. I have mentioned every year that this methodology has many limitations and fails to capture a lot of important work, and I reiterate that this year as usual. Nonetheless, many people seem to find these statistics helpful, so here they are. Read more " ## postmarketOS launches a contributor compensation programme funded by donations DevFeed: [postmarketOS launches a contributor compensation programme funded by donations]() Original publisher: [Read original article]() Published: 2025-12-19T00:00:00Z Content type: news Language: en Sources: [postmarketOS Blog]() Topics: [Development](), [maintenance](), [Documentation](), [Support](), [Tool](), [Repositories]() Tags: [contributions](), [contributors](), [development](), [documentation](), [financial](), [funding](), [kernel](), [metrics](), [postmarketos](), [processes](), [repositories](), [support](), [upgrades](), [work]() ### AI overview postmarketOS announces a Contributor Support Programme that offers financial compensation to contributors with high time commitments. The programme aims to support essential maintenance, support, and administrative work, while distributing funds using equal hourly compensation and logged work. ### Source excerpt We are excited to announce the Contributor Support Programme. This programme offers postmarketOS contributors with a high time-commitment the option to receive financial compensation for the work they do. It is designed to achieve the following goals: Address some of the sustainability challenges facing postmarketOS development. While we can oftentimes fund feature development through donations (e.g. wireplumber and callaudiod) or grants, other work like essential maintenance, support, and administrative tasks remains difficult to get funded with our current approaches. Some people have already been working on these topics full-time or part-time with no compensation. Ensure fairness and equality among participants and their contributions. Everybody is entitled to the same hourly compensation, regardless of location, kind of tasks, or any other variables. Fulfill our commitment to supporters who have donated specifically to compensate contributors, as stated on our Open Collective page. Establish metrics that strengthen future funding applications by demonstrating our current resource investment, and our ability to distribute funds fairly and efficiently. High level overview Every quarter, eligible contributors can opt in for the programme. The total amount of funds available is taken from excess donation income, while making sure that other budgeted items are not affected. Then, every month, contributors invoice proportionally to the hours they work, and report on the tasks that they spend time based on the logged hours. If you want to read more details about criteria, processes, and reasons, you can check the documentation. We see this as another small step towards improving the project and fulfilling the long-term goals! Monthly report November 2025 And as we started working on this programme in November, we are now able to provide our first report! During this last month: Stefan spent a lot of time looking at pmbootstrap, the tool we use for development. He opene ## Python 3.14.1 is now available! DevFeed: [Python 3.14.1 is now available!]() Original publisher: [Read original article]() Author: Hugo van Kemenade Published: 2025-12-02T00:00:00Z Content type: release Language: en Sources: [Python Insider]() Topics: [Python 3.14](), [releases](), [Development](), [Documentation]() Tags: [bugfixes](), [build](), [community](), [contributions](), [development](), [documentation](), [maintenance](), [python](), [python-3-14](), [release](), [releases]() ### AI overview Python 3.14.1 is the first maintenance release in the Python 3.14 series. It includes around 558 bug fixes, build improvements, and documentation changes since Python 3.14.0. ### Source excerpt !Two snakes enjoying a pie with 3.14 on the top and π crimping This is first maintenance release of Python 3.14 Python 3.14.1 is the first maintenance release... ## Hacktoberfest 2025 Comes to a Close DevFeed: [Hacktoberfest 2025 Comes to a Close]() Original publisher: [Read original article]() Author: Bedabrata Bagchi Published: 2025-11-21T15:45:11Z Content type: article Language: en Sources: [DigitalOcean]() Topics: [Hacktoberfest](), [Open Source](), [Maintainers]() Tags: [2025](), [community](), [contributions](), [contributors](), [developers](), [hacktoberfest](), [maintainers](), [open-source]() ### AI overview A retrospective on Hacktoberfest 2025 describes participation by developers, maintainers, and first-time contributors, highlights community growth and collaboration, and reports that the pull request requirement increased from four to six. ### Source excerpt October rolled around again, and with it came Hacktoberfest for its 12th year where contributors and open-source communities across the globe came together to build, contribute, and make tech more accessible for everyone. This year saw--as it does every year--developers, maintainers, and first-time contributors working side by side, creating solutions that matter to open source. A huge thank you to everyone who participated and made this Hacktoberfest special. We saw a lot of new faces join the celebration this year, and it's exciting to see the community grow! What really stood out this year? The genuine enthusiasm. People were here to contribute, collaborate, and make a tangible impact on open source projects. That's what Hacktoberfest is all about: getting more people involved in open source and working together to improve the software that powers our world. It's fulfilling to see how Hacktoberfest continues to inspire developers and successfully achieves what we set out to do. Here's what Mike Swift, Co-founder and CEO of MLH has to say about Hacktoberfest this year: "What I enjoyed most about this year's Hacktoberfest was seeing next-gen developers step into open source with genuine curiosity and realize they could make meaningful contributions. They approached issues, learned from maintainers, and connected those experiences to the AI tools shaping their work. Being part of moments like that is incredibly rewarding and exactly why the MLH community exists." A change for Hacktoberfest This year we increased the number of PRs from 4 to 6. As the program has matured and participants have access to better onboarding resources, we increased the requirement to encourage deeper project engagement and more substantial contributions. The additional PRs allow participants to move beyond initial contributions and tackle more complex issues, leading to higher-quality work and more meaningful impact on the projects they contribute to. This change was embraced by all contribu ## How to Query GitHub for User Contributions in a Specific Timeframe DevFeed: [How to Query GitHub for User Contributions in a Specific Timeframe]() Original publisher: [Read original article]() Author: Chris Hager Published: 2025-10-10T00:00:00Z Content type: tutorial Language: en Sources: [Chris Hager]() Topics: [GitHub](), [GraphQL](), [GitHub API]() Tags: [api](), [contributions](), [github](), [graphql](), [how-to](), [query](), [repositories](), [timeframe](), [tracking]() ### AI overview A tutorial showing how to use the GitHub GraphQL API to list public repositories a user contributed to during a specified timeframe, with an optional modification to include commit counts and format the output. ### Source excerpt I needed needed to find all public GitHub repositories a user has contributed to within a specific timeframe, and wanted to share - and record for myself - the API query I learned. This can be a useful for generating reports, tracking progress, analyzing activity over a certain period, and more. Use the GitHub GraphQL API We leverage the GitHub GraphQL API to get the list of public repositories a user contributed to within a specific timeframe, using the contributionsCollection field to specify a time range and retrieve contributions made by a user during that period. ## Hacktoberfest 2025: How to Participate DevFeed: [Hacktoberfest 2025: How to Participate]() Original publisher: [Read original article]() Author: Haimantika Mitra Published: 2025-09-29T07:06:22Z Content type: tutorial Language: en Sources: [DigitalOcean]() Topics: [Hacktoberfest](), [Open Source](), [pull-requests](), [GitHub](), [GitLab](), [Maintainers]() Tags: [also](), [community](), [contribute](), [contributions](), [github](), [gitlab](), [hacktoberfest](), [maintainers](), [open-source]() ### AI overview A guide to participating in Hacktoberfest 2025, covering registration, contribution requirements, rewards, code contributions, and ways maintainers can prepare open-source projects. ### Source excerpt Hacktoberfest 2025: How to Participate Hacktoberfest registrations are live, and we're just a few days away from kicking off the month-long celebration of open source. Every October, developers from all over the world come together to contribute their skills, big and small, to open-source projects. Code is the most common way people participate, but that's not the only way you can help. Open source thrives on more than just commits. It needs documentation, testing, design, writing, and so much more. Before we get into the how, let's cover the basics. First, the rules of Hacktoberfest: Register anytime before October 31. Contribute to projects on GitHub or GitLab that have the hacktoberfest topic. Submit at least 6 high-quality pull/merge requests between October 1 and October 31. These need to be accepted by project maintainers to count. Rewards: Everyone who signs up and gets at least one PR merged, gets a digital badge from Holopin (you can get up to 4 badges). If you're among the first 10,000 people to complete 6 merged PRs/MRs, you'll also get a limited edition Hactoberfest 2025 t-shirt. That's it! You're ready to dive in. Ways to contribute: 1. Code Contributions This is what the majority of Hacktoberfest contributions consist of. Most participants jump in by submitting code to projects they care about. Maintainers, many of whom run projects purely out of passion, appreciate thoughtful, quality code more than anything. Whether this is your 12th Hacktoberfest or your very first pull request, now's the time to fire up GitHub or GitLab and get started. Helpful resources: Introduction to GitHub and Open-Source Projects How to use Git 5 things for your first time contributing 2. Maintaining a project Hacktoberfest isn't only for contributors. It's for maintainers too. If you've got a project idea that could help the community, you can launch it now and take part as a maintainer. If you're already maintaining an open-source project, here's how to prepare it for Hackt ## Hired Through GitHub: Part 1 DevFeed: [Hired Through GitHub: Part 1]() Original publisher: [Read original article]() Author: Joseph Lyons, Katie Geer, Franciska Dethlefsen Published: 2025-09-16T00:00:00Z Content type: article Language: en Sources: [Zed Industries - Blog]() Topics: [GitHub](), [Open Source](), [Code quality](), [coding]() Tags: [code-quality](), [coding](), [community](), [contributed](), [contributions](), [developers](), [discord](), [github](), [interview](), [linux](), [macos](), [open-source](), [pycharm](), [series](), [technical](), [university](), [vs-code]() ### AI overview Zed Industries describes how open source contributors can become employees through sustained, high-quality GitHub contributions, community engagement, and collaboration with the team. The article begins a series profiling contributors who joined Zed's core team. ### Source excerpt Stories from the open source contributors who became core team members. ## Improving our Java SDK with Codex by OpenAI DevFeed: [Improving our Java SDK with Codex by OpenAI]() Original publisher: [Read original article]() Author: Ryan Cox Published: 2025-05-17T00:00:00Z Content type: article Language: en Sources: [Temporal Blog]() Topics: [codex](), [Java](), [SDKs](), [OpenAI](), [bug](), [Refactoring](), [test-coverage](), [Development]() Tags: [agentic](), [announcements](), [automate](), [bug](), [bug-fixes](), [code-coverage](), [codex](), [contributions](), [development](), [documentation](), [github](), [java](), [open-source](), [openai](), [refactoring](), [sdk]() ### AI overview Temporal engineers describe using OpenAI's Codex to improve the Java SDK by fixing bugs, implementing features, increasing code coverage, adding documentation, and performing refactoring. They also used parallel background tasks and AGENTS.md files to prepare repositories for agentic contributions. ### Source excerpt Learn all about how the Temporal engineers used OpenAI's Codex to improve our Java SDK, automate bug fixes, and prepare for agentic contributions, plus, how part of Codex itself runs on Temporal. ## Announcing QEMU Google Summer of Code 2025 internships DevFeed: [Announcing QEMU Google Summer of Code 2025 internships]() Original publisher: [Read original article]() Published: 2025-03-06T07:00:00Z Content type: article Language: en Sources: [QEMU]() Topics: [qemu](), [Open Source](), [Development]() Tags: [contributions](), [contributors](), [google-summer-of-code](), [gsoc](), [internships](), [open-source](), [qemu](), [remote]() ### AI overview QEMU announces its participation in Google Summer of Code 2025. The article explains the paid remote open-source internships, mentorship, application process, project selection, and application dates. ### Source excerpt QEMU is participating in Google Summer of Code again this year! Google Summer of Code is an open source internship program that offers paid remote work opportunities for contributing to open source. Internships run May through August, so if you have time and want to experience open source development, read on to find out how you can apply. ## Who Contributed to PostgreSQL Development in 2024? DevFeed: [Who Contributed to PostgreSQL Development in 2024?]() Original publisher: [Read original article]() Author: Robert Haas (noreply@blogger.com) Published: 2025-01-22T20:55:00Z Content type: article Language: en Sources: [Robert Haas]() Topics: [PostgreSQL](), [Development](), [data](), [Code]() Tags: [contributions](), [development](), [postgresql](), [repository]() ### AI overview The article presents 2024 contribution statistics for the PostgreSQL repository. It reports 229 principal commit authors, with 66% of new lines contributed by 18 people and 90% by 47 people, while noting that the analysis is not comprehensive and does not cover related projects. ### Source excerpt People continue to tell me on a semi-regular basis how much they appreciate these approximately annual posts, the first of which came out in April of 2017. I think this might be more because the project doesn't have enough official ways to recognize people than it is an endorsement of the particular thing that I've done here, the limitations of which I am always careful to mention. In particular, I do not intend this as a comprehensive picture of contributions to the project, or even to development activity; and I lack the data to fairly divide credit for a single commit between multiple individuals. Nevertheless, I am very grateful to all the people who have expressed appreciation for these posts, or told me about the value that they derived from them. Thank you so much. Read more " ## Ethereum Protocol Fellowship Cohort 4 Recap DevFeed: [Ethereum Protocol Fellowship Cohort 4 Recap]() Original publisher: [Read original article]() Author: EF Protocol Support Published: 2024-04-22T00:00:00Z Content type: article Language: en Sources: [Ethereum Foundation Blog]() Topics: [Ethereum](), [Development](), [Programming](), [Wiki](), [Protocol (disambiguation)](), [foss]() Tags: [contributions](), [devconnect](), [developers](), [development](), [ethereum](), [foss](), [knowledge-base](), [learning](), [open](), [programming](), [projects](), [recap](), [research-development](), [updates]() ### AI overview The Ethereum Protocol Fellowship completed its fourth cohort, with 35 stipend-supported participants and five retroactive stipends. Fellows worked with 27 core developer mentors, reported nearly 600 weekly updates, and proposed or contributed to 35 projects. The program also launched a 10-week study group and the EPF.wiki knowledge base to help aspiring core developers learn Ethereum protocol development. ### Source excerpt TL;DR: The EPF concluded the fourth cohort and is preparing for a fifth cohort. Applications will be open soon. In the meantime, explore the new EPF.wiki and sign up to get notified when they open. The Ethereum Protocol Fellowship recently completed its fourth successful cohort, culminating with EPF Day... ## Building a macOS screen saver in Kotlin DevFeed: [Building a macOS screen saver in Kotlin]() Original publisher: [Read original article]() Author: Márton Braun Published: 2024-03-05T12:00:00Z Content type: tutorial Language: en Sources: [zsmb.co]() Topics: [kotlin-multiplatform-libraries](), [Kotlin Multiplatform](), [macOS](), [multiplatform](), [interoperability](), [Code](), [GitHub]() Tags: [android](), [binaries](), [build](), [code](), [contributions](), [development](), [github](), [installation](), [interoperability](), [kotlin](), [kotlin-multiplatform](), [macos](), [marton-braun](), [multiplatform](), [zsmb](), [zsmb-co](), [zsmb13](), [zsmbco]() ### AI overview This tutorial documents the creation of a custom macOS screen saver built almost entirely in Kotlin with Kotlin Multiplatform. It covers customization options, release binaries, installation, and the challenges of working with macOS screen saver APIs and interoperability. ### Source excerpt This article documents how I created my own custom screen saver for macOS, built almost entirely in Kotlin, using the powers of Kotlin Multiplatform compiled to macOS. Join me for a tale of Kotlin success and macOS failures. ## How to become a Trusted Contributor, part 2 DevFeed: [How to become a Trusted Contributor, part 2]() Original publisher: [Read original article]() Published: 2024-01-28T00:00:00Z Content type: article Language: en Sources: [postmarketOS Blog]() Topics: [foss](), [code reviews](), [patches](), [Accessibility]() Tags: [accessibility](), [code-reviews](), [community](), [contributions](), [contributors](), [developer](), [email](), [foss](), [how-to](), [postmarketos](), [support]() ### AI overview This post explains how contributors to postmarketOS can qualify to become Trusted Contributors through sustained contributions beyond code, including accessibility improvements, community support, artwork, writing, and podcast editing. It also outlines the application process, which involves a confidential issue, team endorsements, and a list of contributions. ### Source excerpt After our How to become a Trusted Contributor blog post was received with great enthusiasm by the community (and already have two new TCs since, shout out to @travmurav and @f_), we thought that it would be a great idea to expand its scope. We know that people have been contributing to postmarketOS in many ways, not just via code reviews and submitting patches. So if you have been contributing to postmarketOS for the past six months or longer and don't fancy yourself a developer, there is now a path for you to become a Trusted Contributor too! Some examples of what types of contributions can qualify you as a Trusted Contributor include: making accessibility improvements supporting others in our chat rooms supporting others in our issue trackers creating artwork or other promotional materials writing blog posts for postmarketOS.org (the main and/or "edge" blogs) podcast / audio editing If you're curious how to get started with any of those things today, in hopes of applying to be a TC later, please do not hesitate to reach out to us in chat! If you find other tasks that we didn't think of, which would also have a good impact on the project or our community, feel free to reach out as well. Trusted Contributors enjoy street cred (public contributions to a large FOSS project can look good on a resume!) and their own @postmarketos.org email address. The process to apply is largely the same as what we detailed previously: file a new confidential issue in our application repo, find existing team members to endorse you, and list out your contributions and achievements to support your application. We also got a bit of behind-the-scenes audio for you in the podcast. That's it, thanks for reading this blog post! ## How to become a Trusted Contributor DevFeed: [How to become a Trusted Contributor]() Original publisher: [Read original article]() Published: 2023-12-03T00:00:00Z Content type: tutorial Language: en Sources: [postmarketOS Blog]() Topics: [Development](), [Code review](), [patches](), [Repositories](), [free software](), [engineering-culture]() Tags: [code-of-conduct](), [code-review](), [community](), [contributions](), [development](), [job](), [patches](), [postmarketos](), [repositories]() ### AI overview postmarketOS explains its revised process for becoming a Trusted Contributor, including the experience, knowledge, permissions, and responsibilities expected of contributors. The process formalizes code review, patch merging, issue management, and pathways toward deeper project involvement. ### Source excerpt During the past team meetings, we have reworked the process for becoming a Trusted Contributor (TC). To make it easier, more transparent, and to allow the postmarketOS community to continue to grow as we review and integrate an increasing amount of patches to improve stability, bring cool new features and support more and more devices and usecases. What is a Trusted Contributor? In postmarketOS, a Trusted Contributor is somebody who: ...has been supporting the project through positive contributions for a long time (could be own patches or just code review) ...has a good idea of how the project works, what our standards are regarding Code Of Conduct, for getting devices into various categories, rules for merging, etc. They have the responsibilities and permissions to: Merge patches into most branches Do code reviews (a bit more officially than a regular community member, they can hit the approve button.) Close/move issues Additional perks for TCs: A faster moving project! Our development workflow involves code review for most repositories (pmaports, etc.), so the more active TCs we have giving meaningful code reviews, the faster everyone's patches can get merged. Regular reviewers may prioritize each others patches as it makes sense. If desired, a possibility to become a Core Team member at some point. This is completely optional, as being a Core Team member means additional responsibilities (see below), and may as such not be desirable for every TC. We had people stepping down from the Core Team to becoming a TC in the past for being able to better focus on TC tasks / writing patches. Fame and glory of being a Trusted Contributor! In all seriousness, it is very useful to be able to point out just how much you have been contributing to free software projects in your free time, e.g. when applying for a job. Why we needed a new process The previous process was not documented anywhere. But it was more or less: be very active in the project for a long time until a Core T [Next page]()