On 6 Apr 2004, at 17:13, Kip Hampton wrote:
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
I think this document hits the mark, and I'm +1 on moving forward with becoming a TLP and adopting this new development approach. I've gone over this document twice now and have nothing to add to it at this point.
Of course we'll need a pumpking. I'm not saying I won't do it, but given my recent activity (rather - lack of) on AxKit I doubt many people would ask me to take up the role. But if it turns out to be a hot potato I'd be happy to pick it up as it's easier to arrange meetings and shout at people than it is to pick up the codebase again.
Matt.
