Skip to content

Commit e9c07ae

Browse files
Revise sections on burnout and mental health care
Updated text for clarity and emphasis on self-care in open source maintenance.
1 parent 00f3f69 commit e9c07ae

File tree

1 file changed

+8
-4
lines changed

1 file changed

+8
-4
lines changed

_articles/preventing-burnout.md

Lines changed: 8 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,7 @@ Maintaining an open source project can be deeply rewarding, but it can also be e
1111
## Understanding Maintainer Burnout
1212

1313
Burnout in open source maintenance typically manifests as:
14+
1415
- Emotional exhaustion from constant demands and support requests
1516
- Cynicism or detachment from the project you once loved
1617
- Reduced effectiveness or productivity despite increased effort
@@ -22,6 +23,7 @@ Many maintainers delay addressing these symptoms until they reach a crisis point
2223
## Recognizing Early Warning Signs
2324

2425
Watch for these indicators before burnout becomes severe:
26+
2527
- Dreading opening your email or GitHub notifications
2628
- Spending nights or weekends on maintenance when you didn't plan to
2729
- Feeling irritable during interactions with contributors
@@ -31,7 +33,7 @@ Watch for these indicators before burnout becomes severe:
3133

3234
## Setting Sustainable Boundaries
3335

34-
Clear boundaries are essential for long-term maintenance:
36+
Clear boundaries are essential for long-term maintenance.
3537

3638
**Define your working hours**: Establish specific times when you respond to issues and PRs. Communicate these clearly in your README or CONTRIBUTING.md.
3739

@@ -45,7 +47,7 @@ Clear boundaries are essential for long-term maintenance:
4547

4648
## Delegating and Building a Team
4749

48-
You don't have to do everything alone:
50+
You don't have to do everything alone.
4951

5052
- **Identify potential maintainers**: Look for consistent, high-quality contributors who understand your project's vision
5153
- **Document your processes**: Write detailed guides on how you make decisions, merge criteria, and project direction
@@ -55,11 +57,11 @@ You don't have to do everything alone:
5557

5658
## Taking Care of Your Mental Health
5759

58-
Maintenance is a marathon, not a sprint:
60+
Maintenance is a marathon, not a sprint.
5961

6062
- **Practice saying no**: You can't accept every feature request. Declining requests is not rude; it's necessary.
6163
- **Celebrate wins**: Acknowledge releases, milestones, and community achievements
62-
- **Connect with other maintainers**: Shared experiences help. Join maintainer communities like the Maintainers Slack or open source forums
64+
- **Connect with other maintainers**: Shared experiences help. Join maintainer communities
6365
- **Seek professional support if needed**: If stress becomes overwhelming, talking to a therapist or counselor is valid and helpful
6466
- **Remember your "why"**: Periodically reflect on what made you start this project and what you want it to be
6567

@@ -73,3 +75,5 @@ Maintenance is a marathon, not a sprint:
7375
## Conclusion
7476

7577
Sustainable open source maintenance requires intentional boundary-setting, delegation, and self-care. By recognizing early warning signs and implementing preventative strategies, you can maintain your project and your wellbeing for years to come.
78+
79+
Remember: A burnt-out maintainer helps no one. Taking care of yourself is taking care of your project.

0 commit comments

Comments
 (0)