Wednesday, October 15, 2014

Evolution of a systematic and traceable, robust and scaleable system for onboarding volunteers.

I want to make sure everyone has seen the all new Get Involved page  and to give a huge shout-out to the many, many Mozillians, including many of you, who have been involved in setting this up, along with Guides - our new community forum designed to support brand new Mozillians.

(Note that localized versions of Get Involved are coming soon! Many people here have been involved in getting the locales up, and that is critically important. Thank you. We can't wait to share that work with the world.)

David blogged about it too, including some history of the page and the importance of this system in what we do as a community here at Mozilla.

This set of improvements will allow us a far more robust tracking and followup system for community as well.  I look forward to growing and learning with all of you. The metrics we will get from this new system will allow us to trace volunteers from signing up for an opportunity through becoming an active member of our community - and all the places people could get lost along the way can be addressed. This is a huge opportunity for improvement.

Thank you to every one of you who made this happen. Especialy big thanks to Jennie Rose Halperin, Emma Irwin, Matthew Zeier, everyone on the team, our Stewards, all the community who helped and were interviewed and reviewed prototypes, and our dedicated localizers.  Building programs and tools like this with all of you is my sincere pleasure and joy.

This is how we will build the internet the world needs - with the power of a scalable way to help people figure out what they want to do - and support them in doing it.

Wednesday, July 2, 2014

The Web We Want is Private: Building a global community of Privacy Contributors and Advocates through Mozilla

[This is the first of a series of blog posts related to my new-to-2014 role leading Contributor Development as a Community Builder at Mozilla. Most are also posted on Mozilla’s about:community blog.]

I’ve never actually been that good at keeping things private. I’m a talker. I’m not usually the one to keep your secret. I learned the hard way why one should be careful with passwords and privacy via a few embarrassing linkedin and twitter incidents. Despite having learned my first system administration in college in 1993 or so, I have been pretty hopeless at staying private. But. I’m learning all the time. And, increasingly, I see that privacy is about a lot more than my learning to use Last Pass correctly, or the settings on my facebook (though those are important things).  It’s actually central to all that we do online. And if I can learn the value of privacy, anyone can.

When we started the Community Building Team this year we chose teams to work with as partners, to help them build Mozillian community. One of the teams I chose was Privacy, and I was privileged to be partnered to work with Stacy Martin to grow the project we’ve come to call PriMo - or Privacy Mozillians. Working with the newly established Contribution Lifecycle, we brainstormed projects we’d like Mozillians to do around privacy, and we listened to people around the project’s existing ideas and needs for privacy community.

Stacy: "Larissa has been a great connector for us.  She is aware of what other teams are doing and helps point us in the direction of content and ideas we can leverage.  She suggests ways to include Foundation projects, such as Webmaker and Open Badges."

We started out with a call for privacy advocates to rally around Data Privacy Day and started to collect a few contributors.  Following on his assessment of the needs of community in Utah, Mozilla L10N engineer and Rep Jeff Beatty started a program around TACMA screenings - which has been very successful and will be expanding soon to include screenings in more Mozilla spaces and in communities as far apart as Utah to Zimbabwe. 

Outside organizations also have been reaching out to us for support in privacy - the National Network To End Domestic Violence asked us to develop best practices for browser privacy for survivors, and a community project is evolving. Please check out the NNEDV Browser guidelines project to learn how you can support this effort.

Throughout all our efforts, we're also infusing educational opportunities to learn more about Privacy, and building community of privacy educators - that can be as simple as learning to teach family members how to use lightbeam over the kitchen table on a Saturday afternoon.

The relevance of privacy work becomes more clear all the time. When we released Firefox 28, we did a global campaign to ask our community - the global network of Firefox Users - what kind of Web We Want. Resoundingly and around the world, they responded: the web we want is private. With the development of PriMo, and projects such as the TACMA screenings and NNEDV browser guide among many, we have the power to take that energy and enthusiasm and turn it into action - one privacy advocate at a time.

I ask you to invite your privacy leaning friends and family to become privacy action takers
- whether that means downloading lightbeam (or teaching someone else to),  signing our Net Neutrality petition, taking action to support our work with NNEDV, or attending (or hosting) a TACMA screening when it comes to your town…  there are many actions large and small that can add up to a strong global community of privacy advocates.

The web we want is respectful of each of our autonomy, our privacy, our data, our needs. The web we want is open to innovation and includes diverse voices. Building community for privacy means casting a wide net and calling many kinds of people together - people who have been involved with Mozilla a long time, and people who are just learning what we’re about. It will take many people together to change the culture of the web. What kind of web do you want?

Wednesday, January 8, 2014

My Nerd Story

[My colleague Crystal Beasley started this thread of women in tech/hackers posting our stories, in response to some comments out there.... This is my nerd story, shared with you because I do believe in role models, and I do believe that there are many paths one can take.]

I am, among other things, a daughter of Silicon Valley.  Mine is not a story of arriving at tech from the sidelines, or of dedication from childhood. it is more a story of how exposure shapes you, how marinades work, if you will. This is not the story of a straight path, or a clear dedication from childhood to one goal.

I was born in Manhattan, but we lived in New Jersey while my dad was working on a pHD at Rutgers in Computer Science. When I was four, someone at school asked me what my dad did for a living and I said "he watches tv and hunts for bugs, but I never seen em". He had a dumb terminal at home, presumably by then for his job at BBN.  I was watching. I did not get to play with dad's bug hunting TV, but I was steeped in tech from an early age, and I value the gift of that early exposure. Early exposure is one of the things we must give to the future nerds... take time to talk to the kids you know (it takes a village to raise a child) about what you do!

Similar, if not identical, to this one.

When I was six, we moved to California, dad was taking a job at Xerox Parc. I went to school in Palo Alto, where, after a year of public school, my sisters and I were sent to Peninsula School... at school, we rarely saw anything one would call a computer, in the early to mid 80s. I do remember cranking the mimeograph machine. Home was another story. Following his days at Xerox Parc dad went to Apple, where he worked on and brought home the first computers I played with.... to wit the Apple II and the LISA. I remember that he made us "play" the mousing tutorial over and over - he wanted my 3 year old sister to be comfortable with it.... and she was.  Maybe it was a bit like...

OK maybe not quite like that. But close.

At the same time, in school, while I was great at conceptual math, I floundered in basic computation. One teacher told my parents I was bad at math because while I excelled in our "regular" math program, understanding logical puzzles beyond what one expects of a seven year old, I could not successfully complete the math "drills" we had to do at the beginning of each day. She called me stupid, and I didn't forget it. My parents quickly moved me to another school (lucky us, with the resources for private school) where that did not happen again...

Years of playing with dad's computers followed. He went from Apple to EA to SGI, and I played with all his machines. Eventually this led to us having what we thought was the coolest house in town, because we had an SGI machine on which to play Doom, in our garage. I didn't code much at all... what I got from those years, I see now, was a measure of fearlessness about trying out new technologies. At the same time, my mom, whose background was literature and education, became a technical writer, showing me both that careers can change, and that it is possible to manage a technical career and motherhood together. She was leaning in way before it was hip. It might follow that all of this early exposure might send me straight into a technical degree and career. It did not.

I thought I wanted to be an elementary school teacher, and I enrolled at Mills College with every intention of doing that, and instead was moved toward Women's Studies and later theology, primarily driven by one of my great desires in life - to understand human motivation, and another, to work for a better world.  At the same time, I was for the first time being exposed to the full power of the internet, in 1991 a very heady thing, to have your own unix shell account and a world of people to talk to. I learned a lot from just "playing" online, and more from having people around willing to answer my many questions, and it turned out that these same explorations led me down my career path at least as much as any formal academic education. All information is useful. I do not think it is *any* accident that this critical period of learning and exposure happened at a women's college, where a brilliant woman ran the CS department. We were not just allowed but encouraged to explore many paths in that rarified atmosphere of empowerment (we had access to lots and lots of technology and to smart people who wanted to help), and I did. I've always been grateful for it. It was also where I learned about geek culture...

I went to grad school in feminist theology, but technology was in my blood by then, and when I realized I didn't want to be a professor, I left academic life and came home, with a lot of school debt and not a lot of ideas. I was stunned, in 1995, at the power I saw in the world wide web, to connect people and share thoughts and information (I still am stunned by it).  I wanted in on it.  It occurred to me that I could go into the "family business" but not really *how*. I started working as a temporary contractor, at offices in the valley, and I tried a few things (writing very basic databases on semiconductor data, pre-press work for technical manuals, filing payroll stubs) before I landed my first "real" tech job, at Sun Microsystems (a very exciting place to be... we were, after all, "the dot in dot-com" heh)...

At Sun, I stuck my neck out, trying as many new things as I could... I worked first hand-htmling white papers, then hacking basic surveying tools (perl, mostly) for beta programs, then became a program manager for Solaris beta programs, and at last, got my first whiff of open source in Open Solaris. The biggest thing I did was learn. I found it to be an atmosphere where engineering and education were both valued, and where my questions were not "stupid", and I was lucky in my choices of mentors and friends. I took every class I could, read every book I could, and tried to give myself the technical, business, and project management skillsets I hadn't obtained in school, before deciding to take the oft-discussed "mommy break" to prepare for the birth of my second child. When I was ready to go back to work Sun was no longer a viable place to go, so I gathered my contacts (networking is your friend) and my consulting skills and ended up with a rather long term contract release managing a web "portal" (in 2005, everything was a portal) and exposing myself to everything I could about CRMs, release methodology, localization, networking, and more. I explain all of this background, mostly because my biggest lesson was that the education I got was in what I tried, and in what I failed to do, as much as in what I succeeded at... and I think we need role models for that, too. In many respects, the entire first part of my career was my technical education.

After all of this, I still did not see myself as a role model, or as highly technical. I was quite shocked when a geek friend encouraged me to apply for a job as product manager at a very obscure seeming and highly technical nonprofit open source infrastructure shop (Internet Systems Consortium, makers of BIND, the widely deployed open source DNS nameserver, and operators of one of the 13 root nameservers). For the longest time, I couldn't figure out why they hired me! I knew very little about DNS, infrastructure, or protocol development, but I found my mentors again, and I found that I flourished, traveling, working on critical processes, figuring out how to work with highly international teams, solving hairy problems, and most of all, embracing open source and the vibrant community that loved and supported our efforts so very much. I learned most of all again, by making mistakes. I learned what it takes to build a vision for a product, and how building things in the open and in community takes all sorts of specific skills, talent, and patience, but how much value it brings.

It was also around this time that, through the amazing TechWomen program (which brings technical women from the Middle East and North Africa to Silicon Valley for mentoring), that I got hooked on mentoring other women in tech, and mentoring in general, and supporting women in tech, particuarly  in open source and open culture. It was really when I started mentoring, that I started believing in my own abilities, too. That was a long lesson to learn.

In the end, my work and my values brought me to Mozilla, where I've been lucky enough to end up doing community building full time, following my passion for empowering people to find meaningful ways to contribute to the internet I believe the world needs, an expansion of the one that excited me so long ago, (and changing open source culture in ways that it needs) and I get to see a lot of the world while I do it... my nerd story has had its painful moments, but I wouldn't trade it for anything.

Sunday, October 13, 2013

Next Steps After Summit - The Mozilla Summit 2013 Session That Wasn't Quite

  Long ago, at a Mozilla Summit... well, last week... several Mozillians planned an afternoon "supporting session" called "Ideas Into Action: Next Steps for Me and My Team". It was planned for Sunday afternoon, but for a variety of reasons (mostly, I think, the plethora of amazing technical Open Sessions that cropped up like mushrooms after a rain) was not well attended. Karen Rudnitski, Selena Deckelmann, Ernest Chiang, and myself, had put some thought into a framework for y'all. I think it is still helpful. Maybe especially now, a week after Summit, with the clouds of #MozFlu and our hangovers and jetlag dissipating at last. I don't know about the rest of you, but I'm feeling overwhelmed with finding time for my big ideas and wild notions among the day to day, already, again.

To that end, and to further the goals of our once poorly attended session, I submit to you:

Ideas Into Action: Next Steps for Me and My Team - Blog Edition

I encourage us all to consider the following four steps:

Remember what got you excited at Summit!
Was it the "Million Mozillians" idea? Candy Crush on Shumway? Security Champions? Appmaker, Marketplace, L20N? A conversation with someone you didn't know before - whether from Botswana or Belize (or Boston)? Write it all down. Big and small things. Maybe you already did this part. Find those notes.
Personally, I was really excited by the idea of the "internet the world needs", and volunteer community security champions, and open badges, and this totally badass robot made from an old One Laptop Per Child box that the folks from Uruguay brought to the World's Fair…. or the Innovation Fair…. one of them). How to make a Popcorn class work in a situation where there isn't reliable wireless (local web server of course).  All the open hardware stuff, and Liz Henry's "bug bracelets". And every new person I met.

Remember the four pillars Mitchell walked us through.  
Build, Empower, Teach, Shape. How do your favorite Summity things connect to the four pillars?

Come up with goals that tie these ideas together for you - in terms of how you could further the mission, build the internet the world needs - through what you do, who you know, and your own unique contributions.  

Think of small, achievable actions, that will move you forward on these goals.
One for each. Or a few, but then only consider the first one as an actual "to do" item for now.

Think of another person (probably a Mozillian) who could hold you accountable for these actions, and ask them to meet with you at regular intervals to discuss progress. 
 Offer to hold them accountable, too. Keep meeting with them and iterating through "small actions"… and watch for big results. (This trick is not my invention, I got it from TRIBE... and it's been working for me!)
It is easier to think big thoughts when we're away from home and from regular work - that is part of what events like Summit are for. A few tricks are needed, to turn ideas into action, once we're back to the grind.
I cannot wait to see what we do.

Saturday, September 28, 2013

Dusting off the blog. Yes.

I have in fact been communicating online in the last year, just... not here. A few outside old blog posts of mine...

And I tweet incessantly.

These days, I am working for Mozilla, and what I'm most excited about at the moment is community building, and most particularly the Mozilla Summit, which is coming quickly, next weekend. My specific roles include organizing the Innovation Fair, and working as a Track Owner for the Product and Technology track for the 3-city event, as outlined in our founder Mitchell's blog post from yesterday. I've recently made a commitment to myself to start blogging more again... so... perhaps this shall get less dusty.

Sunday, October 7, 2012

An Inspiring Panel on Women and Innovation at GHC

I was really looking forward to this panel, as I struggle to see myself as an innovator... and I wanted to be inspired. I was. The panel was moderated by  Dr. Francine Gordon, who is one of my colleagues in the TechWomen mentoring program, but far beyond that, she has a  Yale PhD,.... runs  TED Women Bay Area... and has many more honors I cannot even count. I knew she would run a truly useful panel. The panelists included Rahima Mohammed of Intel, who was also a TechWomen 2011  mentor, Nina Bhatti, product development engineer at Hewlett Packard, Judy Priest, Cisco office of the CTO, and Kathleen McKeown, director of a new institute for Data Sciences and Engineering at Columbia and Winner of the ABI Women of Vision award for Innovation in 2010.

This panel helped so much with realizing where and how I already innovate. Rahima challenged us that  one thing women can do as innovators is to "think of the problem in a slightly different way"

Nina Bhatti pointed out that innovation is only that when it actually gets into a user's hands, and that the implementation and user focus of an idea is something many women excel at.

Judy Priest, Cisco office of the CTO pointed out that  innovation means targeting things "in the right time and place" - not pushing too much on the envelope and telling competitiors what you're doing.

Moderator Francine Gordon suggested that many women don't think of ourselves as innovators... but as problem solvers. Girls have as many characteristics as innovators as boys... but they (like women) see themselves as problem solving when they innovate.

Francine also ran through an amazing list of great women innovators such as Helen Greiner, inventor of the Roomba, Judy Estrin - co-founder of Cisco who wrote The Innovation Gap... about private/public/university collaboration for innovation, and Margaret Knight - holder of 26 patents - invented a machine that allowed paper bags to have square bottoms and several patents arond the combustion engine... called by some the "female Edison".

Questions for panelists:

What does innovation mean to you?

Rahima: It needs to be new, and be solving a problem that has a real need base, someone has to *use* it. Its not enough to have an idea, it has to be brought to someone who uses it.

Nina: when you get irritated by something, this should move to a problem solving point and then looking for innovation. Another place to look is a greenfield area, at the front of technology, because other people aren't there yet. You can get to the problems first, and the first solutions, wrong or right, set the trend. A key part of innovation is figuring out where to put your energy, that serves you organization's needs and a perceived market need or desire.

Judy: You also can innovate in integration, and in business models, not just technology. You need to expand your definition on innovation and find new ways to apply it. There was a famous story of a woman who invented the rotor thats in vacuum cleaners, because she was tired of sweeping the floor. Alas she didn't patent it. And the same mechanism is now used in amusement park rides.

Kathleen: what is the difference between innovation and invention? Being at a university, my first reaction was "I don't know", and I looked it up on wikipedia, and the definition there was that innovation is something new that has a *use* as a product, while invention is something novel, a new process or technology, and it doesn't have to have a use necessarily. So as a university person, the line blends. So for me, innovation is building a new system that does something cool. I don't think as much about the customer or user, though I do think about needs.

Francine: What attributes help you to be an innovator?

Kathleen: I like going into an area where I can be first, where no one has gone before. I often feel very afressive about that, wanting to push for it. Usually in the beginning I get a lot of "no"s, and my reaction is determination and almost anger. These people are wrong, and I know they're wrong, and Im going to show them.

Rahima: I like to figure out the most critical problems, and where will I get the biggest return on investment with the resources I have. Also really questioning and experimenting, and connecting the dots, associating the problem with another problem, after that also to build a network, try the idea with different kinds of people. To be successful doing something new you need a strong passion, the first time it doesnt work, second time doesn't work, but maybe the third time. Don;t give up when you hear a "no".

Francine: you can't take no as a no. It means try again another way.

Judy: One of the biggest questions I get is "where do the ideas come from" - most ideas are not siloed, problems are more complex than that. Talk to your friends. A good idea will solve a *significant* problem.

Nina: I pitch my ideas to people who I trust and who I know will listen to me, and see how their reaction is, I look for them to light up. If they don't, I go back and rethink. Then I go to experts in the area.

Francine: Failures?

Kathleen: in the academic world this is about not getting a grant or losing the grant once you had it. I sometimes wrote 5 or 6 proposals and didn't get funding before I finally did get it.

Nina: If you're trying to do something you havent done before, there is always a possibility of failure. Go for the risk area first, not last. You should not have a failure of execution. That's just a planning failure. There are failures of fit or agenda within organization. There is also a failure *To take the risk at all*. Are you failing to live up to your potential?

Judy: Failures are like bad relationships, not a black and white thing, good parts and bad parts, but a good innovator knows when to pull the plug and when to course correct. There's always something that can be gleaned or leveraged for the next thing, too.

Rahima: in many companies there is an employee review process, and people worry if they fail it will affect their review. So we fear it. But there can be failures even when all the risks are calculated. So you need a system that helps you tolerate failures. You really should have a strong handshaking agreement with your management system about your innovation. If you're not updating them about the risk, this is where you can fall flat. Get people excited, and communicate, and then even if it fails, its okay, you move on, and you are ok with management.

Judy: you also have to assign a timeline and not let things run on forever, and negotiate that up front.

Francine: remember that what some people call a failure another person calls a success. Many inventions we use today were "failures", penicillin is the most famous, but saccharine is another example, someone was trying to find new uses for coal tar, and he didn't wash his hands, and then tried to eat, and it tasted sweet, and they discovered saccharine (ew?) but...

Francine to panel: wht are the differences between your male and female team members?

Kathleen: I do always watch the women in my group. Right now I have a team and we are building a large system with a huge amount of data, and getting it done on the grant timeline is a challenge. I notice that the men on the team are very strong in stating what they think should be done, and why, and they state it in a tone of authority. They're often right, but watching the people, the women on the team, they are working extremely hard and very knowledgeable but much more soft spoken about it. I've had this experience a lot and seeing who speaks the loudest and who speaks more quietly, the quirt spoken people often know quite a bit. One of my roles is to manage communication and make sure the quiet ones get heard.

Rahima: I am very blessed in my team, I'm always looking for women, so almost half my team are women, and yes, the men are strong communicators, and women are strong collaborators, they want everyone to agree... the women want a nod from all four people on the team to proceed in an idea.

Nina: I have a no jerks policy. Innovation is a risk and I want everyone to feel safe. I had a boss, once, who was a problem and I called him on it, he was harassing one of my team members, and he didn't even know he was crossing the line, but it was really important. A culture of safety is critical. People have to be safe saying half formed ideas and know they wont be jumped on. So for me its not a man or a woman, I had quiet guys and balanced women, maybe because I auditioned people for fit with the team.... that is the key.

Judy: if someone on the team says "that's the stupidest idea I've ever heard" about aything, that person is a dream thief and they need to be off the team. Its hard for women to feel comfortable with 30% definition, women seem to want 75% definition. As an innovator, though, your job is to find the constraints and risks and then proceed boldly.

Question from the audience: Who do you define success as an inivator?

Rahima: It could be solving a problem you're working on. We think it has to have a patent, a trade secret, whatever, to be a success. Even solving a small problem can be innovation and save a lot of time or resources or otherwise be very important to your organization. Its not useful if nobody adopts your idea, it remains a discovery or an invention, does not become an innovation.

Kathlee: in the University setting, there are successes along the path, but when you see people pick up on it, thats huge success. When people download your software, that's success. Another way is it gets picked up by the TechVenture office, or people from outside the University come to you and say they think your software will solve their problem.... it takes time and you see it in stages, but the feedback is where you see it.

Francine: lets move along to patents for now. First question: what's the value of patents?

Nina: there are some things you *don't* patent because you want it to stay a trade secret. Sometimes women controbute to the ideas (not just women) and then they dont get their name on the patent, and, if you came up with any idea, you need to be on it or it invalidates the patent. Really. Also writing a patent is like publishing a paper. You can then discuss it publicly. There is a value in patenting because then when you leave th company you can still discuss it.

Francine: how do you know when you have a patentable idea?

Judy: we have a committee at Cisco, patents are very expensive, so we have to assess carefully. It costs us 30-50 thousand dollars for one US patent. The patent committee looks for the business case, the business value, is it detectable? Is it novel? If we patent it are we just telling someone else how to test a new product? This is important.

Judy: something to consider is whether its more important for things to be known as "your" idea vs the idea getting through... that depends on the situation. Think about it, but also don't give up, an when you can, own your work as yours.

Truly, this panel inspired me not just to be bold, but in how to foster a culture of innovation, and to see how I already *am* an innovator. This was a fantastic session and I hope it is a theme we see in the  future at Grace Hopper.

TechWomen in Baltimore - Grace Hopper!

It has been so much fun to be at Grace Hopper this year with 41 women from the 2012 TechWomen class, four returning members of the 2011 TechWomen class (who did a fantastic panel... see my other blog:  Technical Women in the Arab Region: Challenges vs. Aspirations) and quite a few of the program mentors. Running session to session I saw participants everywhere - engaging at all levels, together, separate, checking out booths, in sessions, sitting at our TechWomen tables. TechWomen is an initiative of the US Department of State which brings highly qualified technical women from the Middle East and North Africa to the San Francisco Bay Area for a mentorship with a local professional technical woman (industry or academia) and this year all the participants came to Grace Hopper, a wonderful opportunity for all involved.

The Emerging Leaders were honored at the Thursday plenary, which is wonderful. Many excellent sessions followed - I particularly enjoyed being with the Emerging Leaders at a session on mobile phone apps in developing nations, and the "Women and Innovation" session where mentor Francine Gordon moderated and 2011 mentor Rahima Mohammed (Intel) was one of the panelists. There was one great moment Thursday night, when two of the Emerging Leaders and I were watching the dance floor from up above. I said "this is what a mosh pit of technical women might look like?" and we just all kept saying "technical women mosh pit!" and laughing - because it was so inspiring and fierce and fun. But even better was watching the Emerging Leaders participate in the community of technical women - each with her own unique voice.

Saturday morning the delegation from TechWomen moved on to Washington DC for another phase of our program... and as the bus pulled out, I felt sad, because, I've come to love Hopper so much...  here's to next year.