Opening open source events?

I sent a brief email around to the group I participated with at Open Source Day at GHC2013 to thank everyone and mention something along the lines of what’s mentioned in this post. I got a few emails back from people at Microsoft and Google asking more about what I had experienced and if I had any thoughts on how the day/similar events could be improved for the future. My reply went a little something like this:

Thanks for asking my opinion. I think that some of the things that might deter people in general from attending such events may happen to deter females more than males, which might lead to the low participation rates that you’ve noticed. In my case, some of the things that made the most impact were the following:

  • Having never been to an event like this or made an app before or whatever, I wasn’t sure that I would know enough to be productive. Even for someone else who did have experience in this area, she (at one point) wondered if she knew ‘enough’.. perhaps there are particular people who are more likely to feel less confident about their skills (first years, females) and are more likely to think that the event is not suitable for them
  • I wasn’t sure that anyone would help me to know enough to be productive, and that I wouldn’t get left behind (the emails which were being sent were a bit intimidating.. not for most people, I’m sure. but for someone for whom the contents of the email goes completely over their head, it can make you feel more of the feelings in the previous point)
  • There was a waitlist. I think that this is the biggest thing that contributed to my uncertainty of attending. The previous two points you can recognise are not necessarily true, and overcome to decide to sign up anyway. But once you start receiving emails about how the positions are full and there are people on the waitlist.. you end up wondering if you are more ‘appropriate’ for or ‘deserving’ of the position than the people on the waitlist. And this can make you second-guess the confidence you had to muster in order to overcome the first two points. I’m not sure how it is best to accomplish the functionality of a waiting list while keeping the pressure off the first-come registrants, but I would definitely argue that it’s necessary.

Perhaps one of the first steps that could be done to understand other people’s opinions would be, if you have their contact details, to ask the people who were registered for events but de-registered.. I mean, we can’t capture information from people who didn’t register, but there might be useful information in the people who registered but at some point decided that they wouldn’t go. And maybe it is just that they couldn’t make it, but perhaps other people found the waitlist put a bit of pressure on.

I had never particularly contemplated attending an event like this before, and so I don’t know which of the feelings that I have experienced are unique to this event. I will tell you though, some of the things that made me eventually attend the Open Source Day at GHC2013 were:

  • The way that it was in the schedule and what-not made it seem like it was the norm to attend, so I registered. In that way it seemed like it was welcoming to all participants.
  • The limit of places available gave me pressure to register quickly to secure my spot, so I did that and stopped thinking about it. I felt liable in that way, and if it were more like ‘whoever wants can come’ but there weren’t registrations, I probably would have felt less committed and would have found an excuse not to go.
  • I had been to a session the day before at GHC about ‘preparatory privilege’ and how schools sometimes mistake students with experience in computer science as the only students with aptitude for it. “Just because I haven’t done it before doesn’t mean I’m not good at it!” I said to myself to get over the ‘not sure I’d be appropriate’ feeling.
  • A lot of the sessions at GHC spoke of imposter syndrome, so I was more aware of what was going on when I was doubting myself, and was able to ignore it. Similarly I recognised that, at GHC, probably I was not the only one (or even close to being the only one) feeling concerned and so that helped me to feel stronger about attending.
  • In the end, only one person in our Android group of 8 had experience making an app! And we had all managed to feel confident to attend. For me, it was easier to feel confident about being welcomed and not left behind (skill-wise) because it was at GHC and I knew it would be a group of girls. Now, I won’t make any generalisations or gender stereotypes here because I am not trying to make any claims about female environments vs males, I just wanted to mention that for me, in my opinion, the significant reason that I felt more comfortable with my less-appropriate skill set was because I knew that I would be in a room of females.

As for the event itself, everything went well in my opinion. The first person I spoke to was in the same position as me experience-wise, which immediately made me feel better (I’m not sure what difference in terms of feeling welcoming that having a mentor that is experienced would have, vs having a friend who is as inexperienced as you! They are both comforting in different ways perhaps). On the Android team for our project, we didn’t have much experience but one of us had made two apps before and became the leader. It was perhaps frustrating before to have to bring us all up to a functional knowledge level while the other teams (smaller and more experienced) were wanting to discuss details that the team leaders had to agree on, but were so far from the point that we were up to. Anyway, she did a great job, and we all learnt a lot.

Although, I felt like the day was geared a bit too much towards producing output (which is a good goal, of course). For our group, we had worked very hard but didn’t have much to show because most of the gains in our group were less tangible.. I mean, I had learnt enough that I was able to go home and finish the content that we were working on, and when we had to present about what we had done, I felt that ‘we learnt a lot’ was an acceptable answer. But, all of the other OS groups were presenting what they had accomplished (in a tangible way) etc, and it became a bit pressuring for us to make it seem like we had done a lot not just learnt a lot.. perhaps our speaker recognised this and it sounded like we were pretending like we had done a bit more than we really had, to impress the rest of the room etc. So, maybe in the future there is a way to make the show-and-tell side of things less show-offy, somehow.. so that people who have just learnt a lot can feel proud and not embarrassed. (Maybe, taking a leaf out of the Harvey Mudd CS5 class‘ book that we heard about at GHC, there could be two different streams for those who had experience before and those who didn’t, so that intimidation and pressure/embarrassment didn’t feel so present in the room).

So, perhaps somewhere in this email of thoughts/experiences there are things that can be taken and developed into suggestions for events in the future. Happy to clarify anything that anything hasn’t quite come across clearly in email! Perhaps you have some more thoughts?


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

Blog at

%d bloggers like this: