Contribution Review Checklist for RIMA

Last steps

Pinged Leo and Bill on their status (Stefan, 2nd November 2013).

Response from Leo (9th November 2013): Yes, I did start with it then. I'll email Geoff and see what he wants to do.
Pinged Leo and [email protected] on their status (Stefan, 7nd December 2013).
Answer from Leo (7th December 2013): Thanks for offering to take over the submission. I think Geoff is not able to put down the time necessary to have a package currently, and he didn't feel that he was able to generate enough interest from others to be worth the effort either. So I don't think the timing is good for him. I'd just archive it, send him a message about it (you are welcome to forward to him this message), and have him restart the submission it in the future if things change.
Answer from Geoff (8th December 2013): Thanks for the interest, but I think given the time that’s passed, the general lack of interest in Rima, and that I’m pretty short of time, you might as well take Rima off your books. If I ever get it to the point that I think it’s worth looking at again, I’ll be in touch.

Project Description: Rima is a tool for formulating and solving mathematical modeling and optimization problems in the Lua language. Rima's primary design goal is that models should be easy to re-use.
Contributor: Geoff Leyland, [email protected]
Contact Date: 3/4/2010
Handler: Leo Lopes
Reviewer: Bill Hart
Sent instructions: 6/28/2010

README/LICENSE files: (exists and reasonable) 11/8/2010
Project Roadmap (Level 1 only): (exists and reasonable) None (TODO)
AUTHORS/INSTALL files (Level 2 and above): (exists and reasonable) No INSTALL file. (TODO)
Code builds (Level 2 and above): (date checked)
Documentation (Level 3 and above): (exists and reasonable) (date checked)
Unit test (Level 4 and above): (has one and passed) (date checked)
Project binaries (Level 5): (exist and function properly) (date checked)

PM named: (name) (date)
PM familiar with Guidelines and Procedures for Project Management: (date)
- Legal issues
- Tracking contributions
- Responding to bugs
- Using SVN
- Using Trac
- Setting up a static Web page
- Standard practices (versioning and release, build procedures)
PM subscribed to mailing list: (date)
Code imported: (date)
PM given write access: (date)
Trac page set up: (date)
XML page (projDesc.xml, see documentation in the file itself, which can be copied and adapted from here) set up: (date)
Project announcement: (date)
Moved this page to ArchivedChecklists: 9th December 2013