If you want to build a successful open source community, the best way is to not build in a walled garden.

You want to leverage a community of other open source projects, including those that might be adjacent or event competitive.

Real Quadrant provides complimentary digital engagement tools to Open Source projects to build out thriving communities.

To support these Open Source projects, we provide commerical open source or even closed source SaaS to provide education-based content for a fee in order to reach open source developers and end-users.

The key is being open to being truly open and ecosystem minded.

Many open source projects are actually walled gardens put up on GitHub.

The real way to succeed, however, is to drive engagement and involvement into a central "Town Square" where open source developers are able to gather.



We'll provide you the hosting of webinar, and act initially as a host and interviewer for your project.

You drive traffic to attend the awesome webinar, which we can record, and put on replay.

We will then ask those who register to continue the discussion and ask questions in the Community Forum.

There will be a dedicated section for Your Project (you can work with us on Taxonomy).

Why would you do this versus driving them to your own slack?

For two reasons:

1) The forum will collect SEO and support a virtual loop; attendees continue to engage around your project in the forum; new people who find the forum through SEO can then engage with the evergreen webinar.

We think being in a public square with multiple related projects, versus your own walled garden, is the best way to grow your community.

It feels counter-intuitive, but owning a category in a place that's a "hub" for projects (which is basically what Real Quadrant is), and then linking back out to your own silos of content is fine.

But....we really think if you keep content in a public square and link back to your project for the core work of downloading and contributing is the best approach to maximizing awareness and collaboration, and then narrowing back down into the actual code in your open source repository (such as GitHub or GitLab).

We think it's better if you create a hub in our space to encourage cross-linking across projects on our "neutral town square."

This blog post should ideally be original content but you can also host on your blog, just keep this blog post as canonical. (We don't support that, yet, so your post can be canonical)

However, you can always cross-link and even have a CTA from the blog we host back to your project's website.

Having a blog post which sets the stage for the webinar (why it's useful, code snippets you reference, a link out to the webinar registration and replay) before the webinar date gives you multiple ways to promote it and create linkable content.

I suggest that this "webinar announce" blog post ask for questions right in the forum. It gets you better prepared for the webinar to make it relevant, increasing searchability, and then advances your content.

We'll work to get it published and time promotion with other projects. They'll promote their interview while you promote your interview.

The interview will be based a little bit on what you share in the webinar, but is meant to cast a much wider net for the audience. We will provide a set of standard questions we use for the Podcast.

https://www.heavybit.com/library/blog/so-you-want-to-start-a-show-podcasting-best-practices/?mc_cid=895e7723ca&mc_eid=2cb96b191b

https://zencastr.com/pricing

We will then reach out to those open source projects and ask to do the same thing: host a webinar.

How do you come up with open source projects that compliment yours?

Real Quadrant will also create an evergreen social presence, where we will also mention your handle and a link to your content.

As we encourage more followers of Real Quadrant twitter, this will be another source of amplification acorss the ecosystem.

There are more things we can do with your community as we build out a repeatable flywheel:



I am pooling the infrastructure costs across a bunch of open source projects.

As the open source projects pools their communities together, we offer paid services for the commercial offerings. This may even include proprietary software vendors or SaaS.

Because I am asking the same of 10 different projects at the same time.

When your webinar is hosted with us, you will be exposed to the communities of the other projects.

Even if we're in the early stages, you still benefit by having a third-party interview and validate your market, and the link back to your site.

The concept of the "public square" will be more gradual in the beginning. We're building a central, neutral service for any open source project to teach and connect with developers.

As a "public square" we will be leveraging other communities and expose them to you.

It's less work (since the infrastructure is ready), lower costs (infrastructure is free), and more developers (by being the hub across all the other projects)

Because your own forum is captive: they are people who are already part of your community and will always return there because that's where the deeper engagement is

On the Real Quadrant forum, that's an outpost where you want activity which will bring people into your own forums.

This means you should hold AMA's, tutorials, introductory content out in the "public square," but then provide links back into your community for going "in depth."

Being active in a "public square" makes people excited to join the party behind your walled garden!



We have an Ambassador service which will allow you to reward developers for key actions with schwag.

Set up fulfillment in our centralied Schwag Store, allocate budget for an initial run (20 shirts), and we can come up with rewards and fulfillment.

Usually, we find the best things to reward are tutorials on YouTube (which are then made available on our website and can be embedded into blogs) and Blog posts.

The Ambassador service simplifies the process of enlisting and rewarding ambassadors.

You can either pay for someone to run the community or, if you have someone already with that role, we can give you admin access.