Tag Archives: apachecon

We’ve Always Done It That Way

From a Lightning Talk at ApacheCon Budapest

As you know, the Apache Software Foundation has a number of mottos that we like to use. Like, “Community Over Code”, and “No Jerks Allowed.” Another popular motto recently has been “We’ve Always Done It That Way.”

As you no doubt know, the ASF is an organization deeply rooted in tradition, which means that we never, ever change the way that we do anything. Those of you who have been around the ASF for a long time can verify this.

Here’s a few of the things that have been the same at the ASF for all time.

We have always required that every project have their code in CVS for revision control.

Um … I mean SVN. As far back as we’ve been around. We’ve always done it that way.

Well, except for … you know … unless your code is in Git.

But we definitely don’t let you use Github for collaboration.

… actually …

You Infrastructure guys ruin everything.

Since the beginning of time, ApacheCon has been organized and produced by a committee of members. We gather before the event, with all of the talk proposals printed out. We sort them into piles and argue over which ones will be scheduled. Third-party producers really don’t understand us, and so it’s important that we control every aspect of how ApacheCon is put together.

We’ve always done it that way. And so we’d never try anything else.

We have never had any paid staff, and would never consider having any.

All ASF projects are written in C, and always have been.

Also, all projects at the ASF are server projects of some kind. Desktop-type software projects are completely outside of what we do – what we’ve always done.

Wikis are the spawn of Satan, as we determined on long, heated, vitriolic mailing list threads, and we’ll never allow any project to have a wiki. At least, not one running on ASF hardware. Ever.

Except … these things have all changed.

Principle 13 in the Toyota Way says that one should make decisions slowly, by consensus, thoroughly considering all options, and then implement those decisions rapidly. We believe a similar thing at the ASF. So to people who have only been around for a short time, it looks like we never change anything. But the truth is that we change things slowly, because what we’re doing works, and we need to be sure that change is warranted, and is a good idea.

There is one thing, though, that I’m sure won’t ever change. Here at the ASF, we believe in collaborative, community-centric development.

We’ve always done it that way.

ApacheCon North America returns to Austin

We just got done with ApacheCon Europe in Budapest last week – http://apachecon.eu/ – and it’s time to start thinking about ApacheCon North America.

We’ll be holding ApacheCon North America, April 13-17th, 2015, in Austin, Texas. The call for papers is already open, at http://apachecon.com/, and we are hoping that this event will represent the breadth of the Apache Software Foundation projects.

Organize your community

The most important thing at this stage in the process is getting the Apache community involved in this event. ApacheCon exists to unite our community, get various projects to interact with one another, and bring new members into our community. The best way to accomplish these goals is to ensure that your project has representation at ApacheCon. Here are four specific areas where we need the help of Apache project communities:

Track layout

We’ve found that the very best way to have a project well represented in the content tracks is for someone deeply familiar with the project to craft an ideal track schedule, and then solicit speakers for those sessions. This has two immediate benefits.

First, it goes a long way to ensuring that the topic is covered with the breadth that it deserves, rather than having a few random talks that cover random esoteric parts of the technology, and ignore segments of the audience that you most want to attract.

Second, it is very encouraging to first-time speakers. It’s very difficult, and very intimidating, to try to come up with a topic to speak about the first few times. Seeing a list of proposed topics is the perfect way to say to a new speaker that what they know about is worth them proposing to a conference. “Hey, I could speak about that, and nobody would think it’s a stupid idea.”

Speakers

Some talks require certain speakers. You know this a lot better than we do, because it’s your project. We need your help to go to those specific speakers and encourage them to submit the specific talk(s) that you know they’ll shine at.

Reviewing and Scheduling

Once the talks have been submitted, we’re going to need your help reviewing them and building the schedule. To help with the review process, you’ll need to create an account in the CFP system (if you haven’t already done so) at https://identity.linuxfoundation.org/user and then email me – rbowen@apache.org – with your username, so that I can get you added to the review system. From there, you’ll see a list of talks to consider, and you can rate them according to how well you think they’ll fit the conference.

Of course, if you specifically solicited those talks, then you’ll quickly mark them as “Strongly Accept” with a comment of “I solicited this specific talk”, and move on. (The CFP review interface is at http://events.linuxfoundation.org/cfp/cfp-list if you already have an account.) You can review talks from other topics/tracks, too, if you feel that you have some domain knowledge.

Once the review process is complete, we’ll select the talks that rate the highest, and at that point we’ll be back in touch with you to help us order them correctly. Here, again, if you’ve already approached us with a layout of your ideal content track, there’s really nothing else to do. But if there are other talks that made it in through the review process, we’ll need help.

Hackathons

A key benefit of ApacheCon is getting your developers together in one place to work on things. We’ve got a a general hackathon area where you can gather to work on bugs, features, documentation, or discuss thorny community issues. (Don’t forget to summarize your conversations back to the mailing list for the people who can’t make it!)

If you want to have a sponsored hackathon specifically for your project, we can find room to make that happen. Just get in touch with me, and we’ll work out the details.

Talking before the event about what you’ll be working on has a number of benefits.

First, it gives people time to think about how they can contribute, and plan accordingly.

Second, it encourages people to come in from the edges of the project to participate more fully in the life of the community, because they can select something that they’re particularly interested in, and work on it in company with the rest of the project members.

Using the ApacheCon wiki – http://wiki.apache.org/apachecon/ – as a place to work on your hackathon topics gives conference attendees an easy way to find topics that they might be interested in, and connecting with the community. If you don’t have write permissions to the wiki, send me your wiki username, and I’ll get you added to the access list.

Your company uses Apache software every day. Perhaps you even contribute to a project as part of your day job. ApacheCon is the best place in the world for your company to show off their involvement in Apache, and to find new talent to work on their products. Sponsorship of ApacheCon gives you a platform from which to talk about what your company does, and gets your company name recognized – and closely associated with Apache – by the people that make the decisions in some of the most important places in IT.

If you’d like to sponsor ApacheCon, get in touch with me, and I’ll get you a sponsor prospectus, and help you select the sponsorship opportunity that’s right for you – whether that’s the conference lanyard, an evening reception, the conference bags or tshirts, or a booth in the exhibit hall. There’s something for every budget and level of exposure you’re looking for.

Get the word out

You have the ear of your project community – both the developers and the end users. We need your help telling them about this event. Right now, we need you to tell them to save the date. Later on, we’ll need you to be telling them about specific talks that will be of interest to them, both directly relating to your project and about other related projects that they should know about.

Join the Community Development mailing list – http://www.apache.org/foundation/mailinglists.html#foundation-community – where we’ll be posting suggested tweets, suggested things to share on Facebook and Google Plus, and other suggestions for helping us get the message to the communities where you have a more trusted voice than we do.

This is critical – it does no good putting together a great event, if nobody comes. You know who needs to hear the message, and you know where they hang out. A well-placed message by the trusted members of the community is far more effective than a dozen mass emails from a stranger.

Come join us!

So, if you’d like to help us make ApacheCon a success, get onto the Community Development list – http://www.apache.org/foundation/mailinglists.html#foundation-community – and on the #apachecon IRC channel on Freenode, and speak up. Tell us what you can do, and we’ll find a place for you to fit in.

Apache httpd at ApacheCon Budapest

tl;dr – There will be a full day of Apache httpd content at ApacheCon Europe, in Budapest, November 17th – apacheconeu2014.sched.org/type/httpd

Links:

* ApacheCon website – http://apachecon.eu
* ApacheCon Schedule – http://apacheconeu2014.sched.org/
* Register – http://events.linuxfoundation.org//events/apachecon-europe/attend/register
* Apache httpd – http://httpd.apache.org/

I’ll be giving two talks about the Apache http server at ApacheCon.eu in a little over 2 months.

On Monday morning (November 17th) I’ll be speaking about Configurable Configuration in httpd. New in Apache httpd 2.4 is the ability to put conditional statements in your configuration file which are evaluated at request time rather than at server startup time. This means that you can have the configuration adapt to the specifics of the request – like, where in the world it came from, what time of day it is, what browser they’re using, and so on. With the new If/ElseIf/Else syntax, you can embed this logic directly in your configuration.

2.4 also includes mod_macro, and a new expression evaluation engine, which further enhance httpd’s ability to have a truly flexible configuration language.

Later in the day, I’ll be speaking about mod_rewrite, the module that lets you manipulate requests using regular expressions and other logic, also at request time. Most people who have some kind of website are forced to use mod_rewrite now and then, and there’s a lot of terrible advice online about ways to use it. In this session, you’ll learn learn the basics of regular expression syntax, and how to correctly craft rewrite expressions.

There’s other httpd content throughout the day, and the people who created this technology will be on hand to answer your questions, and teach you all of the details of using the server. We’ll also have a hackathon running the entire length of the conference, where people will be working on various aspects of the server. In particular, I’ll be working on the documentation. If you’re interested in participating in the httpd docs, this is a great time to learn how to do that, and dive into submitting your first patch.

See you there!

ApacheCon NA 2014 Keynotes

This year at ApacheCon, I had the unenviable task of selecting the keynotes. This is always difficult, because you want to pick people who are inspirational, exciting speakers, but people who haven’t already been heard by everyone at the event. You also need to give some of your sponsors the stage for a bit, and hope that they don’t take the opportunity to bore the audience with a sales pitch.

I got lucky.

(By the way, videos of all of these talks will be on the Apache YouTube channel very soon – https://www.youtube.com/user/TheApacheFoundation)

We had a great lineup, covering a wide range of topics.

Day One:

0022_ApacheCon

We started with Hillary Mason, talking about Big Data. Unlike a lot of droney Big Data talks, she defined Big Data in terms of using huge quantities of data to solve actual human problems, and gave a historical view of Big Data going back to the first US Census. Good stuff.

0084_ApacheCon

Next, Samisa Abeysinghe talked about Apache Stratos, and the services and products that WSO2 is building on top of them. Although he had the opportunity to do nothing more than promote his (admittedly awesome) company, Samisa talked more about the Stratos project and the great things that it’s doing in the Platform As A Service space. We love WSO2.

0127_ApacheCon

And to round out the first day of keynotes, James Watters from Pivotal talked about the CloudFoundry foundation that he’s set up, and why he chose to do that rather than going with an existing foundation. Among other things. I had talked some with James prior to the conference about his talk, and he came through with a really great talk.

Day Two:

0602.ApacheCon

Day Two started with something a little different. Upayavira talked about the tool that geeks seldom mention – their minds – and how to take care of it. He talked about mindfullness – the art of being where you are when you are, and noticing what is going on around you. He then led us through several minutes of quiet contemplation and focusing of our minds. While some people thought this was a little weird, most people I talked with appreciated this calm centering way to start the morning.

0635.ApacheCon

Mark Hinkle, from Citrix, talked about community and code, and made a specific call to the foundation to revise its sponsorship rules to permit companies like Citrix to give us more money in a per-project targeted fashion.

0772.ApacheCon

And Jim Zemlin rounded out the day two keynotes by talking about what he does at the Linux Foundation, and how different foundations fill different niches in the Open Source software ecosystem. This is a talk I personally asked him to do, so I was very pleased with how it turned out. Different foundations do things differently, and I wanted him to talk some about why, and why some projects may fit better in one or another.

At the end of day three, we had two closing keynotes. We’ve done closing keynotes before with mixed results – a lot of people leave before. But we figured that with more content on the days after that, people would stay around. So it was disappointing to see how empty the rooms were. But the talks were great.

1052_ApacheCon

Allison Randal, a self-proclaimed Unix Graybeard (no, really!) talked about the cloud, and how it’s just the latest incarnation of a steady series of small innovations over the last 50 years or so, and what we can look for in the coming decade. She spoke glowingly about Apache and its leadership role in that space.

1105_ApacheCon

Then Jason Hibbets finished up by talking about his work in Open Source Cities, and how Open Source methodologies can work in real-world collaboration to make your home town so much better. I’d heard this presentation before, but it was still great to hear the things that he’s been doing in his town, and how they can be done in other places using the same model.

So, check the Apache YouTube channel in a week or so – https://www.youtube.com/user/TheApacheFoundation – and make some time to watch these presentations. I was especially pleased with Hillary and Upayavira’s talks, and recommend you watch those if you are short on time and want to pick just a few.

ApacheCon North America 2014

Last week I had the honor of chairing ApacheCon North America 2014 in Denver Colorado. I could hardly be any prouder of what we were able to do on such an incredibly short timeline. Most of the credit goes to Angela Brown and her amazing team at the Linux Foundation who handled the logistics of the event.

My report to the Apache Software Foundation board follows:

ApacheCon North America 2014 was held April 7-9 in Denver, Colorado, USA. Despite the very late start, we had higher attendance than last year, and almost everyone that I have spoken with has declared it an enormous success. Attendees, speakers and sponsors have all expressed approval of the job that Angela and the Linux Foundation did in the production of the event. Speaking personally, it was the most stress-free ApacheCon I have ever had.

Several projects had dedicated hackathon spaces, while the main hackathon room was unfortunately well off of the beaten path, and went unnoticed by many attendees. We plan to have the main hackathon space much more prominently located in a main traffic area, where it cannot be missed, in Budapest, as I feel that the hackathon should remain a central part of the event, for its community-building opportunities.

Speaking of Budapest, on the first day of the event, we announced ApacheCon Europe, which will be held November 17-21 2014 in Budapest. The website for that is up at http://apachecon.eu/ and the CFP is open, and will close June 25, 2014. We plan to announce the schedule on July 28, 2014, giving us nearly 4 months lead time before the conference. We have already received talk submissions, and a few conference registrations. I will try to provide statistics each month between now and the conference.

As with ApacheCon NA, there will be a CloudStack Collaboration Conference co-located with ApacheCon. We are also discussing the possibility of a co-located Apache OpenOffice user-focused event on the 20th and 21st, or possibly just one day.

We eagerly welcome proposals from other projects which wish to have similar co-located events, or other more developer- or PMC-focused events like the Traffic Server Summit, which was held in Denver.

Discussion has begun regarding a venue for ApacheCon North America 2015, with Austin and Las Vegas early favorites, but several other cities being considered.

I’ll be posting several more things abut it, because they deserve individual attention. Also, we’ll be posting video and audio from the event on the ApacheCon website in the very near future.

ApacheCon welcomes SourceForge back for another year

The following guest post appears on the SourceForge blog today. I’m personally very pleased to welcome SourceForge back to ApacheCon for another year.

————-

The Apache Software Foundation is pleased to announce ApacheCon US 2014, which we’re presenting in conjunction with the Linux Foundation. The conference will be held in Denver, Colorado, and features three days, ten tracks of content on more than 70 of the Apache Software Foundation’s Open Source projects, including Apache OpenOffice, Apache Hadoop, Apache Lucene, and many others.

We’re especially pleased to welcome SourceForge as a media partner for this event.

See http://na.apachecon.com/ for the full schedule, as well as the evening events, BOFs, Lightning Talks, and project summits.

Co-located with the event is the Cloudstack Collaboration Conference – http://events.linuxfoundation.org/events/cloudstack-collaboration-conference-north-america – the best place to learn about Apache CloudStack.

Apache OpenOffice – http://openoffice.apache.org/ – has an entire day of content, including both technical and community talks.

Hadoop, and its ecosystem of Big Data projects, has more than five full days of content (two tracks on two days, one track on the other).

Other projects, such as Cordova, Tomcat, and the Apache http server, have a fully day, or two, of content.

If you want to learn more about Apache Allura (Incubating), an Open Source software forge (and also the code that runs SourceForge) we’ll have two presentations about Allura, by two of the engineers who work on that code: Dave Brondsema and Wayne Witzel. Learn how to use Allura to develop your own projects, and join the community to make the platform even better.

This is the place to come if you rely on any of the projects of the Apache Software Foundation, and if you want to hang out with the men and women who develop them. We’ve been doing this event since 1998, and this promises to be the best one yet, with more content than we’ve ever presented before.

ApacheCon EU

ApacheCon EU starts tomorrow, and, for the first time ever, I won’t be there.

In fact, today is my very last chance to say this – I’ve been to every (official) ApacheCon. In fact, if you don’t count 1998, I’m the only person who has been to every ApacheCon.

In 1998, there was an event called ApacheCon, in San Francisco, hosted by CNet, but that was before the Apache Software Foundation was formed. So I choose not to count that one.

Then, in 2000, I spoke at ApacheCon 2000 in Orlando. Then there was London 2000 with Douglas Adams keynoting. Since then, we’ve been a lot of places, including Santa Clara, San Diego, Las Vegas, Atlanta, New Orleans, Amsterdam, Dublin, Vancouver (Canada) and Stuttgart – not in that order.And Colombo, Sri Lanka, where I met Arthur C. Clarke. In fact, it’s the Sri Lanka one that lets me claim the honor of being the only person to go to every one, because the only ASF members there were me, Ken Coar, and Danese Cooper.

But, tomorrow, ApacheCon EU starts, in Sinsheim Germany, and I won’t be there. Already many of my friends have gathered there, and are having dinner there right now. I wish I could be there with them, and not just because it would keep my record intact. I love ApacheCon. I love giving and attending the talks. I love spending time with old friends and meeting new ones. I love the passion of the community, and learning about the new sub-communities that are joining the larger Apache family.

And I sincerely hope that the is the last one I’ll miss.

Looking forward to ApacheCon North America 2013 in Portland. I plan to be at that one. You should come, too.

Apache Web Server training, mod_rewrite training

I’ll be teaching two training classes at the upcoming ApacheCon in Atlanta in November.

On Monday, I’ll be teaching Apache, Nuts to Bolts, with Jim Jagielski, another long-time contributor to the Apache httpd project. This class is a day-long training on everything from obtaining and installing the server to configuration, third-party modules, and security, and everything in between.

On Tuesday, I’ll be teaching a half-day training onmod_rewrite, the most powerful, and probably most confusing module, and the source of the majority of questions on any given Apache support forum.

I’d love to have you in my classes. ApacheCon will be fun, as always, and Atlanta is a great city. We’d love to see you there.

mod_rewrite docs rewrite at ApacheCon

The plan, (assuming I don’t get sidetracked on a million other things, which is what usually happens) is to do a major overhaul of the mod_rewrite documentation during the hackathon at ApacheCon. Please speak up if you have specific comments or recommendations. So far, the outline is something like this.

1) A couple of years ago, I split the “Rewrite Guide” into basic and advanced. This was ill-advised, and the division was stupid. Now it’s just harder to find stuff. Going to re-merge those, and then try to do a division based on topic, rather than difficulty, since that’s not a particularly useful concept.

2) Rewrite cookbook, divided into categories of, perhaps:
a. redirecting/remapping
b. controlling access
c. when not to use mod_rewrite (aka ‘mod_rewrite is obsolete’)
d. advanced features

3) Scrap the inscrutable examples. Both the guide and the formal docs are littered with examples that either never happen in the real world, or are done better using some of the built-in functionality of other modules like mod_alias and mod_dir. Scrap those examples entirely, rather than continuing to try to make then scrutable.

4) Rewrite Flags documentation. Started this years ago, and never really finished it. Also, needs to be updated to include the new flags that have been added in 2.2 and trunk.

5) General grammatical overhaul, hopefully with help from Noirin, who has better grammar than all the rest of us put together. (Actually, that’s the problem – it was written by all of the rest of us put together, resulting in a mish-mash of styles and voices.)

6) A document about (so-called) S.E.O. uses of mod_rewrite, discussing both the techniques that can be used, and the misinformation that tends to drive the desire to use those techniques. This needs to be handled carefully, because there’s a tendency to simply state that all SEO is snake oil – which much of it is – and ignore the topic entirely. But, folks are going to do this stuff whether or not we approve, and it’s better if they do it well. At least, that’s what I think at this particular moment.

2c, above, is both about stuff that you shouldn’t do with mod_rewrite at all, and also some of the new features in 2.2 and trunk that make mod_rewrite unnecessary.

Tomcat at ApacheCon

Tomcat is one of the oldest members of the Apache family, and one of the standard building blocks of the web as we know it today. It can sometimes fall below the radar, because it just works, so most folks are completely unaware of it.

Filip Hanik will be doing a training class on Tomcat at ApacheCon this year. I spoke with him last week for Feathercast, and I’ve finally edited it. You can listen here, or come to ApacheCon and hear him there.