I’ve spent a lot of time over the past few weeks talking about why we have so few women in open source and web development and how to encourage more women to join. (I even got to spend an awesome afternoon with a bunch of girls. I was supposed to be mentoring them but they were already Python game developers and small business owners – at the ages of 10 and 15!)
But the more I think about it, the more I realize that I am in this field because I really like the people. And 95% of those people are men and I appreciate them. I appreciate all the help they’ve given me whether they knew they were helping or not!
So I decided it’s time to thank all the men that I appreciate, who have helped me in my interests and my career.
First, there’s my dad. He not only told me I could do whatever I wanted to do, but promised to make sure I had the opportunities. I think he’s always been secretly disappointed I didn’t want to play football.
To my grandpa. He told me it was his sandbox, so I could play in it. He taught me how to defend my right to participate with out a leg to stand on — it wasn’t his sandbox. (And to Chris who taught me how to play toy soldiers in that sandbox. I still consider that to be one of the most boring games I know but it taught me how to steer the game or the conversation in the direction I wanted it to go.)
To my uncle John who saved all his computer magazines. He asked me once if I wanted to organize conferences. I stand by my firm answer of no, you’d have to be crazy. (But I do help out occasionally!)
To my uncle Larry who used to save me boxes of science fiction books. Boxes! Boxes of science fiction books! When you live in Spain and can’t get them that was a treasure.
To my great uncle Ted who was more delighted than I was when I finally managed to beat him in a game of cards.
To my boyfriend Frank who projects complete confidence that I can do anything. Except mow the lawn. But he is willing to get in a small boat in a big ocean with me. And he listens to my excited stories and my gripes and promises to beat up anyone who bothers me. I know he’s got my back.
And a whole bunch more people that I’ve talked to on IRC, IM, in hallways, over lunch or a beer, … I’m not leaving you out. But I do have to get back to work at some point.
Thanks to all of you. For all the conversations, for all the ideas you’ve shared, ideas you’ve given me feedback on, questions you’ve answered, trust you’ve shown, … I thank you. Hopefully I am successful in returning the favor or passing it on because I think it’s what makes our communities great. It’s what will continue to bring more men and more women to our communities.
That’s why I’m part of these free and open source software communities and why I’ve chosen this career path. For the people in the communities and the way we are making the world a better place together.
And I love the 5% that are women too! But I feel like I owe the guys a special thank you as we don’t often mention how encouraging and helpful they are.
You know those people that come into every meeting and everyone just loves their idea? Or they propose an idea on the mailing list and everyone immediately pipes in to say how great it is?
Ever wonder how they do it?
They do their homework.
Before they propose their idea to a large group, they’ve floated it by a lot of people. They’ve discussed it in various settings, public and private, with individuals and with small groups. They’ve explained it, adapted it, discussed it. Most importantly, they addressed a lot of key people’s issues ahead of time and incorporated their feedback.
In some meetings, I know the person proposing the idea has actually discussed it with every single person at the meeting before hand.
Yes, that’s a lot of work. But that’s how they get their ideas accepted.
It’s not sneaky. It’s getting feedback.
It’s not broken. It’s communication.
So if your idea didn’t get accepted, stop to consider if you could have done more homework. Communicated more. Incorporated more feedback. Addressed more concerns.
LinkedIn Maps takes your LinkedIn contacts and groups them. The result is not only interesting but rather pretty. You can mouse over the different nodes, see who they are and who else is connected to them. After a few nodes I was able to see patterns in all my groups but one …
The group I can’t identify is dispersed throughout the whole map and contains friends from college, old collegues from HP as well as people that used to work at O’Reilly. I believe the group is really one of people that don’t share enough connections with others in my network to fall into any one group.
I have really enjoyed working with GNOME over the past 2+ years. Working with the GNOME community on creating a free desktop accessible to everyone has been fun and exciting – as well as challenging – which is part of the fun. It is the community that makes GNOME, and it’s working with that community, in particular the board, that has made my job so much fun.
Over the past two years I think we’ve made great progress with the GNOME Foundation. We’ve more than doubled our income both from corporate investors and individuals. We’ve made great technical progress especially with all of the hackfests. And we’re well on our way to GNOME 3.0 which is looking like a solid release at this time. In addition we’ve grown teams and processes like the marketing team, the sys admin team and the travel committee. And you know all this because we’ve also improved our communication processes with things like the quarterly report and more active use of the GNOME Foundation blog.
And I can’t take credit for all this. Obviously this is way more than one person can do! It’s been a team effort and again and again I’ve felt extreme gratitude for all the hard working people on GNOME.
So I am really sad to say that I am leaving my paid position as Executive Director. It’s been really hard to write this blog post because I really don’t want to leave. (And I won’t be leaving – more on that later.) However, I’ve been offered a great opportunity to work on the open web at Mozilla. As you all know, I think we need to be pushing for freedom on the web as much as we’ve pushed for it on the desktop. So I see this next step as continuing in my contributions to making sure users have a completely free and open experience when using technology.
So what about GNOME?
The timing of my move comes at a time when GNOME is getting a lot of press. I’d like to give my thoughts on how GNOME will move forward over the next couple of months.
In particular I’d like to highlight one that’s at the top of everyone’s mind, GNOME 3.0. I am confident the GNOME community will continue to work hard on GNOME 3.0 and they will release it next spring when it is ready for end users. My leaving will not affect the development of GNOME 3.0. My job was to run the GNOME Foundation to support the GNOME community. I did not set technical direction nor contribute to the code base – the GNOME community, led by the release team, individual contributors and partners, sets the technical direction and does the work. While I will not have as much time to help with things like marketing and partner coordination, because of the GNOME Foundation, GNOME has the resources and funding we need to move forward with GNOME 3 whether it’s hackfests or resources for marketing. Not to mention that we have many partners hard at work on GNOME technologies like
Red Hat on Nautilus and Evolution … Igalia and Collabora on WebKitGTK+ … Novell on Sabayon and Banshee … Collabora on Empathy and Telepathy … Intel on Clutter … Litl on GObjectInstrospection … Openismus on gtkmm and anjuta … Oracle, Mozilla, Igalia and F123.org on accessibility … Nokia with a GNOME Mobile grant … Google on Outreach … Openismus and Canonical on the Bug Squad … Igalia, Lanedo, Codethink, Red Hat, Openismus and others on GTK+ … and many, many more
Where I can continue to help by supporting the marketing team or helping introduce companies, I will.
Another area where I’ve invested significant effort is fundraising. People have expressed concern that it won’t be easy to duplicate the work I’ve done. I’m proud to say that the GNOME Foundation is looking good financially. We recently hired a system administrator, sponsored numerous hackfests and we will now be increasing our administrative assistant’s hours. Our financial status is very solid and will continue, given the generous support of our advisory board members. I’m confident that with our current board, our finances will be well managed and we will be in a great situation for the new Executive Director to take over.
There are numerous other things I’ve been working on that might be affected. I’ve worked a lot on the marketing team and I hope to work with the dedicated team that’s grown there to make sure all the projects I’m working on move forward. The GNOME Advisory Board has been benefiting from regular monthly meetings. One of the board members will take over that and we have numerous topics lined up. For everything I’ve been working on, I’ve been working with the board on how best to transition them and make sure items that need attention are addressed in the next couple of months.
If you are working on a GNOME project and regularly checking in with me, please know that someone on the board will be available to help you and you can always continue to bounce ideas off me in IRC or IM or email. If you don’t hear from me about who your contact is, feel free to ping me or the board (board -at- gnome org)
Where am I going?
I’m going to Mozilla to head up their developer engagement program, focused on the open web! As many of you know, I think we have a complete free and open source solution for the desktop but we still have a lot of work to do on the web. Many of us now depend on web applications that are not only not free but don’t even let us download and protect our own data in reasonable ways. Working on developer engagement at Mozilla will let me dedicate more of my resources to making sure developers have the tools and knowledge they need to create applications on the open web.
(And I should point out that GNOME is hard at work solving the problem of how web applications integrate with the desktop with efforts like libsocialweb in GNOME 3 which will integrate instant messaging and social web sites into your desktop. In addition, applications like Tomboy, Banshee and Rythmbox are all integrating with the web. I hope my work at Mozilla will compliment what GNOME is doing and that we will work together.)
I’ve really enjoyed all my conversations with the Mozilla folks I’ve met and I am excited to be joining them. They are aiming to create an open standards-based platform for innovation without restriction. Something that fits very well into what I’ve been thinking and talking about for the past six months.
When I started at the GNOME Foundation, everybody asked me what I was going to work on. So I spent the first couple of weeks asking everybody else what they thought I should be working on. I feel a bit like that again. I’ll be working with the people and team at Mozilla to enhance and define their developer engagement program. I’ll be blogging more about Mozilla and my work there in the future.
What’s next for me and GNOME?
While my last day as a paid employee will be this weekend at the GNOME Boston Summit, I don’t plan to leave the GNOME community. I will continue to be active in the marketing team and I am always available to chat or help. My focus for the short term will be helping the board hire my replacement.
When elections open up for the GNOME Board of Directors next spring, I plan to run. I’ve really enjoyed and appreciated all the work the GNOME Directors do (it’s the most active board I know!) and I hope to be able to continue that trend and contribute my share. I believe the skills and interest I have can continue to strengthen the GNOME Foundation in its efforts to create a free and open source desktop for everyone.
And to echo a cry I’ve heard:
“Rock on, GNOME!”
“How do I raise enough money to be able to spend all my time working on my favorite free software project?” is a question I hear often.
I have a few ideas and I’m very interested in hearing others as I think the world would be a better place if we all could afford to do work we loved and thought useful.
- Focus on the difference you’d make. First off, I wouldn’t approach it as “I need to raise money to pay myself.” Unless you are raising money solely from people that love you, whether or not you get paid is probably not going to sway them one way or the other. You need to tell them what $100,000 a year would do. How would your project be great then? Who would it help? How would it make the world a better place? How would it help this particular type of sponsor?
- Believe it. You need to truly believe your project would benefit from the money and your work. If you aren’t convinced, you won’t convince anyone else.
- Figure out how much you need. It helps to have a goal. Would you quit your day job if you had $20,000 in funding? $100,000? $200,000? (Don’t forget costs like health care, vacation time, etc.)
- Identify different types of sponsors. Are you going to raise money from developers? Or software companies? Or philanthropic grant givers? Also think about how much money that type of sponsor is likely to give. Be realistic. Maybe they gave a project $100,000 once but they gave five other projects $10,000. You are probably going to get $10,000 if you get anything. Then figure out how many sponsors you’ll need. Figure out where those people are and how you are going to get introduced to them.
- Create a pitch. You need a really good web page, a good email, an elevator pitch and unfortunately, you probably need a slide deck too.
- Tell the world. Don’t ask everyone for money. But tell everyone about your project and what your goals are. (Hint: your goal is not to raise money but to make your project better. The money is a means to an end.) Use your elevator pitch. Listen carefully to their questions, their skepticism, their ideas. Evolve. Make your pitch better. Figure out how to pitch it to different types of people.
- Sell your project. Don’t forget to talk about your project. You aren’t just asking for money, you are selling the potential of your project.
- Collect stories. Studies have proven that people are willing to give more money to save one child identified by name and ailment than they are to save 100 kids. Personal stories are moving. Find a couple of stories of how your project has made a difference.
- Learn about them. You are not going to get any money from someone whom you don’t understand. Know them, know their business, know what they care about, know how they view you.
- Work with an organization that can help. For example, maybe you want money to work on your favorite project and you found companies that are willing to sponsor it but they don’t want to manage it. Would they be willing to funnel the money to you through a nonprofit organization that also supports your type of project?
- Ask. Talk to lots of potential sponsors, ask them for money, apply for grants, look for opportunities. If you don’t ask for the money, you will never get it.
What else would you recommend?
P.S. If you are looking to raise money to work on GNOME, please consider the GNOME Foundation your ally.
Photo by thinkpanama http://www.flickr.com/photos/23065375@N05/2247354856/
I’ve struggled with business dress for a long time. It’s inconvenient (requires ironing), complicated (business casual dinner for a woman?) and it’s often uncomfortable (why don’t women’s suits have pockets??) It’s even harder now that I work with people that are more likely to show up naked than show up in a suit.
I don’t care what people wear, and I’d much rather be wearing sweat pants, so why do I ever wear a suit?
I finally figured it out.
I do not want my clothes to make an impression for me.
I dress to not stand out. (At least when doing business.)
If someone at a business meeting is going to remember something about me, I don’t want it to be my clothes. I want it to be the idea I was talking to them about. So if they expect me to be wearing a suit, I want to show up in one, so they don’t even notice it. If they are expecting me to wear khaki’s, then that’s what I want to be wearing. So that my ideas get 100% of their attention.
And I’ll wearing my sweats as soon as I get home …
I find that when I’m procrastinating, I often have a question.
For example, this week I delayed submitting an expense report because I wasn’t sure what expenses were covered. The problem is that I didn’t realize that. I just procrastinated submitting an expense report and figured it was because they were no fun to do. When I finally sat down to submit the expense report, I realized I had a question. I sent it and got back a quick answer and suddenly I had no problem submitting the expense report. I no longer felt like procrastinating.
I also procrastinated responding to a business offer because I had questions as opposed to opinions. Again, it took me a few days to realize that. I thought I was just procrastinating writing up my response until I realized that I had a couple of key questions before I was willing to give my opinion.
So next time you are procrastinating, stop and think if you really have a question you need answered first.
Photo by jaaron, http://www.flickr.com/photos/jaaronfarr/1404738465
Either we need a business card substitute or I need a better way to remember who I met.
I see fewer and fewer people handing out business cards at conferences. That’s fine by me. But some times it’s really hard to remember the name of the person I talked to. I used to flip through my pile of business cards and I could figure out who it was. Now I have a hard time. I know what they look like, where we were standing and what we talked about. And I want to follow up. But I don’t know their name. So I end up using details and google and friends to try to find them. Sometimes it works, sometimes it doesn’t.
Ideally, I’d have a picture, name and email for everyone I talked to at a conference. With location and a few notes. People might think I’m weird, but I could start just taking a picture of everyone I talked to at a conference. But I’d have to remember to do that and I’m often in a hurry to get to the next talk or conversation.
P.S. I’m not sure if fewer business cards are the trend or if I’m going to different conferences. I’ll let you know after OSCON.
I’ve recently watched a few people struggle to get things done in online projects. I’ve written and spoken on 12 tips for getting things done in the open source community but now I see that people also need to learn how to work with mailing lists and virtual teams.
Skills you should master if you plan on working in a virtual environment. I’m interested in any other skills you’d add to the list.
- Master your email. You will get a lot of email. There are few in person meetings and there’s a large group to coordinate, so email is the most popular method of communication. Email will become a knowledge base. You need to be able to handle hundreds of emails a day without complaining that they are too many. (You don’t want to be cut off from the knowledge base do you?)
There are lots of ways to master managing your email. Here are a few of the most common:
- Touch each email once. If you read it, think about what you need to do with it and do it right then. If it’s something that requires action outside of email, add an action item to your todo list and then tag the email or file it in a special folder. Get it out of your inbox.
- Use a threaded email client. It’s much easier to catch up on conversations if you can read the whole thread easily at once.
- Use filters. Many people filter mail from different lists or about different topics to folders. (I personally do not do this. I find I never look at them if I do this.)
- Dedicate certain time periods to checking email. I spend the first couple hours of every day responding to email. I don’t look at it as “doing email” but rather as communicating and following up with people.
- Research and try. There are lots of methods and tips for dealing with incoming email. Try a few of them and figure out what works for you.
- Learn online tools. You should know how to use mailing lists, IRC, Skype, Twitter, IM, wikis, etc. Each team will use a different set of tools, but you should know the basics of most of them. That way if someone says, let’s have an IRC meeting in a hour, you won’t be googling “IRC” to figure out how to join at the last minute. Or looking for a headset in order to join a Skype call.
- Know where to find things. People that work online usually deal with a lot of information. Learn how to search your email archives effectively, how to search the mailing list archives, where the project stores documents or information online and how to search. If you need to ask for information, also ask how the person found it. Often they are simply searching for it. Do not ask for information that you can find easily yourself. Above all, do not ask for the same information twice! If you asked for it and got it, you should be able to find it again. Feel free to ask someone how they found the answer to your question. I learn a lot that way.
- Observe how things get done. Every virtual or online team is different. Watch how things get done. Do people present ideas before they are done? Wait for consensus? Present final products for review? If nobody ever responds to your email, it’s likely you are not following the project’s culture.
- Be prompt. With people working in different timezones and with different priorities, it’s important to respond to emails and to finish action items promptly. Each delay seems to multiply across the project.
- Keep the group informed. If you have a discussion off list, be sure to let the rest of the list know. Don’t be afraid to have the discussion on the list. If you make decisions or agree to something on the group’s behalf, be sure to let the rest of the group know.
- Know when to take it off list. Sometimes it’s best to have a discussion offlist first and then tell the group the outcome. For example, if you think your idea is controversial or too vague, you might want to run it by a few trusted people first. But remember, to get buyin and build consensus, some of the discussion has to happen on the list – it can’t be all polished decisions!
- Rethink conference calls. If you have conference calls, make sure everyone has access to good technology and make sure everyone is on the phone, not just some people. I think Nat’s Everyone Dials In policy is an excellent one. Also be aware that conference calls are particularly difficult for people that have to dial an international number to join and for people who’s first language isn’t English. While you may think conference calls are the most effective way to get things done, if half the team can’t hear or communicate well, IRC may be a much better choice.
- Learn how to read silence. Sometimes you’ll post a great idea or a question to the mailing list and nobody responds. Does that mean nobody liked your idea? Or that they couldn’t understand it? Or that they are all busy on the release that’s going out the day after tomorrow? In the absence of body language, you will have to be more aware of everything else that is going on.
- Know what’s been done. When you join a project you should spend some time observing, asking questions and reading the archives. If you suggest a multitude of projects that already exist or have already been proposed, people are going to think you aren’t willing to learn the project.
- What else would you add?
For suggestions on how to get things done in virtual teams, see 12 tips for getting things done in the open source community.
This quote has been haunting me because it rings so true:
men tended to stick with their studies as long as they completed the coursework, while women did so only if they earned high grades
I don’t see that in all fields but I definitely see it in computer science. I wonder if it’s because only really competitive women tend to stick it out in a field that’s often less than 20% women (and comes with all the problems that entails.) They are used to working hard, competing and doing well. And when they don’t, well they figure they should be doing something else. Something they excel at.
I’ve seen it happen. (And for the record the women I know went on to be really successful in other scientific fields. I think they would have excelled in computer science too.)
What do you think?