When we announced our full day of open-source at tretton37, we immediately got a lot of questions from people asking us all sorts of questions. A lot of the questions were about what projects we would be working on and how many people would be involved. However, even more questions were related to how we convinced the company to let us spend a full day doing free work, instead of billing clients.
The short version is that we did not have to convince the company at all. We already had the corporate structure in place to enable us to do something like this. The more interesting question really is; why are we able do things like this?
tretton37 was founded on the ethos of "Creating value by sharing knowledge". An important thing to understand is that for us this is just not a marketing strap-line. This is the ethos that defines who we are and it is what attracts people to join our family.
We have defined five core values that are important to us, as a company, to help us embrace that ethos.
- Craftsmanship as a lifestyle
- Embrace the family spirit
- What you see is what you get
- Challenge the world
- Have fun
I won't go into detail about each of the values, but if you are interested to learning more about them, you can find the information at our website
So who exactly do we share knowledge with? The answer is EVERYONE. We share knowledge inside the company by organizing weekly code nights, we share knowledge with the community by speaking at conferences, sponsoring user groups and other meetups, being crazy enough to create our own, nearly free, conference Leetspeak and we share knowledge with our clients.
Just last year we sponsored 16 user group meetups, spoke at 10 conferences, organized 50 (!) code nights, wrote 82 blog posts and organized the second incarnation of the Leetspeak conference. It just so happens that we created a nice little infographic about our past year.
So sharing knowledge is not something we do, but it's also who we are.
One thing that we love doing is getting the opportunity to all meetup and embrace our ethos and core values. There is not a single ninja at our company that wouldn't tell you this if you asked them. Because of this and because we are consultancy company, which means we spend a lot of our time spread out between our various clients, we needed to create a platform where we could quench the thirst of having everyone meetup and do cool things. That's where the Knowabunga Days came to see the day of lights.
What is a Knowabunga Day then? We define them in the following way
So what is a Knowabunga Day? It's the name of the days where we gets the opportunity to gather at our headquarters and further sharpen our swords, learning interesting things by experts and each other. The content and format of the days is created by the ninjas in the Knowledge Committee. The content could be just anything related to our community or our field of knowledge, but the day should be delivered with quality and not just be a day where we hang around at the office.
The thought behind these days goes back to our five core values; maybe most "Craftsmanship as a Lifestyle", "Embrace the Family Spirit" and "Have fun". We state that we focus intently on creating a great environment for gaining knowledge and building a company where we have fun. By doing the Knowabunga Days we try to further develop our own identity and culture as well as maintaining and develop our reputation at existing clients and new ones.
They're nothing more than allocated days where we meetup and try and do awesome things while staying true to our core values and our ethos of creating value by sharing knowledge!
Why an open-source Knowabunga Day?
I was also asked how and why we decide to spend the day working on open-source. The simple answer is that we all love open-source and many of us regularly contribute to projects and/or maintain them ourselves. The slightly longer answer is that back in November we had a company strategy day, where we all (once again) met up at our offices but this time to talk and plan about our strategy for the next couple of years.
We have a very flat corporate structure and we also embrace transparency. Truth be told, the company is (not is made up of - pay attention to the distinction) the people that work there. We are all a bunch of geeks with a huge passion for our profession and the software community. Everything around those individuals is there to help facilitate those individuals to get to work with the things that they are passionate about. We work hard, play hard and know when we should be on either side of the line that divides the two.
So because of this is very important that everybody helps define our strategy for the next couple of year, what we should focus on and what we would love to work more with. During the day, open-source emerged in all sorts of discussions and it became clear that everybody wanted us to actively participate in the open-source community. So that's one of the things we'll be doing, in various formats.
When it was time for our knowledge committee to plan for our next Knowabunga Day, choosing an open-source theme was the obvious things to do and there were cheers all around when the theme was announced!
Planning the day itself
Planning the day was, relatively speaking, pretty straight forward and can be summarized with the following check-list
- Define the purpose and goals of the day
- Have everyone sign-up, or decline, to participate during the day
- When we know how many that is able to attend we can start planning how to divide people up
- Ask everyone that will be attending what they'd like to work on (front-end, back-end etc.)
- Ask everyone that will attend if they have any projects they would like to recommend
- Add additional interesting projects to the list of suggested projects
- Select projects that suite the interests of the attending people
- Divide attendees into teams and assign them a project
- Encourage attendees to read up and explore the project a bit ahead of time
- Tell people to prepare their laptops for the environments they will be needing
- Have an awesome day
The key thing to take away from this is that planning is key. We would never have succeeded in producing 23 total (I've previously mentioned 16 but we had not counted both offices at that time) in a single day unless we had made preparations up front - we would have wasted too much time trying to decide what to do and with whom we'd like to work with.
For this particular Knowabunga Day we followed a simple agenda when it came to the projects
- Take it for a spin
- Take it apart
- Contribute to the project
We had allocated time for each of these activities to help people familiarize themselves with the project and become confident enough with them to start contributing back.
The rest is history...