Community News

Let the River Flow?

river Inside the world of Red Hat, and other open source-oriented companies, there is a recurring metaphor to try to help explain the relationship between the projects where our source software is created and the commercially available software we ship with support, training, and other value-adds.

The metaphor used is "upstream" and "downstream," where upstream code is the "source" project code and "downstream" is the refined product code. Thus, Fedora is the upstream to Red Hat Enterprise Linux's downstream, to pick one example.

But increasingly we have been noticing a certain problem with this metaphor: very few people outside Red Hat and companies in this sector of IT really understood what the whole "stream" metaphor meant. Worse, when we really looked at the upstream/downstream metaphor ourselves, we realized that it has a fairly big flaw on its own.

Read More »

On Difficult Conversations in Community

gluster Before I moved into community full time, I was a project manager working on a lot of different things. As a project manager, you tend to have a large portion of your day tied up in difficult conversations, and what I learned through is: always deliver bad news over the phone. Deliver over the phone, follow up in an email, but give people space to be able to react in person or as near to in person as you can, and have that hard conversation together.

Since I started this practice, video conferencing has gotten a ton better, and that 'near enough' is sometimes good enough! (I have other thoughts on what to do in days of amazingly bad connections, which is more common than you might think these days!)

Read More »

Introducing a New Repository of Open Source Knowledge

The Open Source and Standards team is focused on making open source succeed at every level: community management, development, event management… Every aspect of open source can be improved for any project.

With that mission in mind, a new section of our site is dedicated to hosting "evergreen" knowledge articles and links that will guide free and open source software project participants to better practices.

Read More »

Open Source Stats--But What Do the Numbers Mean?

rdo I recently sent a report to project management containing some numbers that purport to describe the status of the RDO project.

I got a long and thoughtful response from one of the managers—we'll call him Mark—and it seems worthwhile sharing some of his insights. To summarize, what he said was, don't bother collecting stats if they don't tell a story.

Read More »

Online Communities Meeting Face to Face

gluster One of my favorite things about working in online communities is that you can spend nearly all your time with someone online but have no idea what they look like. I went out to dinner with a friend that I've known for ages from the DevOps community, and he went up to order and put it on the tab I had open—and he couldn't remember what my real name was. He came back to the table and we had a good laugh about it—how we've known each other for some time, we're good friends, but there's some things that you just miss out on.

The face-to-face meetings are really important because you get to know why someone reacts a certain way to ideas that are proposed—in person. It's really hard to hug it out over video chat, even though you can indicate a lot in email, in chat, and mailing lists.

Read More »

Growing a Contributor Base: Speed Matters

racing bicyclist Others have written good general information about how to attract and retain contributors for your open source project. Here, I'm going to focus rather narrowly on one critical factor in growing your contributor base: speed. Since it's what I'm familiar with, I'm going to write with the maintainer in mind.

The moment a new contributor posts a PR or a draft patch, a timer starts. The longer maintainers take to respond to their submission, the lower the chance that person will ever contribute to the project again. While no one has done a specific study on this that I know of, my experience is that it drops by half in a couple of days and it gets very close to zero in only a few weeks. If you're running a young project and looking to attract lots of new contributors, there may be no higher priority than dealing with first-time contributions quickly. Minutes to hours is the target here.

Read More »

Community Managers Sit Everywhere. Should They?

fedora This week's community blogging prompt by Stormy Peters includes the question, “should community managers sit in marketing or engineering?” This is a very individualized decision and not an easy one at that.

A lot of companies support open source communities. The Fedora Project is supported by Red Hat. Red Hat’s support is huge and includes infrastructure, engineering and non-engineering contributions, budget for community driven activities and events and community coordination assistance.

Read More »

Encouraging New Contributors

gluster Open source projects survive off new contributions and new contributors, bringing new ideas and new focus to their work. A new project starts with one person or a few people putting code out for other people to use and contribute to, a successful project creates a pathway for contribution.

In Gluster, we've focused the past two years on making our infrastructure effective for contributing, and inviting more contributors into our infrastructure. Open source isn't just about opening up your code—it's about building a supporting infrastructure that invites people to contribute. For projects to be successful, the community needs to be able to participate in the governance, the documentation, the code, and even the hosting. Said another way, a healthy project can attract more diverse skillsets with more transparency.

Read More »

Onboarding New Contributors in the Fedora Project

fedora Fedora is a community with a lot of moving parts and has at least five different ways of thinking about new contributor onboarding. Unlike some single code-base communities where there is a focus around a repository or a bug tracker, Fedora is constantly working on lots of things and the linkages can be hard to see. Some of those activities are directly (in a creation sense) related to the amazing Linux distribution we produce.

These activities, like Release Engineering, must happen or no bits get shipped. Other activities are critical to the experience of Fedora, like Design. Without these activities we might as well not ship. Some activities, like a lot of the work done by Fedora Infrastructure, are critical to providing the tools and glue we need to get our work done.

Onboarding is much on the mind of communities of late, thanks to Stormy Peters' prompt on how community works at Go read it, as it inspired this post and will contain lots of great information in the roundup post later this week.

Read More »

Community is Messy

messy There is an adage in the wide world that goes something like this: "If you want to make God laugh, tell Him your plans."

A less faith-oriented version of that line of thought breaks down to "Life Happens." Which all means that no matter how well we prepare the structure and flow of our daily lives, chaos and random chance can always cast such plans aside and potentially damage all we have built, sometimes irreparably.

Communities are no less immune to this kind of ill fortune than any one person. Even with the best intentions, communities can become embroiled in conflict and strife that can burn like a brush fire through all of the great things you've accomplished.

Read More »