With Apache board elections coming up soon, an ASF Member came up with a great set of questions for all director candidates. With permission, I’m sharing those questions here, and providing my answers as well.
The ASF is holding its 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 – including my 2017 board statement.
Please read on for my take on what’s important for the ASF’s future – or see my Q&A about where Apache is heading.
As the ASF’s Annual Member’s Meeting approaches this month, the Membership has an opportunity to vote in new individual Members to the Foundation. I’ve written about how member meetings work and have proposed some process improvements.
But the bigger question is: how can the membership better help the ASF succeed? What a Member can do at the ASF is documented, but what should Members consider doing? Where does the ASF need Members to help out, and how?
Curious about anything at the ASF or about Apache projects? Can’t find the best place to ask? Here are a few meta-FAQs about FAQs on Apache, the ASF, and Apache projects and communities.
How can I get involved at Apache?
Just get started by emailing your ideas or questions to an Apache project you’re interested in.It’s up to you to start – the best projects to work on are ones you are already interested in. The Community Development project is here to help point you in the right direction.
How can I become an Apache committer?
First – find a project you are interested in. The best way to get involved is to use an Apache software product that you have a reason to use (even if just curiosity), and then ask questions or submit code patches to that project’s mailing lists.
It’s all up to you – Apache projects run on merit, which means people who do more work on that project – as measured by the community – get more of a say.
How many Apache projects are there?
How do mailing lists work at Apache? Where should I email to ask questions?
Everything at Apache happens on archived mailing lists.
Find the right list to use. Technical questions always go to that project’s dev@ list – every project is independent and separate. Reading the Apache mail archives is a great way to see what other people are asking.
How is Apache software licensed? Is it free to use?
Apache software uses the Apache License, version 2.0. Questions? Contact the Legal Affairs Committee. Apache PMCs with specific questions: open a LEGAL Jira. All Apache software products are always free (no charge) to download and use.
Does Apache hold any trademarks or brands?
The ASF owns Apache trademarks, which include all Apache project and software product names and logos. Read useful trademark resources.
Where can I find press releases or analyst briefings?
Who does what at Apache?
How is the ASF organized? Is it a corporation?
How do I ask Infrastructure for help?
The crack Apache Infrastructure team runs everything, and protects our servers from rogue gnomes; you can contact Infra here. Remember: all questions about Apache software products should go to that project’s mailing list.
How do Apache projects work? What’s this Apache Way I’ve heard about?
Are donations to the ASF needed? Can I deduct them from my taxes?
How do I get source code?
Where else can I ask any questions about the ASF?
Apache Community Development (ComDev) volunteers are here to answer any other questions you have about how Apache communities work. You can read all the past questions on the ComDev mailing list.
My question wasn’t answered here!
Add your comments below if there are other questions that need answers – or ask the ComDev project for help!
It’s important to have useful goals that you can measure, but more important that help you focus your work. It’s doubly important to have goals when you work for yourself and are trying to start your own business! Getting Punderthings off the ground can go in so many ways, and focus is important.
November is National Novel Writing Month – which is a great motivator, although I’m no novelist myself. My stories are either short and goofy, possibly with some science fiction thrown in – or are about open source projects, people, and brands, and those are more about teaching. So instead of attempting a novel, I’ll be blogging or otherwise writing essays each day this month.
I was thinking that writing is (often) more useful than reading. Reading something can be an escape, can be inspirational, or can teach you something. But when you write something (and share it, of course) then not only can you learn something, but others might be able to learn (or be entertained, or inspired) along the way. I often forget how important sharing our stories and organizing thoughts into more than 140 characters can be.
To keep myself motivated, I’m planning to write some sort of content every day in November – mostly on open source topics either here or at Choose A Foundation, The Apache Way, or some other websites I run, but some topics will be about local life.
I hope to improve on my goals as well – mostly by writing and publishing something earlier in the day than bedtime! See you tomorrow morning on the internet!
Nothing in life is to be feared, it is only to be understood. Now is the time to understand more, so that we may fear less. ― Marie Curie
(Today we’re interviewing Shane Curcuru about the recent issues reported with Facebook’s React.js software’s BSD + PATENTS file license, and what the Apache Software Foundation (ASF) has to do with it all. Shane serves in a leadership position at the ASF, but he wants you to know he’s speaking only as an individual here; this does not represent an official position of the ASF.)
UPDATE: Facebook has relicensed React.js as well as some other software under the MIT license, without the FB+PATENTS file. That’s good news, in general!
Hello and welcome to our interview about the recent licensing kerfuffle around Facebook’s React.js software, and the custom license including a custom PATENTS file that Facebook uses for the software.
There are really three aspects to your project’s decision (to use React.js or not based on the BSD+Patents license), and it’s important to consider each of them. You really need to consider which aspects are important to your project’s success — and which ones don’t really matter to you.
(See the updated FAQ about the PATENTS issue on Medium!)
- Legal — both details of the license and PATENTS file that Facebook offers React.js under, and some realistic situations where the patent clauses might actually come into play (which is certainly rare in court, but it’s the chilling effect of uncertainty that’s the issue)
- Technology — are other libraries sufficiently functional to provide the features your project needs? Does a project have the capacity to make a change, if they decided to?
- Community — how does the rest of the open source community-of-communities see the issue, and care about your choices? This includes both future buyers of a startup, as well as future partners, as well as future talent (employees) or contributors (open source developers).
Our annual Member’s Meeting for the ASF went well, resulting in some new members getting elected as well as two new directors being elected to the board. While we wait for a bit of paperwork to get filed, let’s document what needs to happen after a Member’s Meeting at Apache.
The ASF is a membership corporation and holds an Annual Member’s Meeting every year to elect the board and nominate/elect new members. As a volunteer-run software organization, we run this process by – wait for it – by emailing around a set of cryptically formatted text files from our private Subversion repository. Of course, as (mostly) software people, we could make it easier on ourselves… with better software. Shoemaker’s children, indeed.
The ASF is holding it’s annual Member’s meeting now, where Members get to elect a new board as well as elect new individual Members to the Foundation. We do this by holding a live IRC meeting on a Tuesday, then we vote with secure email ballots asynchronously during the recess, then reconvene on Thursday to announce results. But how does the meeting really work?