As we just reached our third goal on Patreon, we are now able to hire Rémi Verschelde (Akien) as full-time project manager and representative! In this article, he gives some insights on what brought him to Godot, how he helped organize the teamwork and became the de facto project manager, as well as plans for the future.
Project Planning and Management Resources | TeamGantt
Explore free project management resources from TeamGantt, including practical guides, templates, tools, videos, podcasts, and construction resources.
Changes to our Contribution Policies – Godot Engine
Godot is growing fast, so here is how we are dealing with the huge increase in contributions.
Doce Fernandes • Unicorn Developer, Designer & DJ
I'm Doce Fernandes, a unicorn developer, designer, and DJ. I build tools with Rust & Svelte, maintain FOSS projects, work at Rail Europe, and spin DJ sets on weekends.
Why isn't Godot an ECS-based game engine? – Godot Engine
The topic of why Godot does not utilize ECS comes up often, so this article will explain the design decisions behind that, as well as shed some light on how Godot works.
RethinkDB, SageMath, Andreessen-Horowitz, Basecamp and Open Source Software
RethinkDB and sustainable business models Three weeks ago, I spent the evening of Sept 12, 2016 with Daniel Mewes, who is the lead enginee...
Sophie Alpert
Building things to help people.Engineering at Clay.Previously, eng leader for Notion, Humu, and React.
Open source game engine Godot will no longer accept AI-authored code contributions: 'We can't trust heavy users of AI to understand their code enough to fix it'
At risk of drowning in AI slop code, Godot is firming up its contribution requirements.
The mythical 10× programmer is just a good leader
sourcehut is a network of useful open source tools for software project maintainers and collaborators, including git repos, bug tracking, continuous integration, and mailing lists.
Build Products That Solve Real Problems — A Lightweight JTBD Framework for Product Teams
Drawing on her experiences building products at Lumosity, Oculus, and Facebook's New Product Experimentation group, Sunita Mohanty shares a lightweight "jobs-to-be-done" framework for early-stage product teams, along with templates and go-to-market tactics.
Contributions and the Latest Generation
Simon Phipps wrote a particularly interesting article on project governance in the “GITHUB generation.” The article is very good reading, and thought-provoking. In it, he articulates, …
reladraw/reladraw
Contribute to reladraw/reladraw development by creating an account on GitHub.
Barış Özdemirci - Full-Stack Developer
Full-stack developer based in Berlin. Specializing in TypeScript, React, Node.js, and React Native.
Building an Open Source Company: Interview with GitLab's CEO
Building an Open Source Company: Interview with GitLab's CEO
AI-native project management | Plane
Project management for teams and AI agents. Plan, track, and ship with Projects, Wiki, and AI. Available on cloud, self-hosted, and air-gapped.
Shepherding v3.1
For open source projects, it can be difficult to find balance between a number of factors: the free time of contributors, the desires of the communities using the project, the ability to on-ramp and mentor new contributors, and to provide necessary guidance and feedback. The Rust Project, and multiple sub-teams and working groups have found success in use of the RFC Process for making informed, high level decisions. However, the RFC process does not address the work necessary for exploratory projects before a decision is made, the work necessary to implement made decisions, or the work necessary to maintain and overhaul parts of the projects in the long run. To address these needs, I'd like to propose a general concept and approach called Shepherding, which aims to assist maintainers of these projects with this aspect of managing the project. By enumerating core goals and putting a name to concepts, but specifically NOT mandating every aspect of implementation, I hope that this technique can be applied across many teams inside and outside of the Rust Project. The "Shepherding v3.1" name comes from a blog post written by Niko Matsakis titled Shepherds 3.0, which also does an excellent job describing the motivations regarding these efforts. This post instead makes a few clarifications and additions to the 3.0 post, and aims to be a "reference manual" for the concept, defining terms and important goals, rather than discussing motivations. Discuss on Reddit Discuss on Twitter
