Explanation/promotion of contributor/maintainer opportunities

[rfay]

There are so many opportunities for contributors at many levels in DDEV. We need to make it clear what they are.

DDEV is a mix of many different technologies, including Go, Linux, Bash, Docker, PHP, Python, and many others, and has an extensive automated testing and CI system that must be maintained. In addition, the DDEV Add-on ecosystem uses a variety of technologies including bash and PHP. We need maintainers for all of these, and mentorship is available for those who want to learn. Paid work is available for those who want to commit to work beyond the basics.

Bing suggests these strategies:
I'm glad you're interested in DDEV and want to spread the word about it. Here are some ideas on how to explain the opportunities available to potential contributors and maintainers:

• Highlight the benefits of contributing to DDEV. You can mention how DDEV is an open-source local web development environment that supports a variety of technologies and frameworks, such as Golang, Docker, Linux, Bash, PHP, Python and more. You can also mention how DDEV offers mentorship for those who want to learn something new, such as Golang, and how contributors can get paid for their work if they wish.
• Make it easy for newcomers to get started with DDEV. You can provide clear and detailed documentation on how to install, configure and use DDEV, as well as how to report issues, submit pull requests and follow the code of conduct. You can also label beginner-friendly issues appropriately, such as good first bug, easy, low hanging fruit, etc., and provide guidance and feedback for new contributors²¹.
• Showcase the existing community and culture of DDEV. You can share stories and testimonials from current contributors and maintainers, and highlight their achievements and challenges. You can also invite potential contributors to join your communication channels, such as Discord, Slack, Twitter, etc., where they can interact with other members of the DDEV community, ask questions, share ideas and learn from each other⁴³.
• Promote your project through various channels. You can use platforms such as GitHub, Dev.to, Hashnode, Aviyel, Opensource.com, etc., to write blog posts about DDEV, its features, updates, use cases, tutorials, etc. You can also use platforms such as Twitter, podcasts or Twitter Spaces to talk about your project, its vision, goals and challenges. You can also participate in conferences or events where you can showcase your project and attract new contributors³⁴.

I hope these ideas help you explain the opportunities available to potential contributors and maintainers of DDEV. Good luck with your project! 😊

Source: Conversation with Bing, 5/1/2023
(1) How to attract new contributors to your open source project - FreeCodecamp. https://www.freecodecamp.org/news/how-to-attract-new-contributors-to-your-open-source-project-46f8b791d787/.
(2) 10 tips for onboarding open source contributors. https://opensource.com/article/19/12/open-source-contributors.
(3) How to attract new contributors to your open source project. https://medium.com/free-code-camp/how-to-attract-new-contributors-to-your-open-source-project-46f8b791d787.
(4) Attract contributors to your open source project with authenticity. https://opensource.com/article/22/6/attract-contributors-open-source-project.
(5) 7 strategies for success when contributing to open source. https://opensource.com/article/22/1/open-source-contributions-career.

[mattstein]

This is exactly what I took a stab at with the Support DDEV page, where those calls to action should be resoundingly clear. And showcasing supporters on the homepage. The Get Started page is my best attempt to reduce setup friction and make it easy for someone to try DDEV.

So I’m not sure how to make this actionable or why it would start with this front-end project.

Two prerequisites I’d like to see:

1. A clear, honest description of what DDEV is and who it’s for. It should probably include what it’s not. It now supports Python and Node.js, for example, but is that support as thorough and comprehensive as for PHP? (And do all the options and documentation support those audiences equally?) Starting here would help shape further efforts to ask people to contribute.
2. Strategically optimizing messaging. On my list right now, for example, is to improve ddev.com, the documentation, and ddev/ddev’s project URL and readme. These all make different audience assumptions and point to competing explanations of how to contribute. We should be channeling people to our best writing and not saying the same thing a little differently in several places. It doesn’t matter how well something’s described if it’s not organized for the right person to find it at the most opportune time.

[rfay]

"Support DDEV" is awesome, but it's aimed at the general community/contribution angle - which is fundamental.

But it doesn't say "We want maintainers who can step in over the long term to take responsibility for parts of the project and who can also be paid for their effort". I want to figure out how to communicate that clearly, as it's a fundamental part of achieving long-term sustainability for the project.

The reason I open the issue here is to think about how to explain that on ddev.com

Thanks for having number 2 on your list, it's a great initiative of course.

I probably don't agree that the (valid) items you list as prerequisites are actually prerequisites for this initiative.

[mattstein]

"Support DDEV" is awesome, but it's aimed at the general community/contribution angle

I may have missed the mark, but it should be the canonical starting point for anyone wanting to get involved beyond using DDEV. Whatever this long-term maintainer solicitation should be, it should be referenced from that page at least.

I probably don't agree that the (valid) items you list as prerequisites are actually prerequisites for this initiative.

We can disagree, then. From my perspective as a potential contributor or maintainer, you’re inviting me to get on the bus without telling me where it’s going.

[rfay]

Absolutely agree that maintainership opportunities would be at least mentioned on the "support ddev" page, and maybe that's just where the CTA belongs.

[rfay]

I do hope you understand I'm not asking you to do this. Just starting the conversation to do it, with your invaluable input.

[rfay]

Add a banner advertising maintainer opportunities.