Ask HN: Marketing, DevRel and Evangelism working for Open-source
Speaking with my personal hat, not as Developer Evangelist at GitLab.<p>I&#x27;ve joined my first OSS project in 2009 (left in 2020), and I have to admit - communication can be challenging. There are many best practices, little are documented, and projects and companies differ in their workflows.<p>Here are few things I would encourage to do, or ensure to have in the very beginning:<p>- Be transparent in all your decisions. Discuss in the open, record meetings for the public, share the meeting notes with everyone. If the project reaches a level where everything is discussed behind closed doors, and the only community updates are marketing blog posts and AMA threads ... that&#x27;s a warning signal to lose your community.<p>- Provide a handbook or documentation for all workflows. How to contribute, which direction&#x2F;roadmap (in text form, not as a Git* issue board). Avoid so-called &quot;product conferences&quot; where you announce your roadmap. Instead, be open and have milestones to follow and discuss.<p>- Community members should _never_ be treated as &quot;you can submit a patch, but don&#x27;t bug me further&quot;. Assume positive intent, and get feedback from problem reports.<p>- Do not moderate or manage a community. Help seed the knowledge, and share trust with creating a governance structure (core team, community advisors, etc.). _Never_ silently remove granted permissions, losing trust. (that happened to me in 2020, I then made the decision to leave the OSS project Icinga after 11 years)<p>- Establish a sense of belonging, share praise and encourage to contribute. Handle code of conduct violations with care, ensuring everyone feels safe.<p>- Transfer knowledge in issue description, debug stories, reviews and encourage contributors to learn and follow. Coach and mentor fellow and future contributors. Take the time to thank everyone for their contributions.<p>- Evaluate roles. A founder or backend developer as community builder may work in the beginning. Plan to hire additional resources who can lead the conversation, and involve teams when necessary. Encourage to learn new technologies and stay in the loop.<p>- Document everything on the way, lessons learned, changes, what worked, what did not. Do retrospectives when announcements did not work the way you intended. Verify the defined actions.<p>- Find evangelists&#x2F;advocates in your company and community, give them visibility and push them in all collaborations. Ask friends who love social media, get the technical content writer champion, and give everyone a chance to learn and grow. Don&#x27;t expect to hire experts. Instead, focus on existing DevRel communities and exchange knowledge and experiences within the community.<p>- When you grow, do not hide as a leader. Be approachable with your team, and engage with your community. Coffee chats, meetups, etc. - follow the thought: Everyone can contribute.<p>There&#x27;s more to that, I&#x27;ve only shared a few quick thoughts now. Happy to chat more :)<p>If you want to dive into the topic even more - I&#x27;ve shared my 10 years in OSS community story and all things learned in a talk at the Open Source at Siemens event in 2021.<p>Slides: <a href="https:&#x2F;&#x2F;docs.google.com&#x2F;presentation&#x2F;d&#x2F;1HnciJEQ8dDiHMaq1APg5WXA4mvcYQd9fdtvHicf-JyU&#x2F;edit" rel="nofollow">https:&#x2F;&#x2F;docs.google.com&#x2F;presentation&#x2F;d&#x2F;1HnciJEQ8dDiHMaq1APg5...</a><p>Recording: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=yT63olXdS-I" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=yT63olXdS-I</a>