That seems kinda low-level for a board report... any one else? On Jul 12, 2013, at 2:10 PM, "Mattmann, Chris A (398J)" <[email protected]> wrote:
> [dropped board@] > > Thanks Jim you da man. I'm just catching up on email sorry about that. > > One thing I would add to the next report is that I spec'ed out a REST > API start on the Wiki. I'll hopefully get some cycles to start to > actually work on it (in Bottle) soonish. > > Cheers, > Chris > > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Chris Mattmann, Ph.D. > Senior Computer Scientist > NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA > Office: 171-266B, Mailstop: 171-246 > Email: [email protected] > WWW: http://sunset.usc.edu/~mattmann/ > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > Adjunct Assistant Professor, Computer Science Department > University of Southern California, Los Angeles, CA 90089 USA > ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ > > > > > > > -----Original Message----- > From: Jim Jagielski <[email protected]> > Reply-To: "[email protected]" <[email protected]> > Date: Wednesday, July 10, 2013 10:10 AM > To: Apache Board <[email protected]> > Cc: "[email protected]" <[email protected]> > Subject: [REPORT] Apache Steve > >> DESCRIPTION >> >> Apache Steve is a collection of tools and programs used by the >> ASF to implement the STV voting system and tallying of results. >> >> RELEASES >> >> * No releases yet. >> >> CURRENT ACTIVITY >> >> * The Apache Steve website frame is up. A logo has been selected >> and work regarding populating the website will commence. >> >> * The code was used in the Incubator PMC Chair election. This >> was the 1st use of the tranferred code under the official Steve >> repo. >> >> * Work and discussion regarding porting the current Perl-based code >> to Python has started. We have baselined Python 2.7. >> >> COMMUNITY >> >> * Since the last report we have added Alan Cabrera and Sean >> Kelly as new committers. >> >> ISSUES >> >> * There are no issues requiring board attention at this time. >> >
