Duck Alignment Academy

Considering the wishes of upstream projects

Distributions should be opinionated. If you have a sound reason for ignoring upstream’s wishes, do it. But understand you may get no support.

Posts

You’re obliged to listen to the comments in good faith; you’re not obliged to be convinced by them.

Posts

If you’re considering adopting a “real name only” policy for your project, think about what problem you’re actually trying to solve.

Posts

Valuable meetings increase the work that gets done by providing coordination and accountability. Keep the valuable meetings. Cancel the rest.

Posts

Tasks that are low-impact and apt to be forgotten if not done on a regular cadence probably belong on a calendar instead of the schedule.

Posts

Avoid burnout and maintain a culture that people want to be a part of by getting rid of hero work. It’s an investment in the long term.

Posts

When there’s no chatbot to record meeting notes, you have to do it yourself. This post shares tips for before, during, and after the meeting.

Posts

Growing an open source community requires individual connections. The mere act of existence is not enough to build a community.

Posts

You’ll need to continually refine processes as you go. That’s easier if you think beyond just what you need at the start.

Posts

Making a license change affects how people interact with your project. You need to treat license changes as if they were changes to your API.

Posts