Engagement with Jono Bacon

Hi! You probably have heard about our collaboration with Jono Bacon. This post is to keep you updated on the engagement and the work coming out of it.

In short - Jono is a stellar community builder, and he’ll be sharing his wisdom on how Status can better engage, collaborate with, and serve, the community of contributors around it.

So far, the engagement is in its ~4th week, and is primarily in the discovery & high-level goal setting phase. There are short weekly calls all together (Jono/Carl/Jarrad/Jonny/People Ops), and Jono has also been reaching out to various core contributors to find out more about Status and how things work.

Weekly meeting notes will be updated here if you want to follow along, and updates will be added to this thread from time to time. Shout if any questions, comments, or if you’re keen to get involved!

5 Likes

No meeting since the last, but plan is to check in again later this week.

What we’ve been working on - Jono has drawn up a doc with high level objectives.The idea is to discuss these tentative objectives with a view to fine tuning them eventually into a strategy (i.e. they’re not yet set in stone). Broadly:

Target personas are devs building Dapps with Embark, and a wider tech audience.

High-level proposed focus areas are:

  1. Optimise the Embark developer experience
  2. Optimise community communication channels
  3. Have a content, social, and events calendar (for dev awareness)
  4. Build dev community growth and participation
  5. Consolidate project branding.

Shout if you want to know more, or if you have any questions. Cheers, c

1 Like

What’s the latest on this? I’ve been following Jono for some time and am a big fan of his work. Would love to know more!

1 Like

Hey @alexcg1! Not much to report - we’ve had a couple of weeks’ hiatus due to availability. We’re back on for a call this week though (today in fact!)

The last call (Oct 10th) was mainly about:

  • Agreeing on Discuss (our implementation of Discourse) as the centre of comms with the community - good for Q&A, async collab, searchability, international accessibility
  • Agreeing on Discord as the the hangout spot for synchronous chat and community meetings. Talked about making community meetings chat based as it’s been difficult to schedule synchronous voice hangouts (chat meetings = there’s a log for people to easily catch up on)
    *** Side note - full marks for anyone that can talk about Discord, Discuss, & Discourse without confusing the terms :sweat_smile:*
  • Using Discord instead of Status could be viewed as a weird choice - we should have a good reason for doing it and understand the trade-offs. Eventual aim will be to migrate back to Status > could lose some of the community when migrating back
  • To track or not to track developers through the onramp so that we can get feedback to help build a more smooth onboarding? Privacy concerns about doing this > led to the Community Governance call this week on Fathom as a good compromise.
1 Like

Nice!

OMG, agree so much on that.

Is this bc Status is still in development and not yet mature enough? Or because it’s a different kind of platform (messaging vs deeper discussion ala Discourse)? Having dealt with user groups on messaging apps like WeChat and Telegram before, I find Discourse a lot better for async comms and deeper discussion.

1 Like

Hey @alexcg1! Bit of both - Status desktop still misses some of the features we found were useful for engagement (e.g. sharing pics, emoji reactions) and also we were looking for a tool that allowed more for collaboration over pure instant messaging (e.g. with @ mentions, knowing if someone is online or not, etc.)

Latest catch up with Jono was yesterday - we talked project management. Jono is going to put together a list of granular action items as next steps, we’re (Status) going to finding owners for each of the tasks and figure out timeframes based on how best it fits around existing commitments. The work will probably be tracked in Wrike (our existing choice of PM tool).

Last call was 31 Oct and we looked through a tentative task list and threw around some ideas on who would be the right person to be accountable each task. I’ll ping each person individually and see if they’re keen to get involved and have bandwidth. As well as an owner, each tasks will have additional people involved and /or notified.

As well as finding owners for each task, we also need to suggest when we think they’ll be reasonable to complete.