Documentation Documentation is a multiplier. •Use Docs-as-Code •Publishing is optional •Getting started •Platform-specific info •Advanced usage @lornajane@indieweb.social @lornajane.net (bsky)
Slide 8
The Tools we Build •Follow as many conventions as you can •Make the right thing the easy thing •Offer binaries or containerized tools if appropriate •Publish plugins/examples, or curate space for community work
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 9
DevEx for Contributors
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 10
Code of Conduct A code of conduct sets out expectations for all participants. GitHub prompts with a selection of CoC templates.
@lornajane@indieweb.social @lornajane.net (bsky)
Contributing file Everything a new user needs to contribute. •Philosophy •Mechanics •Codebase •Quality •Finishing
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 13
Philosophy Are patches actually welcome? •A public resource with a private change process •A corporate project with a permissive license but no external contributors •A community-driven project
@lornajane@indieweb.social @lornajane.net (bsky)
Finishing What is the “definition of done” in the project? •docs •tests •changelog •something else…?
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 16
Local development Local tools shorten feedback cycle and improve developer experience.
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 17
Pull request reviews Transferrable skill from other code projects. •Be clear and constructive •Be prepared to add one more commit •Be consistent •Be responsive
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 18
CI really matters Give instant feedback on the things you care about (and can automate). •coding standards •prose linting •tests •changelog
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 19
DevEx for Maintainers
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 20
Review checklist Things to check on every pull request, documented. •helps contributors too •serves as onboarding for new maintainers •reduces your cognitive load •makes more consistent reviews
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 21
Maintaining fIle •like a contributing file •but for maintainers •write down the release process •the docs publishing process •anything else that the maintainer does
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 22
Automation Invest time to save time! Automate tests, syntax checks, build processes. Also spell checks, coding standards, file naming, pull request requirements.
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 23
Notification management Do you get too many notifications, too few, or the wrong ones? •route notifications •adjust watching •use codeowners •email rules
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 24
Outreach Your project is more than the code. Build and enable the ecosystem: •write about the project •feature cool projects using your project •check stackoverflow questions •speak at a meetup
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 25
Developer Experience in Open Source
@lornajane@indieweb.social @lornajane.net (bsky)
Slide 26
Get in touch https://lornajane.net
@lornajane@indieweb.social @lornajane.net (bsky)