Join the Policy Simulation Library?

[MattHJensen]

This GitHub organization (Open-Source-Economics) is becoming a home for the Policy Simulation Library, and it will be renamed PSLmodels on December 3rd. Starting then, I'd like for every project in PSLmodels to either be in PSL or be in the process of joining PSL.

TaxData is very welcome in PSL! If the project is interested in joining, could you please let me know by Dec 3 and begin (if not finish) conforming to the PSL Criteria? If the project is not interested in joining, I'll help move this repo to a different organization or remove it.

Please let me know how you'd like to proceed -- I'll be keeping an eye on this issue, and I'm also happy to join a call to discuss.

[andersonfrailey]

@MattHJensen I'd love to see TaxData in PSL. I can start working to meet the requirements this week.

[jdebacker]

The TaxData project has agreed to join PSL (as indicated by the psl-incubating status). But I thought this issue could continue to be used to see the progress that TaxData has made towards being a cataloged project:

Acceptance Criteria for Transparency and Quality

• [x] Models MUST be released under an OSI-approved open source license or the Creative Commons Public Domain Dedication (CC0).
• [x] Data MUST be publicly available, unless release is restricted by a third party.
  • Source data linked and available in repository.
• [x] For any data that SHOULD not be disclosed, provided MUST be:
  • A complete descriptive list of all data variables;
  • Descriptive statistics for all data variables for such data (including averages, standard deviations, number of observations, and correlations to other variables), to the extent that the descriptive statistics do not violate the rule against disclosure;
  • Contact information for the individual or entity who has unrestricted access to the data.
  • A complete descriptive list of all data variables;
  • Descriptive statistics for all data variables for such data (including averages, standard deviations, number of observations, and correlations to other variables), to the extent that the descriptive statistics do not violate the rule against disclosure;
  • Contact information for the individual or entity who has unrestricted access to the data.
    • All data seem available
• [x] Projects MUST have unit tests and SHOULD report code coverage.
• [ ] At least one test MUST generate key outputs from source materials, the test MUST be run with every new version, and the outputs of the test MUST be checked into the repository.
• [ ] Projects MUST report names and contact information for at least one maintainer.
• [x] Projects MUST have a suggested citation.
• [x] Projects MUST have a project overview.
  • See README
• [x] Projects MUST have installation directions.
• [x] Project MUST be mirrored in the same GitHub organization as PSL, and therefore they MUST be under version control.
• [x] Projects MUST use a consistent versioning scheme, which SHOULD be semantic versioning.

Community Criteria

• [ ] Projects SHOULD have a public roadmap.
• [ ] Projects SHOULD have contributor documentation and guidelines.
• [ ] Projects SHOULD have regular office hours, webinars, or standing meetings.
• [ ] Projects SHOULD list technical contributors.
• [ ] Projects SHOULD list funders.
• [ ] Projects SHOULD list user citations and case studies.
• [ ] Projects SHOULD include subject matter tags, choosing from ...
• [ ] Projects SHOULD include a disclaimer.
• [x] Projects SHOULD have a public issues tracker.
• [ ] Projects SHOULD have a changelog.
• [ ] Projects MAY have a Stack Overflow channel.
• [ ] Projects MAY include a "News" translation of the changelog for users.
• [ ] Projects MAY include criteria for participating in cross-model PSL initiatives.
• [ ] Projects MAY include a link to a webapp version.
• [ ] Projects MAY include a list of consultants.

Interoperability Criteria

• [x] The source code SHOULD be written in an open source language.
  • Python and Julia are used
• [ ] A PSL_catalog.json configuration file to be used for cataloging these criteria MUST be included in the project's repository. Specific instructions for creating this file can be found in the Catalog-Builder Documentation.

[jdebacker]

taxdata is in the PSL Catalog already. This issue can be closed. But you should update the tag in the "about" section on the main page of the repo to note that the project is cataloged.

cc @MattHJensen @andersonfrailey