[Radmind-devel] Radmind-PC status check

[Kevin G. <ktgraham@Princeton.EDU>]

Several people who've been involved with porting the Radmind tools to Windows participated in an online chat to discuss that project.  Here are the notes from the chat.

Kevin Graham
OIT Student Computing Services
Princeton University

Participating:
Patrick McNeal, U. Mich.
Rob Smith, Stanford
Jarod Malestein, U. Mich.
Kevin Graham, Princeton
Allan Chen, Stanford
Surajit Bose, Stanford

Item 1: The separate "radmind-pc" list hosted by Stanford is no longer necessary.  Traffic should now go to the radmind-devel or radmind-users SourceForge lists, as appropriate.  The project will be advertised to a larger community that way.  If traffic becomes excessive, it is possible to make a separate PC-specific list on SourceForge.
   1.1: Allan disabled Stanford's radmind-pc list shortly after the chat.
   1.2: Archives of the list are still available, however, messages sent after Jan 2006 were apparently never archived (though there was minimal traffic during that time).

Item 2: Jarod created a new page in the radmind.org site specifically for the Windows port of Radmind.  The URL is http://rsug.itd.umich.edu/software/radmind/windows.html or http://www.radmind.org/windows.html.  This page will mostly link to resources on SourceForge.

Item 3: We believe the current code is ready for wider release (though still beta).  Patrick or Jarod will put it in the CVS on SF as version 0.7.0, and will post a message to radmind-announce when it's available
   3.1: Allan will send to Jarod some sample negative transcripts developed by Terrence Bobryk-Ozaki.  Jarod will make them easily accessible for people who download ver. 0.7.0
   3.2: Rob will send Jarod some sample negative transcripts developed by Fred Thomson.  Jarod will also make those available
   3.3: Allan will forward the announcement to mailing lists where interest has been expressed previously

Item 4: Development resources-  Stanford will likely be hiring a programmer for the summer, who can devote some time to radmind.  Surajit and Allan will work on scheduling that person's time.  Jarod also has some time to allot to coding, but will be away for 6 weeks starting around the first of August.
   4.1: Kevin will speak to Dustin King to see what time he has available over the summer
   4.2: Rob suggests that users will likely be more interested in having bugs fixed than in adding new features.
   4.3: As usual, users should report bugs through the bug tracker (not through the user list),  so they can be prioritized and assigned properly
   4.3: New features necessary to bring the project to a 1.0 level are certificate support and configs
   4.4: Jarod added Dustin's name to the "contributions" page.