Embed Notice

@anildash I dispute that "discussing patches over email over a bad mailing list software" are better than having issue templates, kanban boards, automatic reviewers, and browser based contributions & previews...

The former is a recipe to get lost in noise

The later is a collaborative inbox with a definable workflow (like saying pull requests have to pass unit tests, instead of receiving a random patch in a mailing list you must test yourself, by hand)