Repository Migration for Namespace Refactor

As part of the namespace refactor, we surveyed the packages in and near the OpenFF umbrella to roughly evaluate what software would eventually fall under a unified openff namespace. Something like this table will eventually be similar to a maintainers' “dashboard” of badges and other status checks

Package name

Status

Stakeholders (non-exhaustive)

Package name

Status

Stakeholders (non-exhaustive)

Toolkit

To be moved

@Jeffrey Wagner and many others

OpenFF Evaluator

To be moved

@Simon Boothroyd @David Dotson

openforcefields

To be moved

 

SMIRNOFF99Frosst

To be moved

 

QCSubmit

To be moved when released

@Joshua Horton

OpenFF System

To be moved when released

@Matt Thompson

CMILES

TBD, maybe gobbled up by toolkit

@Jeffrey Wagner @Joshua Horton

Smarty

TBD, if considered within org

 

Taproom

TBD, if considered within org

@Jeffry Setiadi

PLBenchmarks software

TBD (talk with stakeholders, maybe eventually)

@David Hahn

PLBenchmarks data

TBD (talk with stakeholders, maybe eventually)

@David Hahn

choderalab/perses

TBD (talk with stakeholders, probably no)

 

choderalab/freeenergyframework

TBD (talk with stakeholders, probably no)

 

choderalab/gimlet

TBD (talk with stakeholders, probably no)

 

openbenchmark

Probably do not move (no value)

@Jaime Rodríguez-Guerra