STOP - coin-or-foundation/tlc GitHub Wiki

STOP Contribution Review Checklist

Previous steps

  • Leo pinged Ted who offered to contact Brady (Jul 8 2010)
  • Ted on 2nd November 2013: For STOP, as far as I recall, I don't think we have the actual code. I was waiting on Brady to clean up the code and submit it formally. I can ping him again.
  • Stefan pinged Brady and Ted on 26th September 2014 to check whether the submission should still be considered as active. If not, he will move it to inactive submissions.
  • Ted replied that he got a response from Brady:
I had in fact already followed up with Brady and here was what he said:

"I think the STOP code needs some ongoing attention to make sure it's
working and see whether it's still giving useful estimates, since I imagine
solvers have been changing in the past few years.  I don't have time for
that level of attention right now.

I have no concerns if someone wants to pick it up and maintain/extend it,
though.  I'd be happy to devote a few hours to sharing knowledge and
helping with any initial cobwebs."

I was considering taking it under my wing, but hadn't gotten to looking
into it yet. I suggest that Brady passes the source code to me and I will
see if a student wants to take on looking at it a bit. In the meantime, we
can make the submission inactive and we will re-submit it when everything
is working.
  • moved to inactive submissions (27th September 2014)

General

  • Project Description: Selection tool for optimization parameters
  • Contributor: Brady Hunsaker
  • Contact Date: (date)
  • Handler: (who)
  • Sent instructions: (date)

Legal

  • Received CSRO: (date)
  • Received DOO: (date)
  • OSI-approved license: (license type)

Classification

  • Classified (Level 1-5): (see ProjectCategories)

Code and Documentation

  • README/LICENSE files: (exists and reasonable) (date checked)
  • Project Roadmap (Level 1): (exists and reasonable) (date checked)
  • AUTHORS/INSTALL files (Level 2 and above): (exists and reasonable) (date checked)
  • 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)

Accepted

  • (Yes/No): (date)

Establishing Project

  • PM named: (name) (date)
  • PM educated: (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 set up: (date)
  • Project announced: (date)
  • Moved this page to ArchivedChecklists: (27th September 2014)