Nick called my bluff on my review comment for his Apache Way talk proposal. I said we need to update these and so Nick asked for suggestions - damn him making me work for my comment ;-)
Here's what I was thinking when I wrote that comment... For years we've rolled out the same "this is how apache works" session. We've talked about consensus building, PMCs, voting, board s and members. We've said our projects are independent. We've repeated the same governance content using the same slides we've been using for years. I pointed out in my comment that Nick hasn't even bothered to update the stats in his abstract (the lack of refreshed content is true of my own Apache Way slides, I'm not intending to pick on Nick). There is value in these sessions, some people are completely new and we probably should still schedule them. However, I think we ought to do some new stuff along the lines of: How is the ASF different from other foundations? Why should I bring my project to Apache? How can I get paid to work on Apache projects? How do I build a business around apache software? Why doesn't the ASF pay for software development? Why, after 15 years, do people see the ASF as a desirable place to take software? Why does the ASF have a reputation for bureaucracy amongst the younger GitHub crowd? Just what rules are immutable in the ASF? And much more... Sent from my Windows Phone
