Howdy Folks,
This message is a long time coming and, since no one seems to want to step up to address the issue I guess I'll be the one to drag in into the light...
Specifically, I'm concerned about apparent lack of recent interest in AxKit among what have historically been its core developers and the general "so what" attitude that is being presented to its users.
I'm aware that every project has its ebb and flow, and that sometimes the requirements of Real Life don't always make it possible to contribute the time and attention that we'd like; but the inertia seems to go deeper than that, in this case.
Speaking personally for a moment, the timing for this couldn't possibly be worse. On the one hand, I'm very excited to be at the end of the publishing process for the O'Reilly AxKit book, but, in emerging from that 2-year ordeal (with a book that I believe the AxKit community can be proud of) I find that the once-vibrant group that inspired me to write the thing in the first place have, for all practical purposes, abandoned ship.
I don't see any value in pointing fingers or ascribing blame-- we've all done what we could as time permitted and need required (and we should be *proud* of what we've done!)-- but its time, I think, to draw a line between AxKit's past and its future.
Letting the AxKit project fall by the wayside is simply not an option. In addition to our regular users, we have other OSS community projects and commercial companies whose development plans require a vital and energetic AxKit.
So, where do we go from here?
For those who may not be aware, the Apache XML Project Management Committee is being reorganized and AxKit has the opportunity to become what is known as a "top-level project" (much like mod_perl or Cocoon is now). The most significant change for us, is that we can set the guidelines and processes by which AxKit gets developed in a way that most intimately reflects our goals and ideas as a smaller community. That is, *we* get to define the rules and conventions that we believe will lead to best possible AxKit for everyone.
I suggest that we take the opportunity that (potentially) becoming a top-level project provides to take stock, put aside old baggage, and move AxKit forward with renewed vigor. To that end, I've put together a first draft proposal for the guidelines and mission that are required for AxKit as an Apache top-level project. That document can be found here [1].
It is important to note that this document is not intended to be the final word. In fact, the official charter and guidelines for AxKit as a TLP must be decided by its new Project Management Committee and approved by the ASF Board. I post it here (with some trepidation) only as a means open discussion about where we might be going and a concrete means to get there.
The time for shoe-gazing, shoulder-shrugging, and praying for "round tuits" is now over. Be realistic. If AxKit is not part of your future then so be it; things change and no one will judge you for being honest. But if you are practically committed to AxKit and its evolution (and are willing and able to devote the time to back that up) then please, help us re-kindle the fire and move on.
Okay, I've said my piece-- now its time to hear from others. Thanks for bearing with such a long-winded screed...
Cheers, -kip
[1] http://totalcinema.com/axkit/axkitguidelines.xml
