How Apache *really* works

How much do you know about the Apache Software Foundation (ASF) and the many Apache projects we host? Did you know we’re holding our annual Members meeting to elect our board of directors and new Members in just a few days?

I’m often surprised by the variety of basic questions and misunderstandings I hear in the software world about how the ASF really works. We’ve written plenty of documentation about the Apache Way and our governance, but let’s try a different approach. I’d like to interview myself to try to explain some things.

So, Shane, what *is* Apache? I thought it was that web server?

The ASF is a non-profit, public charity, 501(c)3 membership corporation with the mission of producing software for the public good. The Apache HTTP Server project (to use it’s formal name) is a project community at the ASF that creates the httpd web server, which has powered more active websites than any other server since 2000.

The ASF is the corporation that provides legal, branding, press, fundraising, and infrastructure support, and proven community mentoring to the many Apache projects like the HTTP Server. Think of the ASF as a great big house, where we provide shelter for a lot of different families that write open source software.

Well how many Apache projects are there?

We have over 165 different projects, and about 40 podlings. These 200+ project communities create a wide variety of software products, including Apache Hadoop, Apache Lucene, Apache OpenOffice, Apache CloudStack, and many, many more.

You are almost certainly using multiple Apache products right now as you read this. You may not realize it, but much of the plumbing of the internet uses Apache software to keep servers organized and connected. Most browsers use various Apache products under the hood for a wide variety of utility functions. It is our project communities that actually create the software you’re using — the ASF just helps keep them organized.

How does the ASF organize all these projects?

The ASF provides all the infrastructure an open source project needs: websites, code repositories, mailing lists, bugtracking services, a crack infrastructure team. We also provide all the rest of the services that a project will want, like legal support, access to press releases or analyst contacts, and some fundraising support. The ASF also owns all Apache trademarks on behalf of our projects, to ensure they get the credit they deserve.

Most importantly, the Apache Membership and many of our 4,000+ Apache committers provide the community mentoring and support to keep our projects running smoothly, with an independent project governance. We have many passionate Members with amazing experience in making open souce projects work, and they volunteer to help keep our projects healthy and running strong.

But this is mentoring and guidance, not direction. The ASF does not direct the technical direction of our projects. We let the people doing the work — the project committers and Project Management Committees (PMCs) decide where the code should go.

So the projects direct themselves. But what is “independent project governance“? How do you enforce it?

A critical behavior for any Apache project is independent governance. That means that every project manages their code for the benefit of all users (the public good), and not just for some company or vendor. In particular, the ASF and Apache projects only recognize individuals as committers or Members — never companies.

We expect when committers are working within their Apache project, they are acting for the best interests of the project itself. But we also have checks and balances: all Apache projects report formally to the board of directors quarterly. The board reviews project health — are they acting indepenently, are they publishing software releases, are they voting in new committers. If the board sees behavior that does not show mature Apache project behavior, the board will work within that project community to help the project community correct itself. Many Apache Members also volunteer to mentor our projects in these cases. In extreme cases (very rare), where a project does not follow the Apache Way, the board will unilaterally make changes to correct their course.

Can you clarify who are the board, the Members, and how they relate to projects? Are Members part of all projects?

Imagine Apache as a condominium association with multiple condos together. The ASF as a corporation provides the building. Like some condo associations, we also define a few expected behaviors and appearances for all the condos we offer. We also offer bonus services, like help moving into your condo or fixing things up. Each Apache project lives in one of these condos. We’re happy for you, the project community, to live your own lifestyle within your condo and paint the inside whatever color you want, as long as your public behaviors when you’re here follow our community best practices.

Here, the Apache board is the board of the condo association. They set the core rules and guidelines for the building. The Membership are sort of the owners of the building — not that they can ever sell their shares or make a profit, but they are the only ones who can nominate and elect the board. The board appoints all the officers who set detailed policies and make all the operations of the building work, like trash pickup and elevator maintenance.

Every Apache project condo has at least one Apache Member involved with the community: the Incubator requires that every new project has a few Members interested in that community to help mentor it. But within each project condo, the code direction or decor choice is completely up to the whole project community to decide. Membership in Apache is not transitive to any project: Members need to be elected to your project to have a direct say in it.

The ASF offers a lot of services to projects. How does this all get paid for?

The ASF board approves an annual corporate budget of about one million dollars. Our primary income is from our formal Sponsorship program, where organizations can provide a regular annual donation. As a 501(c)3 charity, we also have many individual donors, and some authors donate royalties from their books about Apache software to the ASF.

Importantly, sponsorship of the ASF does not provide any influence over Apache operations nor the operations of any projects. The ASF’s mission is to serve the public good, and while we very much appreciate our generous sponsors, we do not serve them: we serve our project communities and software users.

Sponsors provide a variety of reasons why they sponsor the ASF, many of which relate to how we host so many different critical software product communities. As one sponsor said, “Apache builds the plumbing of the internet”. Some sponsors and donors simply want to give back to the ASF in appreciation for all the software we provide for free.

So the Sponsors can pay for Apache project development, interesting.

No! Sponsorship funds are purely undirected — we do not accept donations with ties or requirements. By policy, the ASF does not pay for core development on any Apache project. All our budget is used for the support services that allow our project communities to do their work — which is building Apache software.

Do any Apache committers get paid for their work?

Of course — but not by the ASF. Many committers are working on Apache projects on behalf of their employers, who may be software vendors providing support, hosting, or add on products for that Apache project. Some committers are independent consultants, trainers, authors, or the like, who make their own living from helping other people use Apache projects. And a lot of committer work is done simply because that person needs to fix a bug or add a feature that they need for themselves. With so many people using Apache software to run their businesses, most work is self-serving: building code that they need.

The ASF provides a vendor-neutral place where everyone who benefits from Apache software can collaborate to improve that software. The ASF does not have an agenda or direction — we rely on the people using our software to help improve it.

Well… how much do *you* get paid at Apache?

Nothing.

No, seriously — how much do you get paid for this?

Seriously: nothing. Zero. Zip. The ASF has never paid me for my work here, and my current dayjob is wholly unrelated to my Apache activities. I’m here purely as an unpaid volunteer.

How did you get to be at Apache? What drives you to do all this unpaid work?

I first started committing code to the newly formed Apache Xalan project shortly after the ASF was incorporated in November 1999. At that time, I was paid by Lotus/IBM, my employer, to contribute to the Xalan as part of my job. I also got to attend and speak at a few ApacheCons to try to promote our work on Xalan and Xerces.

Over time, my dayjob changed direction, and turned away from Apache, but I was still interested in how the ASF worked. At ApacheCon I had followed a friend into a conference planning meeting to see how it worked, and I walked out of the meeting with assigned tasks for the next ApacheCon. Once I started helping with events, I was hooked. In 2002 I was elected as a Member of the ASF, and got to see how the sausage was made from the inside. In 2004 my job changed to be wholly unrelated to any open source work, but I was already personally invested in the ASF and our many excellent communities.

I volunteer at Apache for several reasons:

  • This is how I give back to the world. I’m lucky enough to have a healthy family, nice home, and stable job. I volunteer my extra time to help make it easier for Apache project communities to build more free software for the public good.
  • I love the ASF and it’s people. I’ve met so many amazing people at ApacheCon and within our projects, and it feels like much of the Apache Membership is one big family. Sure, we fight plenty, but we also buy each other plenty of free beers and meals.
    Helping open source communities get organized and keep their volunteers motivated is something I’m good at, and something I’d love to do more of if I could. Volunteering at Apache is a huge impact to my personal brand and my future job prospects.

Wow, that’s been a great interview Shane! How should we wrap this up?
It’s been a pleasure. Thinking about what motivates me, this is one of the things I love doing: explaining technology and communities to interested audiences. This is also great timing for this interview, because the ASF is having it’s annual corporate meeting where the Membership elects a new board.

We have a truly stellar list of director nominees this year: looking at the candidates the Membership has nominated shows just how talented and friendly all our candidates are, and how any of them would be a help to ensuring the smooth operations of the ASF in the year ahead.

Since I do have the microphone, I will make one short plug to note that I’m also running for a seat on the board. I’ll be posting my director nomination statement — a note detailing why I hope Members will vote for me — soon here on my open source blog, Community Over Code.

Good luck with the election Shane — it sounds like Apache is in good hands no matter who gets on the board.

Yup. While we still have a way to go to make it simple to understand Apache for newcomers, the ASF and our project communities are doing amazing work, and often having a lot of fun doing it. Apache plans to be around for the next 50 years providing a stable home for like-minded project communities of all sorts.

Thanks for the interview — this was great to talk to someone about this!

Shane volunteers as the Vice President of Brand Management for the ASF, although all content here is his own personal opinion. He is not normally an interviewer, but does sometimes play a trademark lawyer on the internet. He hopes you liked this article, which also appears on Medium, and will ask him any questions about Apache that you might have. He promises to stop writing in the third person now.

Three key elements defining any open source project

Open source has come a long way in the past 30 years and is entering the consciousness of most modern cultures. When thinking of open source projects, people categorize them several ways: governance structure, type of product platform, programming language, utility, technical details (language written in), industry sponsored or fully independent, and more.

But what truly defines any open source project, making it a unique entity different from all other open source projects? I would propose that there are three key elements of any open source project that frame, define, and differentiate that project from all others: the code, the community, and the brand.

Continue reading Three key elements defining any open source project

It’s Groovy to join a Foundation

The contributors behind the awesome Groovy project are looking for a new home. It’s bad news that the project and some of its core contributors will no longer be sponsored (paid for) by Pivotal, but it’s great that the core contributors are organized and serious about moving their project to an existing Foundation.

As a long time Apache Member (among other things), I have a few suggestions for the Groovy community.

Continue reading It’s Groovy to join a Foundation

So, I gave this talk at OSCON

So, it was short, but an important message that I don’t think many open source project participants are really thinking through yet. So, it was all about how BRAND > CODE, and I’m looking for feedback on how to expand this, so, into a much bigger and better talk.

OSCON Ignite 2014: BRAND > CODE, by Shane Curcuru

So, you have to understand: yes, watching the video is so painful. I’m not usually that so-so. It was a combination of nerves (bigger stage than expected), jetlag, E_NOTENOUGH_PREPTIME, and the fact that my cell phone had just taken a dip in the water a few hours earlier.

OSCON was awesome, by the way. Next year looking forward to making sure my travel plans include the Community Leadership Summit!

I use Slideshare, and I speak at ApacheCon on managing community brands and making profits while respecting brands.

Congratulations to the 2014 Apache Board of Directors

The ASF recently held it’s Annual Member’s Meeting where all Members of the Foundation cast ballots in the annual election for the Board. We are lucky to have had a number of excellent candidates for the board as always.

The new board comprises:

  • Rich Bowen
  • Doug Cutting
  • Bertrand Delacretaz
  • Ross Gardler
  • Jim Jagielski
  • Chris Mattmann
  • Brett Porter (chairman)
  • Sam Ruby
  • Greg Stein

I also keep a graphical history of the ASF board.

As the ASF grows in projects, communities, and Members, we’re looking forward to continuing to support our now 151 top level Apache projects going forward!

Shane’s Apache Director Position Statement 2014

The ASF is holding it’s Annual Member’s Meeting next week, where the Membership elects a new board of directors along with other matters, like voting in new Member candidates. Director candidates write position statements about what their objectives for being a director are in preparation for the Apache board election process. One of the biggest issues for the smooth functioning of the ASF as a home for healthy projects is better explaining how Apache works – so here is my Director Position Statement. You can also read my statement last year and the previous year.

I’ve also written an Apache corporate governance overview as well as posted an ASF contributor timeplot and history of past boards.


Shane Curcuru (curcuru) Director Position Statement 2014

v1.0 statement

Over the past couple of years, the ASF has grown to a point where we can no longer efficiently continue to govern, manage, and execute the various operational aspects of the Foundation in support of our nearly 200 project & podling communities with only unpaid volunteers. We need a board that can maintain our fiercely vendor-neutral governance while also expanding and improving the services that we offer to all Apache projects, and this will require finding ways to increase our paid staff [1].

While the volunteer membership has been amazing throughout our history in helping with governance, mentoring, incubation, and all other aspects of operations, we simply don’t have enough members with time reliably available to provide this level of operational support. With 150+ separate Apache top level projects – each with its own technology, individual community history, and sometimes urgent pace of development — the overall cohesion that marked the earlier years of the Apache organization has been jeopardized. It’s clear from recent requests and issues that we are not providing the level of support – infra, brand/press, fundraising, and community mentoring – that many of our projects expect and require.

With the growth in key project technologies that affect the larger world, we also have a corresponding higher level of expectations from stakeholders outside of the ASF volunteer community. Our sponsors – when we do talk to them about their sponsorships – want us to be more visible in the open source space and show more support to our projects. The many vendors whose employees work on our projects similarly want to be more involved with donations, servers, events, or branding efforts around our projects. Ensuring that this external energy is focused on the Apache project in ways that maintain an independent project governance is critical to the success of both our projects and to the ASF itself.

We need to provide a better API between individual project communities and our service providers (infra, press, brand, legal, fundraising) at the Foundation level. We need to ensure that projects are aware of the services we can provide to support their operations, and make it simple for them to utilize those services. Clear expectations should be set for the level of services that the ASF will provide, as well as governance assistance for those projects that will continue to use external service providers (eg, various marketing@ efforts and many projects’ externally run build/CI/test farms).

To meet the current services needs, and to support increased quality in our governance and operations, the ASF will need to increase our number of paid staff [1]. We need motivated, experienced, and trusted individuals who have the paid time to address the ever-expanding needs of the Foundation, and who can dedicate themselves and their time at a level that is not possible for an unpaid volunteer.

It is also essential that we scale our management and oversight ability of these services and of staff without losing our soul: without compromising our historically independent and volunteer board and governance structures. I don’t know exactly what this path will be: that will be for the next board to decide. But I do believe we are underserving many of the projects at Apache today, and we have no end in sight of new podlings hoping to join us.

If you also believe we need to better provide for the many Apache project communities that trust us to be their home, I hope you’ll cast your first vote for me. Thanks!

About Shane

Committer since November 1999, Member since 2002, VP Brand Management since 2009.

I am employed by IBM in the HR division as an Applications Architect. My employment and income have been unrelated to my work at the ASF for many years, and I will always clearly separate volunteer work from employer-funded work.

My involvement in the ASF is driven by a belief in, and a love of, the ASF, and is not influenced by politics or finances. I live in Massachusetts with my wife, young daughter, and 2 cats. I view directorships and officer positions at the ASF as serious commitments.

I will attend every board meeting if re-elected.

[1] NOTE: How we pay for staff is equally important: at this point in the ASF’s history, I imagine either independent contractors as infra operates currently, or using the services of our new accounting firm Virtual, Inc. for some sort of co-employment arrangement, to reduce risk to the ASF.

Apache Governance – Projects First

When push comes to shove and full consensus on governance matters at the ASF or at Apache projects isn’t easily found, it’s important to consider what our underlying objectives are. The mission of the ASF is to produce software for the public good. That’s a good start, but like many concise mission statements, it doesn’t tell the whole story.

There are several aspects of how we expect Apache projects to work that we believe are critical to our mission’s success and longevity. These include things like The Apache Way of: volunteer and collaborative led community built software projects; using the permissive Apache license; and having a consistent and stable brand, infrastructure services, and home for all Apache projects.

We – as in the bulk of the Apache membership and especially the directors that we elect to the board (and thus the corporate officers the board appoints to set policy) – believe that these few core organizational and community management principles are so important for our long term mission that we require these behaviors of all Apache projects. Part of having a consistent brand is showing some level of consistent behavior with the products you produce. Having a shared set of infrastructure services likewise simplifies the process for users to find and use our products. Using the permissive Apache license means that we give maximum freedom to the users of our software, meaning that more users are likely to choose it.

But beyond these core principles, ones we have carefully crafted through experience working on Apache projects and have attempted to minimize when prudent, how do we decide where the ASF should go in the future, or what other, more detailed principles might be important to us? While the officers and directors set the official policies of the ASF as an organization, we look to the constructive input of all Apache members when discussing these ideas.

One recurring meme when discussing “What else should the ASF be/do” has been: “Projects first, or Foundation first?” I.e. is the ASF here to serve the needs of our Apache projects, or have Apache projects chosen to come here to follow the direction of the ASF? Should the ASF decide what kinds of projects we want to join, and decide The One True Technology; or should we simply see what projects show up, and try to support them?

If you picture Eclipse, you can see an example of “Foundation first”: the Eclipse board and leadership – mostly through it’s paying corporate sponsors and de facto corporate-led projects – has an overall vision and drive that explicitly provides direction for it’s projects. Eclipse has full-time staff devoted to “…1) IT Infrastructure, 2) IP Management, 3) Development Process, and 4) Ecosystem Development.” Similarly, the Eclipse board is partially made of appointed members from their Strategic Developer and Strategic Consumer corporations. That leads to strong consistency and direction, primarily for the benefit of the corporations directly or indirectly funding Eclipse projects.

“Projects first” means that the ASF exists to serve the needs of any projects who choose to join us, and who willingly agree to follow our basic rules, like using our license, consensus-driven decisions, and running projects independently of corporations. Our mission is not on behalf of the many corporations who pay their employees to donate code to Apache projects. Our mission is to provide software for the public good – that is, the end users of our software, and the larger world around us.

The ASF doesn’t have an agenda beyond that mission. We don’t have a strategic plan for acquiring projects in specific technologies or from specific corporations. We rely on providing a stable and friendly home for like-minded individuals and communities to build software… for the public good. We certainly hope – and time has shown – that this model will attract vibrant communities that will build useful software. There are plenty of Apache Members and Committers who are passionate about sharing their experiences in software development with others, which is great. But as an organization, we don’t have a strategic plan for seeking out new projects: we believe the best process is to let like-minded projects seek us out.

To ensure that Apache projects focus on the public good, we also require our projects to be run independently of undue commercial influence. Apache projects don’t exist to serve as a vehicle for the corporations who may have donated technology or employee developer hours to them – they exist for the broader public good.

This independence is fundamental to the long-term health of our projects, and to the ASF. It both makes the ASF a place where potentially competing corporations can feel comfortable collaborating on technology (which gets us lots of software for our mission) and also seems to attract plenty of individuals who are interested in participating in our projects – even when changing employers. This independence means that an independent Apache project can continue to exist for the benefit of it’s users even if one of the corporations donating technology to it decides to change direction.

But beyond the core requirements here – ones designed to keep project governance in our independent communities – the ASF strives to not add any additional requirements, but rather to provide the best home to like-minded Apache projects that we can. So in that way, we try to remain focused going forward on putting “Projects first”.

Actually, I should amend that. We do have the core project requirements; ones associated with being an Apache project. So I should really say that we put “Apache projects first”. But beyond that Apacheness that the ASF has developed over 13 years and 190 project communities, we strive to not have an agenda – other than to support those Apache project communities who choose to join us as best we can.

People still reading may also be interested in learning how governance at Apache works.

Congratulations Apache Chukwa – the 140th Apache TLP!

Last month, the Apache Chukwa podling passed the Incubator’s graduation vote. At the October Apache board meeting, the directors voted unanimously to create the Apache Chukwa top level project, with responsibility for creating an open source data collection system for monitoring large distributed systems.

While this may seem to be yet another project in the fast-growing constellation of Apache Hadoop-related technologies hosted at the ASF, the important milestone is that this is now the 140th active project at Apache! That is, there are currently one hundred and forty independent project communities, all producing software for the public good, all currently hosted at the ASF. That includes everything from the ubiquitous HTTP Server project, through the widely used Lucene search engine, to the aptly named Rave project, and the admittedly niche-functionality MINA project.

Note that this does not count the 36 separate podlings that are currently in the Apache Incubator – each one is an independent community hoping to grow it’s community (and make some software releases) so that they too can graduate to become an official Apache project.

More importantly, this is not the 140th project that’s ever been at Apache. At Apache, we believe in Community over Code; in that having an active and collaborative community is the most important factor in Apache project governance. However we recognize the immense public good that Apache projects do by providing software, especially source code, under our permissive license.

So what to do when we have an older project that may have lost it’s active community? Well, we put it in the Apache Attic, of course! There are currently 14 projects in the Apache Attic, along with a number of subprojects and other bits of software that are still hopefully useful, but that do not currently have an active community at Apache maintaining them. In that way, we provide the code for anyone who needs it, but warn users not to expect the normal support and releases of a full-fledged Apache project.

Putting that all together, we have a full 190 project communities that have chosen the Apache Software Foundation as their home over the past 14 years. A pretty good footprint for an all-volunteer run organization that started with a handful of geeks emailing code patches around to each other!


There are many places to choose to host your project today. Some people prefer other organizations for their project’s hosting – or simply forgo hosting a “project” and merely look for a place to dump their code. That’s fine, and we respect everyone else’s choices. Some people even go so far as to say that Apache doesn’t get it, or isn’t cool, or other uncomplimentary things. That’s fine too: we can agree to disagree.

If you really don’t see the value in being an Apache project – I mean, not just see the value for yourself (which is completely fine, I don’t care); but if you truly can’t see the value that someone might find in wanting to be an Apache project, then… well, sorry, then I can’t help you at all. You can stop reading now.

Even if you don’t see the value for your project right now in coming to the ASF, I hope that you can see the larger values: longevity, brand protection, stability, strong communities, and collaboration amongst many different groups within our communities. While some of these values may not be exciting for the rockstars out there, they certainly are exciting for the millions of software users out there – both small scale and corporate scale users appreciate using software that seems to have a better chance to be around, and be supported for the longer haul.

And even if you don’t see the value here at Apache, that’s OK. We’ve had 190 other communities of people who do see the value over the past 14 years, and our aim is to be here for another 50+ years to come. We’re happy with what we’re doing – and with the immense public good our many, many freely usable software products we’ve provided to the world.

Congratulations to the 2013 Apache Board of Directors

The ASF recently held it’s Annual Member’s Meeting where all Members of the Foundation cast ballots in the annual election for the Board. I was lucky enough to be elected, so I will be returning to the board, along with new first time Director Chris Mattmann. Everyone also thanked our two outgoing Directors, Rich Bowen and Ross Gardler.

The new board comprises:

  • Shane Curcuru
  • Doug Cutting (chairman)
  • Bertrand Delacretaz
  • Roy T. Fielding
  • Jim Jagielski
  • Chris Mattmann
  • Brett Porter
  • Sam Ruby
  • Greg Stein

I also keep a graphical history of the Apache board.

Shane’s Apache Director Position Statement 2013

The ASF is holding it’s Annual Member’s Meeting this coming week, where the Membership elects a new board of directors along with other matters, like voting in new Member candidates. While I was nominated last year, I was not elected. I would have been sad about not getting a seat, except for the fact that such other fabulously good people got elected instead (including two new directors who got to serve their first terms, Rich and Ross, yay!).

Director candidates at the ASF write position statements about what their objectives for being a director are in preparation for the voting process. Since I write what I believe in, I also am posting my statement here, publicly. One of the biggest issues for the smooth functioning of the ASF as a home for healthy projects is doing a better job of explaining how we work – I hope this helps people understand us Apache types just a little bit better. You can also see what I wrote last year.

If you’re wondering how governance at Apache really works, I’ve written an Apache governance overview too.


Shane Curcuru (curcuru) Director Position Statement

v2.0 statement

As the ASF scales in people, projects, and impact on the world, we
need directors that can ensure our organization stays true to it’s
ideals; that can delegate appropriately and efficiently to officers
and PMCs; and especially that can communicate calmly, clearly,
and consistently in all of their communications.

As we surpass one million $ in assets, with thousands of committers, nearly a gross of projects, and an huge impact both on the software world with our technology, and on the larger world of computer users with our products, I believe it’s important to do an even better job of explaining what the ASF is about and how the Apache Way works.

While we don’t need more rules, we do need to do a much better job of explaining what our few hard requirements are, as well as showcasing the wealth of best practices that our projects have created. This is important both to let the world know who we are, and also to ensure that the many different communities of contributors can more easily understand how to work with our projects.

With the fast growing scale of our organization, it is critical that directors and corporate officers can communicate clearly, calmly, and professionally in all of their Apache related activities – whether or not they’re explicitly showing which hat they’re wearing at the moment. As our impact grows, so does the impact of our words, both inside our communities, attracting (or not) new members to our communities, and also on the larger world of corporations, universities, and other computer using peoples. Even if we as long-time denizens of members@ understand which hat a director or officer is wearing when they speak, most other human beings and most other contributors don’t necessarily see the distinction.

It has been a long time since we held in-person member’s meetings
where everyone knew each others personal style. As we grow,
we need to be sure that we’re making it easy for new members and
contributors to feel welcomed and understand how Apache works. We also need to ensure that we both can keep the sense of family and enjoyable, collaborative community that the membership and our projects have, and that we manage the affairs of the ASF and of our projects in a consistent, documented, and professional manner.

About Shane

I’ve been a committer since November 1999, a Member since 2002,
and VP, Brand Management since 2009.

I am employed by IBM in the HR division as an Applications Architect. My employment and income have been unrelated to my work at the ASF for many years, and I will always clearly separate volunteer work from employer-funded work.

My involvement in the ASF is driven by a belief in, and a love of,
the ASF, and is not influenced by politics or finances. I live in
Massachusetts with my wife, young daughter, and 2 cats. I view
directorships and officer positions at the ASF as serious commitments.

I will attend every board meeting if elected.