3 ms·
As someone who has worked on a project both with and without community managers, having to do some of that myself when we didn't have one, I think it's a valuab
by notacoward 12y ago
As someone who has worked on a project both with and without community managers, having to do some of that myself when we didn't have one, I think it's a valuable role. Does it really make sense to take developers away from development to do any of the following?
* Organize meetups, hackathons, etc.
* Deliver presentations and/or get not-enthusiastic developers to do so.
* Initiate or sustain joint efforts with people on other projects, so they don't stagnate every time developers get distracted by other commitments.
* Get all that stuff from social media into the correct channels.
Most developers are not good at those things, and do not enjoy them. If your project is lucky enough to have some people who will do those things on their own time (or on company time without getting fired because they're not meeting code deadlines) then good for you. Many don't.
Sure, there's always tension between community and corporate needs. Again, who would you rather have managing that tension? Some introverted developer who only sees the world through the lens of the code as its already written, or somebody with better perspective and people skills?
Not every project needs a community manager. However, those that do will get one - either dedicated, or stolen from bits and pieces of other project members' time. Personally, I think it's a good thing when the project's technical leaders can shove all that other stuff onto somebody else.
- levosmetalo 12y ago> Sure, there's always tension between community and corporate needs. Again, who would you rather have managing that tension? Some introverted developer who only sees the world through the lens of the code as its already written, or somebody with better perspective and people skills? And here we go again, someone calling all developers introverts. Could we please stop that nonsense? There are certainly some introverts between developers, but not more than in any other high skill profession.
- Jgrubb 12y agoThat's not how I read it at all, and I'm somewhat introverted and definitely a developer. Nonsense is taking a comment like this so personally and blowing it way out of proportion.
- notacoward 12y agoI don't believe, nor did I imply, that all developers are introverts. However, presenting at conferences etc. takes a more than average degree of extroversion. IIRC, public speaking is one of the most common fears even among average people. A majority of developers certainly do fall below that threshold. Besides E vs. I, there's also an aspect of developers wanting to focus on their one favorite task and not context-switch to an entirely different one. For whatever reason, many projects do lack any developers with the skills or inclination to perform the community-manager role well.
- npsimons 12y agoExactly. Even among other technical groups, you will find those who would rather be "in the weeds" than having to deal with people problems (people suck).
- sbilstein 12y ago> A majority of developers do fall below that threshold Do you have statistics to back this up? Presentations at engineering conferences are almost always given by developers, often one's who have dual roles such as evangelists or sales engineers but sometimes by heads down individual contributors. I think this view in the tech industry that most developers are introverts or "lack the skills" to interact socially for business is myopic; perpetuating the stereotype might help for division of labor but I don't think notion is true at all. Engineers are overrepresented as CEOs in the United States (33%) and that is certainly a very public facing role.
- jarofgreen 12y agoIs this not completely missing the point of the blog post? I didn't read it as saying you should never have someone doing the things you list, but as being about against a certain job spec that get's labelled as "community manager". The test outlined in point A was a pretty good one.
- notacoward 12y agoBeing a community manager for a large project can require a full-time effort, so why shouldn't it be a full-time job with a corresponding title and description? Sure, that person will have be paid by someone, but that doesn't mean they'll always favor corporate interests or that they have no accountability. Where I work (Red Hat) we have many people who work both as developers and community managers on "upstream" projects. Sometimes they really do seem to be working at cross-purposes to each other or to their corresponding "downstream" (commercial/paid) projects, and that's OK because we as a company have made a commitment to give them that freedom. Those who are community managers are accountable to their own bosses for the results they achieve upstream. I don't see how any of this is problamatic, let alone some sort of fraud or farce as the rather whiny OP claims. These people do a valuable job that benefits the upstream project, and they get paid for it. End of story.
- exelius 12y agoIt's all well and good having a "pure" open source project; but at some point things become too big for someone to run in their spare time. Really, it should be about having proper project governance. If a project is big enough, there should be some sort of board of directors with a combination of technical people and some representation from the user community, which is where I see "community managers" fitting in. Like it or not, the companies these community managers often represent ARE users of the product, and often provide funding to support open source projects. IMO, funding open source projects should absolutely get you "special treatment" because it incentivizes companies to support open source projects financially (see OpenSSL for what happens when they don't.) Apache seems to run this model the best; but there are a lot of projects under their umbrella and some are run better than others. And it still depends heavily on the management skills of the project leads; but that seems to be what the development community wants.
- kiyoto 12y agoIn the end, it comes down to economics and how fungible goodwill/vanity/reputation/time/money are. As someone who works as both a maintainer and community manager of an open source project, I find it naive to think that an open source project can thrive completely free of corporate sponsorship/benevolent dictatorship. For example, I am hired by Treasure Data, Inc. to work full time on Fluentd (https://fluentd.org https://fluentd.org), the open source log collector. Treasure Data does use Fluentd, and Fluentd is a core piece of the technology that we offer to our customers. However, my boss explicitly tells me NOT to herd the community to serve our interest. Why? Because we know that we benefit a lot from the Fluentd community both for community contributions and awareness, and it servers our corporate interest to ensure that we stay on good terms with the community. At the end of the day, open source community members are intelligent. They can smell when companies start exploiting the community to serve their own interest, especially in a way that's not beneficial to the community. So, in that sense, my response to the OP is "let the community decide. if enough people hate on community managers, they will disappear." That being said, I can agree with the OP that "community manager" might not be the best nomenclature here. But that doesn't mean open source communities do not need the go-to person for ensuring the community's health and longevity. Whether that person is called a community manager, mailing list patrol, event coordinator, conflict resolver, or geek herder is somewhat irrelevant.