What Apache Also Needs In A Board

Some great recent discussions around the upcoming member’s meeting have got me to thinking about the larger question: how can the ASF as an organization function better, and how does the board effect that? I think there is one more important concept in a board that the ASF needs to have, along with oversight and vision.

Continue reading What Apache Also Needs In A Board

Shane’s Apache Director Position Statement, 2017

The ASF is holding it’s annual Member’s Meeting next week to elect a new board and a number of new Members to the ASF.  I’m honored to have been nominated to stand for the board election, and I’m continuing my tradition of publicly posting my vision for Apache each year.

Please read on for my take on what’s important for the ASF’s future…

Continue reading Shane’s Apache Director Position Statement, 2017

What Apache needs in a Board

The ASF is holding it’s annual member’s meeting soon, where we will elect a new 9-member Board of Directors for a one-year term.  I’ve been honored with a nomination to run for the board again, as have a number of other excellent Member candidates.  While I’m writing my nomination statement – my 2016 director statement and earlier ones are posted – I’ve been thinking about what Apache really needs in a board to manage the growth of our projects and to improve our operations.

Continue reading What Apache needs in a Board

Behind the scenes at Apache: Corporate Org Chart

You probably use contribute to several Apache projects.  But do you know what goes on behind the scenes at the ASF?  Besides all the work of the 200+ project communities, the ASF has an annual budget of about one $million USD to fund the services our projects use.  How we manage providing these services – and governing the corporation behind the projects – continues to change and improve.

Continue reading Behind the scenes at Apache: Corporate Org Chart

Who’s Who at Apache: Roles and Responsibilities

There’s a huge amount of volunteer energy that flows around Apache’s Annual Member Meeting every year.  Old members and new alike come together and brainstorm all sorts of new ideas, both organizational and technical – and we have plenty of online… discussions, let us say.  There is an amazing amount of energy from a lot of very smart people, and when we focus  this energy, we make real improvements to the Foundation and sometimes in some of our projects.

As we’ve grown, keeping a full shared understanding of all the details of membership and corporate operations has become much harder.  We have some documentation, but we also still have a lot of tribal knowledge and decisions hidden in our mailing list archives.  To understand the same things, we need to be able to see what rules or policies we’ve actually decided on – or at least written down.

So here is an overview of all the different roles that people can have with the ASF as either a Foundation or with specific Apache projects.  In particular, I’m focusing on the specific agreements we make with individuals, or the explicitly posted policies that we expect people to abide by.  For more information on how Apache works, see /dev, /governance, and Community.

Continue reading Who’s Who at Apache: Roles and Responsibilities

Shane’s Apache Director Position Statement, 2016

The ASF is holding it’s annual Member’s Meeting this week to elect a new board and a number of new Members to the ASF.  I’m honored to have been nominated to stand for the board election, and I’m continuing my tradition of publicly posting my vision for Apache each year.

We are lucky to have both a large involved membership, as well as another excellent slate of candidates including a couple of great new faces. No matter how Apache STeVe ends up computing the results, Apache will have a great board for the year to come.

Please read on for my take on what’s important for the ASF’s future…

Continue reading Shane’s Apache Director Position Statement, 2016

Congratulations to the 2015 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
  • Shane Curcuru
  • Bertrand Delacretaz
  • Jim Jagielski
  • Chris Mattmann
  • David Nalley
  • Brett Porter (chairman)
  • Sam Ruby
  • Greg Stein

I also keep a graphical history of the ASF board.  The graphic there is a great way to see the slow but steady progress of electing new faces to the board over time.  Thanks to all the active Members who voted in the elections!

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

Note that a number of new Apache Member nominees were also elected; however we don’t share their names until they’ve all been contacted and have accepted the invitation.  Stay tuned in a month for that announcement from @TheASF.

Shane’s Apache Director Position Statement 2015

The ASF is holding it’s annual Member’s Meeting this week to elect a new board and a number of new Members to the ASF.  I’m honored to have been nominated to stand for the board election, and I’m continuing my tradition of publicly posting my vision for Apache.

We are lucky to have a large roster of excellent director candidates, so no matter how the election turns out we’ll have a stellar board. Given the wide variety of opinions in our candidates, I urge all Apache members to set aside the time this week to carefully consider all the board candidates, as well as all the great new Member nominees.  Please vote – and if you’re not free this week, be sure to assign your proxy for the meeting attendance: I and several other Members are happy to proxy for you.

Please read on for my take on what’s important for the ASF’s future…

Continue reading Shane’s Apache Director Position Statement 2015

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.