The Challenges of Keeping Bees

Editor's Notes

• #3: Not really. But let me tell you what I mean.Photo credit, roberrific, cc-nc, http://www.flickr.com/photos/roberrific/6921510878/
• #4: There’s this cool whitepaper from James Dixon at Pentaho. James says…Non-commercial open source projects are like wild bee hivesProject centered around a few queen bees, bees come and goAnyone is free to come along and take the honey, but no formal go to market functionOutput depends on the number of bees, health of the hive, etc.Queen bees are like the core engineering team. The other bees are community members. The honey and honeycomb is the software. The hive is the community.Open source has community but only produces raw material, not whole product. Most customers don’t want to collect their own honey. They want the whole product, not a raw material.Photo credit: Bee hive, by DB Duo Photography, cc-by-sa 2.0: http://www.flickr.com/photos/drb62/2144873098/Source: “The Bees and the Trees: The Beekeeper Model of Commercial Open Source Software”, by James Dixon, CTO, Pentaho
• #5: Source: “The Bees and the Trees: The Beekeeper Model of Commercial Open Source Software”, by James Dixon, CTO, PentahoProprietary software is like a maple syrup factoryCompletely focused on generating product, taking that product to the marketTrees aren’t actively involved in making syrupNo one from the outside involved, including customers Proprietary software produces a whole product but has no community.Both produce a sticky, sugary substance, but with a different process and outputs.Photo credit: Maple Grove Farms of Vermont, by J. Stephen Conn, cc-by-nc 2.0: http://www.flickr.com/photos/jstephenconn/2779332097/
• #7: Photo credit: Bee hives by Eilidh B, cc-by-nd 2.0: http://www.flickr.com/photos/29647084@N06/5002498868/
• #8: Source: “The Bees and the Trees: The Beekeeper Model of Commercial Open Source Software”, by James Dixon, CTO, PentahoBeekeeper creates a rich environmentOutputs sold, profits grow the bee farmSome roles focus on the bees, some on the productMutually beneficial partnership between beekeeper and beesGrowth of the farm depends on how much product the can be sold to customers.The honey in the jar is the same honey as the honey in the hive, but customers will only pay for it when it comes in a jar.Each individual bee makes a small contribution and it takes a lot of bees for a successful outcome.
• #9: Source: “The Bees and the Trees: The Beekeeper Model of Commercial Open Source Software”, by James Dixon, CTO, PentahoEngineers have routine and direct interactions with the community.Community has a mutually-beneficial relationship with the open source company.Engineering and product management are involved in both the syrup and the beekeeper model—those roles are not significantly different.The commercial open source model includes all of the components of the wild hive AND all of the components of the maple syrup factory. Nothing is missing.
• #10: Photo credit: Jordan Fischer, cc by 2.0, http://www.flickr.com/photos/jordanfischer/2341263192/
• #11: Let’s look at the state of the Alfresco bee hive…Photo credit: Brian, by-nc-sa, http://www.flickr.com/photos/ncreedplayer/3763639071/
• #12: Many new faces on the senior management team.Many are new to open source, so we’re educating them.Ultimately, a strong go-to-market engine is absolutely critical because it brings profits that can be invested in the community.
• #13: Community members are asking if the new management team means a change for the community.Everyone take a deep breath.Ouropen source model has brought us incredibly far and it will continue to do so. Here are a few reasons why I think that is true…
• #14: Profits from the commercial side allow us to invest in the communityCustomer is an organization, a person is a community memberGo-to-market is fundamentally separate from community buildingLet’s take a super-successful go to market engine, give them the selling points of a high quality product produced with a superior process and let great things happen.
• #15: Openness continues to be an extremely important value for us and our customersIf you are on-premise, the open platform is critical. Our customers are telling us that is still an important reason they choose Alfresco.If you are in the cloud, you want to be able to build content-centric applications on top of that repository, so an open API is critical.Openness is still an important value to the company.
• #16: We still want a freely-available Community Edition to be a quality productCore values haven’t changed from the time of the blog postBut our company has. So we need to update the differentiation guidelines with that context.Back then we had one product. Now we have several. So the company has changed but our values haven’t.
• #17: The hive is diverse. Let’s zoom in a bit
• #18: The Alfresco Honey Farm is huge. Our community is truly global
• #19: This year’s community members who have distinguished themselves with their level of time and energy given to the community.I am sorry that I always leave deserving people off of this list—there are so many dedicated individuals around the world. Please let me know when you see someone deserving.I want to highlight a few of these folks, so you can put a face to their name.Also pay attention to the diversity of skills, roles, and motivations of the following individuals…
• #21: > 270 community-based translators at last count
• #22: Very active in developing modules listed at Alfresco Addons (http://addons.alfresco.com)
• #23: Not technical. But still loves our community. Applies her passion and organizational skills to running meetups.
• #24: So many more Alfresco engineers I could mention here if I had the room
• #25: They do it because they love the community.Beyond that, though, everyone has their own motivation.Some are establishing credibility. Some are looking for productivity gains. Some are marketing themselves or their company.We must understand all of those motivations and set up an environment that addresses those needs
• #27: Could do better on making the learning curve easier. Tactically, I have written a CMIS book, revised the ecmarchitect.com tutorials and have added an alfresco-api-examples project on github. Need more for Share customizations, though.As a community, we already do a great job of welcoming newcomers (but we need to on-ramp them better)Add-Ons does a lot for making contributions visible. We’ve also resurrected the contributions wiki page. But we could improve a lot on things like how Jiras from first-time creators are triaged. Mozilla says that is the #1 determiner of whether or not a contributor will stick around.
• #28: Peaks had to do with some internal code line reorganizations and other resource intensive tasks.Everyone wants those peaks to go away.We are working to get Community Edition out more frequently.
• #29: How do you know when your community is happy and healthy?
• #30: We watch most or all of these metrics.Each quarter we’ll pick a few and try to move them one way or another.But none taken alone will give you a complete picture of our community
• #31: Is there something always happening somewhere?Do people get an answer when they ask a question?Are we living up to our values of openness and transparency?
• #33: We’ve made progress over the last few years, but there is still more to do.We need to listen to the community, find out what it is they want to do, and then put systems and processes in place to enable that.
• #35: Have been experimenting with Google Hangouts on Air. People seem to like it.Live Office Hours: Community team just talking about what’s been going on. No set agenda. Community members join as panelists sometimes.Tech Talk Live: Specific technical agenda with a guest panelist.
• #36: I’ve heard many people say that it feels like there is always something going on but it is sometimes hard to find out what’s happening, whenA new landing page helps existing community members find out what’s going on, helps them track things like Jiras, forum threads, wiki editsAlso helps newcomers
• #37: Photo Credit: beekeepers, by bwohack, cc-by-sa, http://www.flickr.com/photos/wohack/3727252089/
• #38: Every bee makes a small contribution to the output of the hive. Together, something amazing happens.I cannot (and do not want to) compel you to participateMy goal is to make you want to participateAnd if there is a reason you cannot participate and I can help, please let me or someone on my team know
• #39: You are the bee. Be the bee. Let’s make something beautiful together!Photo credit: Bee, by blathlean, cc by 2.0, http://www.flickr.com/photos/blathlean/5424404555/