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.

One thought on “Shane’s Apache Director Position Statement 2014

  1. Pingback: Shane’s Apache Director Position Statement, 2016 | Community Over Code

What do you think?