Maintainers SHOULD close user issues that are left open without action for an uncomfortable period of time. (2.4.19)

Buried in the Collective Code Construction Contract is the clause above. I'm not sure what an uncomfortable period of time is, but early on it's probably not long, like a month or two.

Early on we tried to populate the issue trackers with what we thought were valid problems, but today we have something better. Problems being raised by our community of user-admins!

It's truly awesome to see this feedback loop in action. We've already got some good problems to solve, like being able to handle Markdown and LaTeX and working better with Debian packaging.

Learn more at

· · Web · 0 · 0 · 0
Sign in to participate in the conversation
Ecko /

Creating magic through evolution of the Fediverse. Running Ecko, a community-driven fork of Mastodon managed using the Collective Code Construction Contract (C4) by the Magic Stone Community. C4 is a protocol for asynchronous, non-blocking, distributed, problem-focused software development.