What have I been writing when I haven’t been writing here?
Stuff I wrote
Duck Alignment Academy
- Does your project say “no” enough? — Saying “no” well keeps your project is focused & maintainable. This may put some people off, but it helps your project stay healthy long-term.
- Handling bug reports for upstream projects — When a user files a report for a bug that’s actually in an upstream project, how should you handle it?
- Directing new contributors to areas of need — If you have a list of what your project needs & empower people to do them, you’ll find newcomers self-direct to the best contributions.
- Managing issue tracker labels — Labels are arbitrary tags that either apply to an issue or not. But how you use them in your project can get very complicated.
Technically We Write
- Git for writing documentation — Technical writers can use Git to collaborate on documentation, such as for open source software projects. These are the basics.
- I contributed to several panel-type articles: