Create a plan for celebrating Maintainer Month (May)
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 7
- Forks
- 35
- PR merge metrics
- No merged PRs in 30d
Description
GitHub run a Maintainer Month in May, we have an option to contribute resources. This might include blog posts, podcast episodes, stories, and other resources.
This issue is to come up with a plan that we can follow to showcase the amazing work that Mautic's maintainers do, across code and low/no code. The content should start being worked on in April so that it's ready to go in May for Maintainers Month.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the issue text and turn its proposed blog posts, podcast episodes, stories, and other resources into an actionable plan. Done means the plan covers both code and low/no-code maintainers, defines work to begin in April, and is ready to support publication in May.
Written by the indexing model from the issue text.
Assessment
- Domain
- content
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100