What the board has decided about this committee or office, and the reports it filed, most recent first. Generated from the published minutes.
These categorised views are best effort. They are read from the published minutes by a program, and what it can attribute to a committee depends on how each resolution happens to be worded — so a page may be incomplete, and nothing here overrides the minutes themselves. The raw minutes are the source of truth.
Please note. The board approves the minutes of a meeting at the meeting after it, and they are published then - so the most recent meeting is not usually here. ASF Members can read the draft in the board's own repository until it is.
[raw] the published minutes, which are the record. [main index]
(No report. Kitty is voting to retire itself due to inactivity.)
By Shepherd: Retirement VOTE thread is +3 to retire with no other votes.
It has not been closed, but was started on October 1.
Signed-off-by: Wave (shepherd)
Kitty is a lightweight, production focused, Java-based application server performance diagnostic and management utility. Kitty entered incubation on October 3rd, 2010. A vote to retire the Kitty podling due to inactivity is in progress. Signed off by mentor: Shepherd: Mohammad Nour
The Kitty Project is a lightweight, production focused, Java-based
application server performance diagnostic and management utility. Kitty
is written in Groovy.
The project entered incubation on 2010-10-03.
In order to get graduated, Kitty needs the following features:
- The ability to save profiles of commonly connected to jmx servers
including groups of tomcat servers
- The ability to collect metrics on an aggregate group of JMX servers
There are no issues that require the Incubator PMC's or the board's attention.
The community hasn't grown since the last report.
The project had some contribution as far as code is concerned, but the
mailing list had no new threads started nor old threads had new contributions.
Changes were related to the management of the console output, and some
re-engineering in order to begin working on the missing features.
Signed off by mentor: kevan
Incubating since 2010-10-03 Description Kitty is a command line JMX Client written in Groovy. It is a lightweight, production focused, application server performance diagnostic and management utility. The three most important issues to address in the move towards graduation: 1) The community around this project is absent, looking at the amount of mails sent to the mailing list in the past months 2) The lack of a "Product Owner" who can prioritise stories/tasks, leaving the developers without a clue about the functionalities to implement 3) The code is a port from another language (Jython), and the history of the past project seems lost, so there isn't any reference about how the actual code should work. Also, there is no test (acceptance criteria) in support of that nor for the new features to implement. Any issues that the Incubator PMC or ASF Board might wish/need to be aware of? What seems relevant to me at the moment is the lack of communication between the committers; it would be fine if there was a clear statement about who is still interested and who is not in participating in the project, and how to reorganise the now shrunken team, if still there is one. How has the community developed since the last report? Sadly, the community hasn't develop at all; even worse, we faced the loss of some members who were actively involved in the project development/management. How has the project developed since the last report? Jira is not updated, leaving a shade of uncertainty about what has been fixed and what is still in progress since the last report. It seems that the last update was done in October, the 4th, with a fix regarding the correct navigation through the server tree in a file-system fashion.
Apache Kitty is a command-line, user friendly JMX utility, incubating since November 2010. * Top graduation blockers: 1) Still resolving major bugs, 2) Have not yet added enough user-friendly / convenience functionality * Description: Kitty is a lightweight, universal, and user-friendly / fast JMX utility * The latest developments is the Kitty community has grown after reaching out to the Groovy development community, we have seen much more community involvement than the past. Voted in Alessandro Novarini as a Kitty Committer.
Community building efforts have been initiated within the Groovy community to help us get to our first release. We have succeeded in generating interest and Groovy contributors have offered to assist on the project by contributing patches/expertise. No further development advances have been made.
Kitty was accepted into the Incubator on 10 October 2010. The Kitty Project is a lightweight, production focused, Java-based application server performance diagnostic and management utility. The project has imported existing code, lists have been set up and committer karma assigned. The current challenges facing the project are: * Continue to generate interest and grow a community * Prepare and work towards a release * Resolve critical defects introduced during the Groovy port The Incubator PMC / ASF Board should be aware that: * Community activity is slow to grow, but communication and progress is being made towards a release Since the last report some users have offered ideas as a result of project presentations at various user groups. Tasks are being organised and some progress has been made with code.
Kitty is a command-line based JMX administration and automation utility. This month was primarily engaged in discussion about the roadmap of the project. After presenting the project to the Los Angeles Java Users Group, the community here expressed that the utility should not only focus on Tomcat, but should have a plugin architecture where application-specific JMX attributes are made available by dropping in plugins in to the application. Kitty currently doesn't have such a capability, and the kitty-dev list agrees that Kitty should head in this direction. A document will be produced discussing how to best achieve the modular architecture, and begin working on adding these capabilities, beginning with Tomcat 6 and Tomcat 7 plugins. Some small code cleanup was done, and documentation will be produce on how to get started in developing for Kitty to promote further community adoption.