OpenSUSE Community Week

OpenSUSE is holding a community week this week, with a GNOME track. Curious as to what that really means, I asked Vincent Untz and Zonker (Joe Brockmeier) some questions. I really like that open source projects often find really new and effective ways to get things done.

There's a openSUSE community week going on right now, what is a community week?

Zonker: Our community week is a chance for experienced contributors to help pass on what they know about packaging, translations, testing/QA, and so forth to newer contributors and mentor them a bit to help them get started. It's also a chance for people to just pop in and meet with a lot of contributors to learn more about the project and ask general questions about the openSUSE Project.

Vincent: It turns out that there are many people out there who are interested in helping but they just don't know how they can help. This is where the community week is really helpful: we introduce people to the various activities that are handled daily by various teams, and we show them how they can contribute to this activities.

How do people join?

Zonker: In the various IRC channels. There are separate channels for the GNOME team, KDE team, marketing team, etc. You can find them all here: http://en.opensuse.org/Communicate/IRC

How many people are participating?

Zonker: Hard to say. We've about a dozen openSUSE contributors who will be leading sessions this week, and more who've helped with setting up the schedules and recruit people to lead sessions and so on.

According to the Facebook page we already have about 100 confirmed attendees, and I'm pretty sure that not all of the openSUSE contributors and new contributors use Facebook, so I'd say it's well more than that. Looking at the IRC channels today, I'm seeing quite a few nicks in IRC that are new. I'd say by the end of the week we'll have seen hundreds of people join in sessions across the various topic
areas.

Vincent: Just a (random) data point: in #opensuse-gnome, we generally have around 60 people. When I looked at some point yesterday, we had 80-85 people. That's +33%, which is quite good. Also, it's IRC, so we get people joining and leaving at all time of the day ๐Ÿ™‚

Of course, not all of the new faces have time to contribute, but they are able to learn more about the community this way, which can only be a good thing.

(oh, and the not-so-new faces — people who were already on IRC before the community week — are also contributing too)

Are they still working or did they take the week off?

Vincent: It really depends on the people — some people are investing some of their free time at work, some are not working (students, or people taking vacation). And then we have some interesting cases like Christopher Hobbs: he'll lead the GNOME Bug Day on Friday, and I believe his employer lets him handle this specific event on his work time.

Zonker: For Novell employees, this is part of the job to engage with the community, so I'd have to say "still working," but people doing Community Week should be doing this as part of their normal work. Not all the topic owners are Novell employees, so I can't say whether our other contributors are taking time off or getting time off to do presentations.

What type of work gets done during community week that doesn't normally get done?

Zonker: Primarily, a lot of mentoring and teaching. It happens other times, of course, but this is more of a focused effort.

Vincent: I can confirm this. Based on the past two days, the main difference is that experienced contributors take more time to help newcomers, and newcomers ask more questions.

What are you most excited about so far?

Zonker: We seem to be getting a fair number of participants so far, so I'm excited by that.

I'm also surprised, but probably shouldn't be, at how many groups are jumping in and setting up sessions of their own — the Samba team, Education team, and the openSUSE Weekly News folks have already
volunteered to do sessions though those topics weren't on the original schedule. Which is, of course, awesome. The more the merrier!

Vincent: One thing that really strikes me is that people are willing to learn. It's not something new, but it's really good to see people curious about things, and experimenting, asking questions, etc. to learn the right things to do.

Also a really good surprise is that the Thunderbird people are planning a Linux testing day this week and coordinated it so it ends up the same day as the GNOME testing day of the community week. So we'll have packages of the latest thunderbird code for people to test. I didn't expect some cross-project effort like this, and I'm quite excited about it ๐Ÿ™‚


What's in store for rest of the week?

Vincent: On the GNOME side, we'll have some wiki space reorganization, but most importantly we'll have a testing day on Thursday where we'll get feedback/bugs from people on various features or applications (thunderbird, multiscreen support, probably pulseaudio, also hopefully the new at-spi-dbus code that will be the basis of GNOME 3.0 accessibility, maybe also gnome-shell, etc.). Then we'll have a bug day on Friday where we'll triage the GNOME bugs filed against openSUSE, and forward all the relevant ones upstream.

And of course, people seem to want to package applications, so this will be an area where we'll keep helping people! We plan to have more volunteers this week-end to help mentor, and so we'll see quite some action on Saturday and Sunday in #opensuse-gnome!

Zonker: We have a lot more sessions for packaging, testing/QA,
GNOME, KDE, marketing, and openFate will all be on the schedule. The
openSUSE Board will be holding several sessions Wednesday and Saturday
to meet with contributors and answer questions about the board and to
get
feedback.

Zonker:  You can find each of the schedules here: http://en.opensuse.org/Community_Week

There's still time to join them!

A call to support open source software projects

Many of you saw J5's call to support the GNOME Foundation. The initial response has been great! I wanted to follow up with a general call to support open source software projects financially.

The GNOME Foundation is a 501(c)(3) nonprofit. By definition it must serve the general public and by definition it must be supported by the general public.

Our charter is not to be supported by a small subset of companies, but to be supported by a large group of companies and individuals. Remember 501(c)(6)'s are trade groups and are supported by a group of companies. Their charter is not to help the general public but to help the business of their group members. The GNOME Foundation is a 501(c)(3) – which helps the general public. 

The GNOME Foundation has been lucky to have a group of companies that support us financially. With their help we've been able to do a lot of good things over the past 10 years. We've had annual conferences, hackfests, and programs like the accessibility outreach and women's outreach programs. And while a number of companies have expressed their interest in
joining the GNOME Foundation and supporting us financially, the reality
is, very few companies are adding anything to their budget this year.

But compare the GNOME Foundation's financial support from 12 companies to the FSF's model.

The FSF receives most of its funding from 1,000s of individuals. According to their 2007 tax forms, they raised $845,000 from the public. (That number probably includes companies, but it's mostly from individuals.)

That is a much stronger position to be in. Not only because they raised more money, but because they are supported by the many individuals.

Open source software has shown the strength of individuals in creating great products. In the FSF's model, they have also shown the strength of individuals in being able to financially support causes they believe in. Providing your own financial support enables you to do what is right for your project. (Companies don't prevent us from doing what is right. But when they provide funding, they set direction. For example, when we depend on them for funding for hackfests, we hold the hackfests they are interested in sponsoring. Luckily, they sponsor good things! However, there is much more we could do, like the GTK+ hackfest we wanted to have this year.)

Bradley Kuhn and I were talking at the Collaboration Summit and we were thinking we should have a campaign to encourage open source software fans (users and developers) to support open source software financially. Pick two projects, any projects, and support them. Here's a short list of some projects that are set up to receive donations and use the money to support their projects:

In addition, I'd encourage people to sign up for "subscription" plans. Having regular donations come in helps projects plan things.

I have a few more posts coming up:

  • Voice your opinion of how money should be spent. For example, voice your opinion on the mailing list when the budget is shared or when the call for plans goes out. (And if you aren't in favor of donating money to free software projects, share ideas on how things can be done with no budget or which things you'd like to see cut from the budget. Or how you'd like to obtain the money.)
  • Participate in your project's non-code plans:
    • In GNOME's case, become a member of the Foundation and vote for people that support your positions! Not only is your vote very important, but having a strong membership helps the Foundation show what it has to offer when discussing our technology and our plans with potential partners and sponsors.
    • If you have the interest or skills, join the GNOME marketing team – help create our messages to the general public or run campaigns like Friends of GNOME or a merchandising store.
    • Speak about free software, why you believe in it and your project to the general public as well as at open source events.
    • Help your friends use open source software. Don't push them but be there to help them install it, even if it's just one application like GIMP or OpenOffice. If it works well for them, they might come back and ask you for others. Encourage them to contribute (skill or money) if they have a good experience.

And of course, continue to write great code and create awesome free software projects!

Which projects will you support?

Hackfests, fundraising and the economy

When I took this job it was agreed that part of my job, but not all of it, would be fundraising. However, because of the economy I find myself thinking about fundraising more often than not these days.

For example, take hackfests. Hackfests are events where you get all the key developers for a project together in one place and they spend a few days or a week discussing issues, planning future releases and writing code. As most open source work happens virtually, hackfests are great opportunity to meet in person and make a lot of progress on things like planning a new release or a particular issue.

Last year many of the GNOME Foundation sponsor companies sponsored hackfests. They were happy with the outcomes – good conversations, good code, great planning sessions – and at the beginning of this year they were interested in sponsoring more hackfests. So we were tentatively planning for about six hackfests this year. However, when we went to raise funding for the first one, a GTK+ hackfest, we soon found that while companies still thought hackfests were a good idea, but, with a couple of exceptions, they no longer had any budget to help fund them. (The notable exceptions: Intel is funding a GNOME documentation hackfest in June and Igalia wanted to sponsor the GTK+ hackfest that we had to cancel.)

So what do we do?

  1. Find more economical ways to run hackfests. We can plan them close to other events where people might already be, have smaller hackfests, coordinate multiple hackfests at the same time, etc. (It disappointed me that nobody has taken Nokia up on their offer to host related hackfests at the Danish Mozilla/Maemo Weekend.)
  2. Find additional funding sources. There are many types of funding out there, some of them easier than others to acquire. For example, there are grants, which might take us a while but could provide substantial funding. There is individual support. The Free Software Foundation is primarily funded by individuals that believe in their cause, not companies. At $10/month, they have enough individual sponsors to support a much larger organization than the GNOME Foundation. So we can and should encourage GNOME users and supporters to sign up for Friends of GNOME.
  3. Find other ways to accomplish what hackfests do. While there is no substitute for face to face conversation, some of the work can be accomplished by virtual hackfests, dedicated hack days, setting goals and milestones, …

Other ideas? Thoughts?

What would you say about the State of GNOME?

Against my dad's best advice, I'm going to admit that I don't feel like I'm the best person to give a "State of GNOME" talk. I mean, it's an open source project. I don't run it, I don't manage it and people not only don't ask me for permission to do things, they don't make a point of making sure I know everything. And that's good! I find out most of my GNOME news the way everyone else does – through blogs, mailing lists and wiki's. We are an effective open source software project and communication is good. That said, I'm happy to help spread the word of all the good things GNOME is up to. (And if you'd like to help too, please join the GNOME Marketing team!)

So, here's what I think I will say about the State of GNOME talk the Collaboration Summit this week. Feel free to add points in the comments or point me to more info. (If you are going to be at the Collaboration Summit and would like to help give this presentation as a member of GNOME or help with QA, let me know!)

The GNOME desktop is alive and well. Despite rumors that everyone and everything is moving to the browser, the desktop is here to stay.

It is true that the desktop is evolving. People are using their desktop differently. You have netbooks, smartphones, multiple desktops, online apps, … so what people expect and need out of their desktop is now different. (And to be honest, most users don't care about their desktop. They care about their email or their social network or the app they use for work. And the desktop or their phone or their netbook just gets them there. You care a little bit, like you care what kind of shoes you wear or what kind of car you drive, but most of the time, you just want it to work painlessly and easily.)

Luckily there are a lot of people who think about the desktop a lot. They make sure it works really well for all the others that just need it to access their stuff. Who are these people? Volunteers, free software lovers, passionate developers, translators and designers determined to make technology accessible to all.

The GNOME community has 2000+ contributors. 400 of those are members of the GNOME Foundation. 300-500 come together every year for GUADEC. 40% of them are paid to work on GNOME, the other 60% do it on their own time. The 40% are paid by lots of different companies. These 20 sponsor the GNOME Foundation – the list continues to grow and there are companies outside of this list that hire GNOME developers.

All these people the community รขโ‚ฌโ€œ
contributors and users alike รขโ‚ฌโ€œ as well as the companies, have
a shared mission and values. Although the GNOME mission is articulated in many different ways by different people, it's basically to provide a free and open desktop platform for the world, accessible to all regardless of ability, financial resources or nationality. And by desktop, I mean your interface to your technology. GNOME also applies to netbooks and smartphones.

The values of the GNOME community have been clearly defined and articulated over time:

  • Accessibility. I've had a chance to work a bit with the a11y folks lately – they're a great team.
    Accessibility means making sure the technology you have works for you,
    regardless of whether you can hear the beeps that you have new mail
    (maybe it flashes at you instead), regardless of whether you can read
    that size 8 font document someone sent you (what were they thinking? –
    at least you can easily magnify it), regardless even if you can double
    click your mouse.  And much, much more. They have screencasts online. We're going to have 2-3 summer interns from HFOSS working on GNOME a11y this summer.

  • Internationalized. GNOME is internationalized into many, many languages and the number grows – daily it seems. Recently the GNOME board was contacted by someone from Nigeria who wanted someone from GNOME to go speak at an open source conference in Nigeria. I have to admit that we (especially me) were skeptical at first but it turns out they even have a GNOME Users Group in Nigeria that's been translating GNOME!

  • Easy to use. A lot of what you see in GNOME 3.0 is intended to make GNOME easier to use. GNOME also places importance on making smart default choices for the user.

  • Beauty. Beauty as in look good but also as in function well, elegantly, simply.

  • Working well with companies. GNOME has a long tradition of working well with companies and has developed things like 6 month release cycles and the GNOME Foundation Advisory Board to maintain those working relationships.

  • Having fun!

GNOME 3.0. A state of GNOME talk would not be complete without mentioning GNOME 3.0! We announced GNOME 3.0 last week. Actually it was announced at GUADEC last summer but there's been a lot of activity kicked off last week by the release team. (And you can read the whole account on the Planning for 3.0 website.)

In the Planning document, the release team first addresses vision – GNOME 3.0 needs an overall vision for the entire GNOME project. "What we are missing is people blessing one specific vision and making
it official, giving goals to the community so we can all work together
in the same direction." These days GNOME includes not "just" the desktop but a lot of applications. We need a vision and a direction for the entire GNOME project.

They called out 3 areas of focus for GNOME 3.0:

  • User Experience
  • Streamlining of the Platform
  • Promotion of GNOME

On the user experience side they focused on two projects:

  • GNOME Shell is a new way of managing your panels, launching applications, finding documents, etc.
  • Document management. GNOME Zeitgeist is a new way of finding documents. The days of carefully storing documents into organized folders are over for most people. Zeitgeist adds most recently opened, tags, comments, location, etc to help you find your data.

On the steam lining side of things, the release team is working on deprecating old stuff in an organized fashion while adding new technologies like Clutter and support more languages like Javascript.

Promotion is primarily marketing. Promoting GNOME, attracting new developers, highlighting applications (I'd guess that most people don't think of applications when they think of GNOME), launching a much needed redesigned website.

Other changes the release team called out as worth mentioning:

  • Desktop Testing which was launched recently.
  • Art/Design. There's been lots of work on theming (like at the GTK+ Theming Hackfest) and we hope to have good collaboration between developers and designers.
  • People and social networking. A lot of work has gone into the telepathy framework enabling interaction not only between people and apps but between people.
  • Mobile:
    the GNOME Mobile platform was first introduced in GNOME 2.24 and since then a lot of the work GNOME developers have done has been towards making desktop technologies function well in the mobile space – devices with small screens, limited processing or alternate input methods like touch screens.

So come join us in developing the future of the desktop. We need everyone from coders to designers, from testers to writers, from promoters to users.

What would you add to the State of GNOME?

Open source enables companies to collaborate

Dave Neary gave me his speaking slot at OSiM USA. I have two challenges, make a talk to fit his title and abstract (although you can almost always safely ignore the abstract) and give a good talk in 20 minutes of time. Here are some thoughts I have. (The title of the talk is Increasing Ecosystem Collaboration through Open Source but I'll let Dave blog that talk.)

Open source software has proved that collaboration between individuals, regardless of geography, time and management structures, can work really well. The open source software model works:

  1. Self motivated. Open source software developers get things done. They don't need to be reminded of what's important or how much work they should be doing.
  2. No management. There are no managers in open source software. There are leaders but people don't work for a manager who tells them what they need to work on first. (A friend of mine once worked all weekend on a customer problem only to have his manager tell him on Monday that if he was going to work all weekend there were other things he should have been working on!)
  3. No time clock. Nobody cares if it took someone 10 minutes or 10 hours to write that patch. They just care if it works and when they can get it.
  4. No performance reviews. There's lots of peer review and lots of feedback – perhaps more than anyone wants – but there are no annual performance reviews tied to raises and promotions.
  5. Fast. While it may not always seem so, things get done very quickly in the open source model. Someone has a good idea and they just do it.
  6. Bad ideas die. On the other hand, bad ideas just die. Nobody keeps pushing for them – or if they do, they can't get other people to waste their time on it.
  7. Evolves. Ideas and projects in open source software evolve as the world changes and new people join the project. (And nobody is paying big money to keep it the same.)
  8. Work gets done. Even without anyone telling them how to do it and what to do, work just gets done.
  9. Communication is great. While it may not always be friendly, communication in an open source software project is great. Everyone knows who is doing what, what decisions have been made and everything is publicly disclosed and documented. In a completely virtual and global environment. If communication isn't great, the project usually doesn't last.

Some companies have figured out how to work well with open source software. Now we need companies to figure out how to work together in an open source way. While some companies have figured out how to work together, either through consortia or through their employees that work on the same open source software projects, others are still figuring out how to collaborate and still keep a competitive advantage. Open source enables companies to collaborate.

Take GNOME Mobile. Many companies are working together, producing very different products, all built on GNOME technologies that are being adapted to new mobile devices. They collaborate on the technologies. On their ideas. And avoid reinventing the wheel. Not only are they using existing GNOME technologies, but the changes they add to make it work well in a mobile environment (whether it's netbooks, scientific devices or phones) and can be used by others who share the burden of maintaining and developing it. Without losing their competitive edge.

So how can companies get involved and cooperate with other companies effectively?

  • Join any consortia or group related to your project, like GNOME Mobile and the GNOME Foundation. This is a good first step as it enables you to meet all the players and often you can find friendly mentors and people to help. Sometimes this is as easy as joining a mailing list. Other times it means paying a membership fee or going to an in person meeting or a conference.
  • Join the discussion. Join the mailing list, irc channel, comment on blogs. Listen and participate. Become part of the community. (You might want to do this before you officially join.)
  • Hire developers or contract companies. Open source software works because lots of people work on it. You'll get a lot of good stuff for free, and people will be glad you are using it, but you'll want to have some technical resources to fix a particular bug, add a specific feature or adapt the open source technology for your product.
  • Use the software! Use the open source software out there. By using it, asking questions, suggesting changes, you'll become part of the community.
  • Let people know you are using it. Several of the products using GNOME Mobile technologies have never told us. We've "discovered" them. We'd be more than happy to work with them.

Any other things companies can do? (As people who have seen my more recent talks can attest, I use the ideas people leave in comments. Thanks!)

5 types of company open source relationships

Companies and communities is a topic I'll speaking on at SCALE. I welcome any feedback or points to consider!

First off, there is no ideal company/community relationship. There are lots of different types of relationships between companies and the communities they work with (or don't work with) – and no one way is perfect for everyone.

The goal should be for companies and individuals who use and support open source software to work effectively together. And part of working effectively together means making sure that the open source model is sustainable. Which means interacting for the good of the project, not just taking or using open source software.

However, how best to interact with the community is a question that many companies struggle with.

It's easy to give companies some general advice: be transparent, let
your employees contribute, talk about what you are doing, … but a
good advice has to take into account what the company is trying to do
with open source software.

In this post, I just want to enumerate some of the types of companies that interact with open source software.

I'll use some of the companies in the GNOME communities as an example because I think GNOME has good, strong ties with the companies in its community.

I can define the following types of companies. There is some overlap between categories.

1. Companies that just use open source software products. These are companies that use GNOME software in their company, say as their desktop or as their image editing software. People use GNOME and they are part of our community whether we talk to them regularly or not. They test the software, do word of mouth marketing, and add credibility to the project among other things. I wrote a whole article about The Role of Consumers Within an Open Source Community. You could argue that a company full of users might have more responsibility to the project than just an average user. And some do. We sometimes get financial support, great case studies and references from companies that use GNOME.

2. Companies that distribute GNOME. In the case of GNOME, some of these are obvious, like all the Linux distributions. Others are not so obvious, like devices or phones that contain GNOME technology. There are also several categories, those that modify the open source software product and those that don't. In the case of GNOME, I think many of our distributors modify it before they ship it. These companies bring some obvious benefits like developers working on the project, fixing bugs and adding features. They also bring some less obvious benefits like ties to end users, marketing, and financial support. The best companies figure out how best to "work upstream." Working upstream means working close to the project, getting your fixes and contributions accepted and into the main branch. For many companies, that is really hard. They often have to make a lot of fixes to make a product acceptable for their solution or their customers and by the time they have time to check it in upstream, they're a version behind and the project doesn't want it. The best companies figure out ways to minimize that time warp.

3. Products built on or with open source technologies. These are companies that build products like Nokia tablets, Garmin GPS units or Supersonic Imagine (the breast cancer scanner). Some fall more into the user category than the distributor category (although they do both.) They need to make sure their developers establish relationships with the community, at the same time they make sure that their companies also establish a good reputation for being supportive of the open source software products they use.

4. Creators of open source software products. There are more of these than you'd think and they fall into lots of different subcategories. Products like Banshee where the key developers work at Novell or products like Maemo started by Nokia but working on creating an external community. These companies need to decide whether they want an external community, an independent community or if they just need an open process for their project.

5. Services. Companies offering services or contract development work around an open source software product. In the GNOME community these are companies like Fluendo, Openismus and Codethink. These companies often have strong community ties because they hire contributors or their employees quickly become contributors.

Any other types?

GNOME Mobile: bringing the desktop and the internet together

Scan0001
I could go the cliche route: the world is changing.

I could go the proverbial route: we're the proverbial frog in the pot being boiled alive.

Or I could just try to explain what I see.

The browser, the internet and the desktop are merging, and while I think we'll work it out eventually, I think we need to work hard to make sure we work it out with a free and open source solution first. (We need to solve the problem before Apple or Microsoft and make sure our solution is a great one!)

Actually I think the internet has already changed everything and the browser has been playing the go between between the internet and the desktop for a long time now.

Mozilla has been working on bringing the internet to users and because of them users know what this new use model can look like – they've tasted what it's like to have seamless integration between at least the browser on your desktop and the application.

GNOME is working on it. Partially with GNOME Mobile and partially with GNOME 3.0.

While most people outside of GNOME Mobile probably think of cell phones when they think of mobile, GNOME Mobile is really about making the desktop fit the new form factors (phones, netbooks, devices, …) and making it work well with a non traditional user interface. And more often than not the nontraditional user interface is a small screen connecting the user to the internet.

In PCMag Tim Bajarin says:

To stay competitive, Microsoft
will need to adapt the core OS to make it desirable for use in all
devices in the home. The company's edge could be in the way it designs
future operating systems,
making devices talk to each other in ways that deliver powerful
networking and integrated communications. Those features will become
more important to a connected home of the future.


I'm glad that Linux and GNOME have already been doing this for a number of years.

Now I think the next step is not making them talk together but making the parts into one seamless user experience. The average iPhone user probably doesn't think about maps as an application on their phone, a browser and some data out there somewhere. It's just maps. It's there on their phone when they need it. If they have a big server in their home, they're not going to want to worry where dad stashed the movies on the hard drive, they just want to see the movies they have, with all the data about each movie and actor pulled from the internet.

A smartphone user no longer really cares about their operating system, they care about what the phone can do, what apps they can put on it. So it's up to us, those building the operating system, desktop, and applications to make sure they all work together to make applications users want.

So why am I harping on this? Because I see lots of work going into the desktop. I see lots of work going into the browser. I see lots of work going into the apps. But I don't see lots of requests coming from application developers to the GNOME Mobile team. Or lots of conversations happening between different application developers, desktop developers and browser developers.

PurpleslogWe provide GNOME Mobile as building blocks for mobile devices but it won't meet users' needs unless there's more interaction and more conversation between the device manufacturers, GNOME Mobile, the browser developers and the application developers.

Like I said yesterday, it's important we understand the new user model and develop for it.

So come join the conversation. GNOME Mobile is one place. Bringing the power of the desktop to devices of all shapes and sizes.

The GNOME Online Desktop project is another. They are working on bringing internet apps and data to the traditional desktop.

Please feel free to suggest others.

Frog in a pot picture by purpleslog.

What do I do as Executive Director of GNOME?

I get asked a lot what I do, exactly, as executive director of the GNOME Foundation.

First off, I want to say I’m really glad I work for an organization where people feel comfortable asking “what do you do?” It shows they care about the organization and are not afraid to ask tough questions. Have you ever asked your boss what they did, exactly?

Secondly, I have to admit that when I first got asked, that first day on the job at GUADEC, I wanted to go “I don’t know!! What do you think I should be doing?” (I did ask the “What do you think I should be doing part” of a few people and I’m always interested in hearing anyone’s answer to that question.)

Ok, so to the point, what do I do? I’m going to answer in three parts.

  • First, the things I think I should be doing, the things I was hired to do.
  • Second, a sampling of what I worked on in the past week.
  • Third, a whole list of things I think need to be done and I’d like to work on.

My “Job Description”

Here’s a picture I drew a long time ago about how I see my job:
Myjob

(Obviously I was not hired for my artistic talents, great as they are!)

I think of my job as having five parts.

  1. One is to be the eyes and ears for GNOME. Part of it is just to be the person that people can come to, not so much as a representative of the community, but as the interface for the community–a single point of contact as well as someone who attends conferences and does things like this to promote awareness of GNOME.
  2. Fundraising. This has two parts.
    First is working closely with our sponsors. The GNOME Foundation is funded by donations from volunteers as well as large donations from our corporate sponsors. Part of my job is finding new ones and working closely with existing ones to make sure that their relationship with GNOME is a good one and that the Foundation offers what they need.
    The second is finding new fundraising opportunities. Like our recently launched Friends of GNOME that enables you to sign up for small monthly donations. (That wasn’t just my idea by the way. I’m glad we have it – the FSF’s program is extremely successful. If our community can duplicate that success, you will see the GNOME Foundation grow tremendously. So sign up and spread the word!)
  3. Along with that comes marketing. We have a marketing team, but part of my job is to figure out what we want to do with GNOME marketing and help set up the infrastructure so that people can help work on marketing. Check out my lists below – there’s lots of marketing stuff on it.
  4. Business development. What opportunities should we be pushing for, what should we be watching for, where could we make a move? This is why I’m involved in GNOME Mobile. There’s a huge opportunity for GNOME in the mobile space and we have to act now. I also think we need to take a more aggressive stand. Aggressive is not the right word. Perhaps holistic. We have to stand for free and open source on the mobile platform – not just pieces of it but everything people need – like we do on the desktop.
  5. Housekeeping. (That’s the broom in the picture, by the way.) Part of my job is helping to make sure the day-to-day stuff happens. We have a lot of things going on in GNOME with lots of people working on multiple projects and lots of ideas floating around. One of my jobs is to help make sure good ideas get done and have the resources they need. That’s pretty much what I did with Friends of GNOME. The idea was there, people were willing to work on it, I just pushed a bit. (Luckily we also have Rosanna!)

A sampling of what I do (work-wise that is)

Here’s some of the things I’ve done in the past week:

  • Emailed each of our corporate sponsors with an estimate of money we’ll be requesting from them in 2009. Asked how and when they’d like to receive requests for invoices and if they had any suggestions about the plan.
  • Had the GNOME Advisory Board meeting. We did a roundtable and asked what people were working on in GNOME in 2009.
  • Helped launch Friends of GNOME. Yeah! (Have you signed up yet?) Sent out email to all the press people I know to let them know about it.
  • Talked to a company who would like to sponsor the GNOME Foundation. They invited me to meet with their architectural committee and asked for the brochure. (Added that to my marketing wish/todo list.)
  • Worked on the Desktop Summit sponsor brochure with a couple of the KDE folks. Figured out who was going to approach which companies about sponsoring the Summit/GUADEC/Akademy.
  • Set up meetings for next week with most of our corporate sponsors to touch base and get their feedback. (Still have a few meetings to set up.)
  • Gave a talk at the Denver JUG. The talk wasn’t about GNOME but I saw it as a chance to spread the word about open source, enabling open source fans to use more in their companies. Also put in a plug for Friends of GNOME and got to explain to quite a few people what GNOME was exactly. (Did I mention we need some more marketing?) I spent quite a bit of time preparing the talk – I very much believe if you are going to use an hour of 40 peoples’ time, you should use it well.
  • Had a call with the KDE and GNOME boards about how we are handling the finances for the Desktop Summit. Got our attorney to review the written draft.
  • Spent a few minutes thinking about what I would like to see in the desktop/netbook track of the OpenSource World conference. (I’m organizing the desktop/netbook track. Let me know if you have good ideas for speakers, including yourself.)
  • Joined the GNOME accessibility team meeting to talk about what our two interns in the FOSS Humanitarian program will work on this summer.
  • Exchanged an email about the MBA/marketing/business development internship program I’d like to get started.
  • Read, answered, participated in an incredible amount of email, IMs, Twits and IRC chats. (And I think these are an important part of getting my job done, so I try never to complain about having too much email because I wouldn’t really want less. I just try to be as effective as possible with my communications.)

Things I’d like to see get done (by me or others)

I’m not going to elaborate on them since each one could be a post (or set of posts) all in themselves.

  • GNOME Marketing 2009 goals – a list of all the marketing stuff we’d like to do but more importantly clear goals and priorities.
  • A marketing/business development internship program. We have interns that write code, why not interns that help with marketing tasks?
  • GNOME Foundation sponsorship brochure for corporate sponsors.
  • A GNOME merchandise store.
  • Storyboards and slides. Lots of different slides that lots of different people could use to talk about GNOME in different ways and different venues.
  • Fundraising contacts. I’m trying to reach out to more of the mobile and netbook vendors.
  • Fundraising “marketing”. How do we spread the word, use social networks, get ads, etc?
  • Usability study. I mention it a lot, other people mention it a lot. I did exchange email this week with a usability company that might be willing to help us out at a greatly reduced cost if we share results and publicity.
  • System administrator. We’d love to hire a part time system administrator. We need a few more regular corporate sponsors to feel comfortable with this. (Or more committed income from the sponsors we have.)
  • Setting up a SugarCRM-like system to track Foundation stuff. (Dave Neary got SugarCRM to agree to give us a free account which is why I mention them.)
  • Making sure we are on the right track with GNOME Mobile.
  • ….

So, that is what I do as executive director of the GNOME Foundation. What would you like to see me do?

A walk down memory lane … with GNOME and Stormy

I ran across the GNOME Advisory Board Minutes from June 2003, back when I was on the advisory board representing HP:

Stormy Peters did a presentation about her work on the Open Source
Program Office at HP, policy, review for releases, and the OSS portal.
The Foundation provides:
- a bridge between community and the users
- credibility
- product management
- communication, especially roadmap
which are the main values from a corporate perspective.
Stormy devoted a significant portion of her presentation to the role
of the advisory board. She says that the advisory board could contribute
more to the GNOME project and could be more helpful to the foundation.
She urged us to make better use of the advisory board, and of her
resources in particular.

Well, the GNOME Foundation is certainly making better use of my resources now! We could still do something about that roadmap though.

Advisory board members often ask for the GNOME roadmap. (Or the GTK+ roadmap or the you name it roadmap it.) They need it to make their plans. They need it to explain to their management and their peers what GNOME is up to. I think even if we didn't have concrete dates on the roadmap, we could still create one. The idea is to show where you're going, not necessarily all the fine detail of how you'll get there.

For example, recently someone contacted us for a list of GNOME goals for 2009. I was getting ready to jump in with some high level, vague answer when Vincent Untz jumped in with this great list of things that might happen in 2009. I went wow, where'd you get that from? To which he responded, in typical Vincent fashion, that it was only in the heads of crazy people who try to follow everything. (And I am very, very impressed with how much crazy people like Vincent follow, keep track of and know. ๐Ÿ˜‰

But what if we created a GNOME technologies roadmap of all the crazy things that might happen in 2009-2010? Then we could color code it with likelihood of happening and update it a few times a year. We could also mark who was working on what, what areas needed help, …

GNOME Advisory Board Meetings

Every month we have GNOME advisory board meetings that are designed to bring our sponsors and our community closer together – to open up channels of communication. The topics so far have covered things from usability to GTK+ 3.0 to finances. There's usually a short presentation by the team and then there's time for discussion.

From the advisory board members it's a chance to hear in more detail what the GNOME community is doing, as well as the other advisory board members, and to give feedback. In addition, since we invite the appropriate community members or additional people from advisory board companies, it's a chance to meet the experts in the community.

From the community perspective the meetings are a chance to show off their project, get feedback from downstream users and make sure that sponsors know about their project.

The meetings are held the second Wednesday of every month. This month we'll be holding it a week late (this Wednesday) and we'll be talking about upstream, downstream relationships.

If you have any topics you'd like to see covered, please let me know. We're especially interested in hearing from community members who'd like to share their project with the advisory board members.