For my regularly scheduled (once every year and a half) blog post, I wanted to announce that July 3rd is my last day at VMware, and I will be joining the CHAOSS project as their new Director of Data Science.
It was really hard to leave VMware after almost 5 years (including my time at Pivotal). The work was fun, and I worked with so many amazing people that I will miss dearly! But as many of you know, I have a deep passion for data, and in particular open source community metrics, so the opportunity to work full time on the CHAOSS project is the dream job that I just couldn’t turn down. I’ve been working in this space for 10+ years with the CHAOSS project, and before CHAOSS, I was working with Bitergia and a variety of open source tools that later evolved into the software that is now part of the CHAOSS project. I’ll be taking July off and then will be starting my role with CHAOSS in August. A big thank you to the Alfred P. Sloan Foundation for making this possible through the grant that is funding the Director of Data Science position and other CHAOSS project initiatives.
I will be continuing my work on the OpenUK Board and as co-chair for the CNCF Contributor Strategy Technical Advisory Group, which have kept me very busy in addition to my work at VMware and in my role on the CHAOSS Governing Board.
Over the past year and a half, I’ve done quite a few presentations on topics ranging from how companies can work in open source communities to open source health / metrics to leading in open source, which can be found on my Speaking page. The highlight was giving a keynote about growing your contributor base at KubeCon EU in front of an audience of 10,000+, which was amazing and terrifying at the same time!
In addition to my world tour of conference presentations, I was quoted in a Linux Foundation Diversity Report, won a few awards for my UK work in open source as part of the OpenUK Honours list in 2021 and 2023, and I’ve written a few blog posts since my last post here on my own blog:
- Dawn Foster on Being a Good Citizen in Kubernetes at KCD UK 2022
- What’s Not to Love about FOSDEM, CHAOSScon and State of Open Con?
- How to Build a Sustainable Open Source Project
On the personal side, Paul and I bought a new house in November, and we have become the people who sit in their back garden and talk about how adorable the squirrels and birds are. Since we live in an area near quite a bit of green space, we have regular visits from foxes and even spotted one badger on our backyard wildlife camera!
Since I don’t post here often, if you want to keep up with what I’ve been doing, I post occasionally on Mastodon and Instagram.
Managing communications can be easier when you have a single company blog with fewer authors. It can get very tricky when managing corporate communications for a company the size of Microsoft or Intel with many blogs and many people communicating with the outside world.
Many companies use their blogs as a way to make announcements and other official communications for the outside world. For your readers, it can be difficult to know whether a blog post is an official announcement or something less formal. In companies, like Microsoft, with bloggers spanning across many blogs, it can help to educate people to clearly state whether something is opinion or official statement. When I worked at Intel, my intel.com blog and this blog had disclaimers at the top of the sidebar making it clear that the posts were my opinions and not official statements. It can also help to educate bloggers about including clarification within the text of certain types of posts. For example, a short paragraph about why the team released the open source CMS app along with a note about how it wasn’t the best example of how to do a MVC-style web app on .NET might have diffused your issue. We get so wrapped up in our work that we don’t always take the time to think about how what we do will be perceived by people outside of the company, but it can help to give bloggers a little training with things to think about. Lightweight social media guidelines might also help in some situations.
I suspect that this is mainly an issue for larger companies or ones that tightly control communications. I’ve worked at several smaller companies where this issue never really came up at all. In other words, don’t sweat the communications issues unless you really think that it might be an issue at your company.
Summary: A few tips for managing communications