back to new submissions

• Date of last action: (November 2, 2013) Pinged the handler and reviewers.

  Response from Gus: No idea what you're talking about.

  Response from Lou:

    The chronology is this:

  October 2010:  proposed MSFLinks as project to Leo Lopes.

  November 2010: Matt & Gus agreed to review for Level 2; sent them a
                 tarball.

This was right in the usual INFORMS crisis period, so I wasn't expecting a quick response. I talked about the initial implementation at INFORMS Austin.

  April 2011:    Submitted binaries to Microsoft for MSF Foundation
                 validation testing. Sent Gus and Matt the `ping'
                 referred to below.

  August 2011:   Received feedback from Microsoft for the first round of
                 validation testing (copied below).

That same month my life went crazy and I've never been able to get back to this (or any of a dozen other things that I shed over the next six months). It's unlikely I'll be able to return to this any time in the near future, so it's dead unless someone is motivated to pick it up. If Solver Foundations is dead, there's not much point.

    I've had no contact with the MSF folks since receiving the initial test feedback. 

Lou on 4th November 2013: If it's my decision, move it to the archived checklists. I'm not likely to do anything with it in the next few years. Presumably it can be resurrected if someone gets interested.

• Wait for someone interested to pick it up again.

• Project Description: The initial content will be a C++/CLI shim layer that interfaces OsiClp/Clp to the Microsoft Solver Foundation backend API. The intent is to expand this fairly quickly to accommodate any OsiXXX solver. A critical step will be to add support for callback methods to the Osi API. Over the longer term, MSFLinks may well develop into an umbrella project for links to other COIN solvers. For obvious reasons, this project targets only the Microsoft Windows environment; initially, Visual Studio builds only.
• Contributor: Lou Hafer, [email protected]
• Contact Date: Halloween, 2010
• Handler: Lou Hafer
• Reviewer: Matt Saltzman, Gus Gassmann
• Sent instructions:

• Received CSRO: Already on file.
• Received DOL: committed November 1, 2010
• OSI-approved license: Eclipse Public License

• Classified (Level 1-5): Level 2

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

• (!Yes/No): (date)

• PM named: (November 1, 2010) Lou Hafer
• PM familiar with Guidelines and Procedures for Project Management: (November 1, 2010) Yep.
  • Legal issues: (April 22, 2011) Entirely too familiar.
  • Tracking contributions: (April 22, 2011) Yep.
  • Responding to bugs: (April 22, 2011) Questionable.
  • Using SVN: (April 22, 2011) Yep.
  • Using Trac: (April 22, 2011) Yep.
  • Setting up a static Web page: (April 22, 2011) Yep.
  • Standard practices (versioning and release, build procedures): (April 22, 2011) Yep.
• Parameters for project creation mailed to submission manager:

   # SVNPROJ  : MSFLinks
   # PROJDESC : Links between COIN solvers and Microsoft Solver Foundation.
   # PM       : Lou Hafer
   # PM_EMAIL : [email protected]

• 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: 5th November 2013