Status is not only creating a decentralized infrastructure that will one day create a new connection to the way we transact, trust and communicate; But also creating a truly decentralized autonomous organization with inclusion from not only our core team and community as stakeholders that will guide the project, but also the new-coming contributors to the codebase.
Recently it was brought to my attention that one of our cherished community contributors had dropped off the radar and I want to address that in a meaningful way, because I care so much about all of our community.
It doesn’t matter if your contribution was a line of code or a friendly gesture to another member it really does count in growing what we are doing and blurring the lines between ‘core team’ and ‘community’ is something I want to help us strive for. A strong community loves its contributors for not only the passion they have and the people they are but also the skillsets they are growing along the way and opening doors to new places to grow this ecosystem.
Today along with the help of my brilliant friend and colleague pedro i’m implementing a developer feedback mechanism for anytime that contributors make a pull-request in one of our repositories. At Status, taking actionable steps to continue making our organization a truly decentralized one is a responsibility I take very seriously, and I think this is a very important part of that process. I hope for this to address some key points.
Making sure new contributors to our codebase have a place for their important voice to be heard and steps to be taken
Keeping contributions easy and removing blockers to allow ‘beyond the bounty’ so-to-speak
Pushing into the foray of making Status as a DAO a reality
Hearing the voices that otherwise would go unspoken is unquestionably one of the most important parts of community. Connecting our community to help understand what we are building and that beyond bounties there is great opportunity found in taking the next steps.
Status-pro-bot already helps workflow a great deal, this will now ping contributors that take the deep dive into the rabbit hole that status is. Will help in getting some actionable insights of how we can help open your creativity and build status into the organization we want it to become. Community owned, driven and built.
On top of asking for insights, I will be working with Stef and our people operations on a possible
commit buddy system for those that are interested to help out our newcomers to the codebase. Will gather interest from this survey sent out and follow up here about the next steps with that. It’s a simple way to guarantee that anyone that touches our codebase knows they can go as far as they’d like.
There are no confines to a DAO.
This is the current survey as it stands - https://goo.gl/forms/3KwzFFdecdwHFPZX2 please feel free to fill it out if you happen to be a contributor that has some feedback you want to share. Many of these ideas / suggestions could be turned into bounties to help our contributors fulfill their own roadblocks with others.
Results from these surveys will be shared publicly in this thread for those that opt-in. Please feel free to share any ideas related to this, creating a more open-community on the developer front and social front is at the forefront of my mind each day.