Yaakov and I spoke about EKG at FOSDEM.
I'll let him lay out some of the roadmap/feature stuff we talked about, but I want to propose a larger question to the list, and especially to Michael:
The first item on the agenda was "is Ruby really the language that is going to make this project accessible to a wider number of contributors, and most maintainable for the future?" followed by "if we have a clear list of enhancements and/or new features, we should decide if Ruby or Python is this project's future before we write them."
So, in short:
Michael, how much of your own personal time do you see yourself devoting to EKG in the next 3 months? I say 3 months, because that is the timeline for development that I want to work on in order to have EKG meet the CommArch team's goals. Do you still see yourself as the lead developer of this project, or is it up to CommArch to find the engineering resources (which for the moment will be Yaakov) to take this project further?
And somewhat separate from that question, is it worth spending (at Yaakov's estimation) 10 days or so to rewrite the core of the code into Python, setting it up for a better future?
--Max