Mike Gifford, CPWA

Consulting and training is the most common way that open source projects are funded. This also provides a double advantage of ensuring that the developer is listening to the end-user. Often technology is difficult to build and maintain. Having an expert on-hand to install, configure or train makes the process of adopting technology easier. One challenge of funding through consulting work is that the software risks serving the short-term needs of the user, rather than a longer-term perspective about their needs.

Nobody likes asking for help, but successful open source projects are able to do this. Part of this comes in terms of code, design and documentation, but also donations and grants. It has become much easier for individuals and organizations to make monthly contributions which can fund the development and maintenance of the project.

I'm always struck by how much design effort goes into highlighting the green efforts of dirty industries. See if the company looks like they are spending more time telling the world how good they are, vs ensuring that they are actually making the world a better place. Looking for certifications like B Corp or Science Based Targets initiative are solid, evidence-based approaches. Ultimately, corporations should be providing evidence of their environmental efforts, within the context of the broader work they do. Also, it is worthwhile to demonstrate humility, and be willing to learn from others. Humanity is still very much re-learning how to walk in balance with the ecosystem that we depend on.

There are frankly so many ways that projects can innovate and improve. Whether it is by identifying performance or accessibility improvements that can be made or simplifying the user interface. Many open source projects allow spaces for experimentation, beyond just forking the project. Look at neighboring projects too. There are likely some projects doing similar things, but perhaps with a different code base or target audience. What are they applying which might help the users? Where could the developer experience be improved?

It is important to not sing to the choir all of the time. People inside the community know why your project is important, but most folks in the tech industry likely haven't heard of it. Reaching out to conferences and events to speak helps raise your credibility, but also that of the project. You need to bring the enthusiasm that you have for the work that your open source community to people who have never heard of it. This will help enlarge the community over time.

Supporting the next generation of contributors is key for a project's viability. Making sure that there are people in the wings ready to take over should a maintainer "win the lottery", or just transition in their career. Bringing in new people also allows you to ensure that your documentation is clear. Talking about your work in blogs, podcasts and tutorials is another way to help grow your community and demonstrate your leadership.