I think there's a slight misunderstanding- the code which Imtiaz developed is going to be applied as a patch attached to ESME-161 in Jira (https://issues.apache.org/jira/browse/ESME-161) and the code in github is a library used as a dependency. It is actually the successor to the scala-stats library, which we have already been using. We have already checked the library's license (which hasn't changed) and the licenses of its dependencies before last release, so I think we're still covered.
On Sun, Jun 6, 2010 at 2:01 AM, Joe Schaefer <[email protected]> wrote: > Be sure Imtiaz or whomever developed the code > formally assents to their code being committed > to esme. Specifically in the commit log message > call out the fact that Imtiaz developed the > code, and post-commit have him send an email here > saying "I have read and approved r952... ". > The reason you should do this is that pulling code > from github isn't covered by the Apache License's > contribution clauses (unlike posting patches to > apache's jira or mailing lists), so either an ICLA > is called for from the author, or something a bit > less heavyweight like I have described. > > > > > ----- Original Message ---- >> From: Richard Hirsch <[email protected]> >> To: [email protected] >> Cc: David Pollak <[email protected]> >> Sent: Sat, June 5, 2010 11:09:53 AM >> Subject: Take a look at Ostrich Integration >> >> Imtiaz has just sent me first results of his Ostrich >> ( > http://github.com/robey/ostrich) integration (see below). This >> means > that we now have a JSON-based way to access our JMX data. Why is >> this > important - developers can now develop web-based tools to >> track > various critical measures / metrics in ESME. We had JMX >> implemented > before but the problem was that we could just use the JMX >> interfaces > (MBean, etc.) - now developers can create their own mash-ups >> to > administer / track ESME events. Better still, it looks like we >> can > use port 80 which means that we could use Ostrich in the >> Stax > environment (still have to try this when I deploy on >> Monday). > > Here is a list of our current >> metrics > (http://incubator.apache.org/esme/jmx.html). > > I'll do a commit >> of Imtiaz's code on >> Monday. > > D. > > ----------------- > > imt...@imtiaz-20100131 ~ > $ >> curl >> http://localhost:9990/ping > {"response":"pong"} > > imt...@imtiaz-20100131 >> ~ > $ curl >> http://localhost:9990/server_info > {"build":"unknown","uptime":144344,"build_revision":"unknown","start_time":"Sat > Jun >> 05 18:20:41 IST >> 2010","name":"unknown","version":"0.0"} > > imt...@imtiaz-20100131 ~ > $ >> curl >> http://localhost:9990/reload > {"response":"ok"} > > imt...@imtiaz-20100131 >> ~ > $ curl >> http://localhost:9990/stats > {"counters":{"userCount":1,"liftSessions":1},"timings":{},"jvm":{"nonheap_commit > ted":52723712,"heap_max":259522560,"thread_peak_count":56,"heap_committed":25702 > 400,"uptime":204782,"nonheap_max":123731968,"thread_daemon_count":35,"num_cpus": > 2,"thread_count":55,"nonheap_used":42131152,"start_time":1275742241593,"heap_use > d":17745008},"gauges":{"users":1.0,"listener":1.0}} > > imt...@imtiaz-20100131 >> ~ > $ curl >> http://localHost:9990/shutdown > {"response":"ok"} > > imt...@imtiaz-20100131 >> ~ > $ curl http://localhost:9990/quiesce > curl: (7) couldn't connect to >> host > > imt...@imtiaz-20100131 ~ > $ > > <<<<<the last >> because shutdown shut the web interface...following with > port >> 80>>>>> > > > > imt...@imtiaz-20100131 ~ > $ curl >> http://localhost:80/ping > {"response":"pong"} > > imt...@imtiaz-20100131 >> ~ > $ curl >> http://localhost:80/stats > {"counters":{"userCount":1,"liftSessions":1},"timings":{},"jvm":{"nonheap_commit > ted":52789248,"heap_max":259522560,"thread_peak_count":53,"heap_committed":25329 > 664,"uptime":73953,"nonheap_max":123731968,"thread_daemon_count":33,"num_cpus":2 > ,"thread_count":53,"nonheap_used":42138472,"start_time":1275743193156,"heap_used > ":15911248},"gauges":{"users":1.0,"listener":1.0}} > > imt...@imtiaz-20100131 >> ~ > > > >
