{"action":"closed","issue":{"url":"https://api.github.com/repos/openjournals/joss-reviews/issues/236","repository_url":"https://api.github.com/repos/openjournals/joss-reviews","labels_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/236/labels{/name}","comments_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/236/comments","events_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/236/events","html_url":"https://github.com/openjournals/joss-reviews/issues/236","id":221588202,"number":236,"title":"[REVIEW]: Brightway: An open source framework for life cycle assessment","user":{"login":"whedon","id":18508068,"avatar_url":"https://avatars0.githubusercontent.com/u/18508068?v=3","gravatar_id":"","url":"https://api.github.com/users/whedon","html_url":"https://github.com/whedon","followers_url":"https://api.github.com/users/whedon/followers","following_url":"https://api.github.com/users/whedon/following{/other_user}","gists_url":"https://api.github.com/users/whedon/gists{/gist_id}","starred_url":"https://api.github.com/users/whedon/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/whedon/subscriptions","organizations_url":"https://api.github.com/users/whedon/orgs","repos_url":"https://api.github.com/users/whedon/repos","events_url":"https://api.github.com/users/whedon/events{/privacy}","received_events_url":"https://api.github.com/users/whedon/received_events","type":"User","site_admin":false},"labels":[{"id":330461591,"url":"https://api.github.com/repos/openjournals/joss-reviews/labels/accepted","name":"accepted","color":"159818","default":false},{"id":330465313,"url":"https://api.github.com/repos/openjournals/joss-reviews/labels/review","name":"review","color":"fbca04","default":false}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":16,"created_at":"2017-04-13T14:54:29Z","updated_at":"2017-04-19T13:57:44Z","closed_at":"2017-04-19T13:57:43Z","body":"**Submitting author:** @cmutel (<a href=\"http://orcid.org/0000-0002-7898-9862\">Chris Mutel</a>)\r\n**Repository:** <a href=\"https://bitbucket.org/cmutel/brightway2\" target =\"_blank\">https://bitbucket.org/cmutel/brightway2</a>\r\n**Version:** 2.1\r\n**Editor:** @katyhuff\r\n**Reviewer:** @amoeba\r\n**Archive:** <a href=\"http://dx.doi.org/10.5281/zenodo.556145\" target=\"_blank\">10.5281/zenodo.556145</a>\r\n\r\n## Status\r\n\r\n[![status](http://joss.theoj.org/papers/6c24869ed7f1e66b3b837c31579c6fe5/status.svg)](http://joss.theoj.org/papers/6c24869ed7f1e66b3b837c31579c6fe5)\r\n\r\nStatus badge code:\r\n\r\n```\r\nHTML: <a href=\"http://joss.theoj.org/papers/6c24869ed7f1e66b3b837c31579c6fe5\"><img src=\"http://joss.theoj.org/papers/6c24869ed7f1e66b3b837c31579c6fe5/status.svg\"></a>\r\nMarkdown: [![status](http://joss.theoj.org/papers/6c24869ed7f1e66b3b837c31579c6fe5/status.svg)](http://joss.theoj.org/papers/6c24869ed7f1e66b3b837c31579c6fe5)\r\n```\r\n**Reviewers and authors**:\r\n\r\nPlease avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the <a href=\"https://bitbucket.org/cmutel/brightway2\" target=\"_blank\">target repository</a> and link to those issues (especially acceptance-blockers) in the review thread below. (For completists: if the target issue tracker is also on GitHub, linking the review thread in the issue or vice versa will create corresponding breadcrumb trails in the link target.)\r\n\r\n## Reviewer questions\r\n\r\n### Conflict of interest\r\n\r\n- [x] As the reviewer I confirm that there are no conflicts of interest for me to review this work (such as being a major contributor to the software).\r\n\r\n### General checks\r\n\r\n- [x] **Repository:** Is the source code for this software available at the <a target=\"_blank\" href=\"https://bitbucket.org/cmutel/brightway2\">repository url</a>?\r\n- [x] **License:** Does the repository contain a plain-text LICENSE file with the contents of an [OSI approved](https://opensource.org/licenses/alphabetical) software license?\r\n- [ ] **Version:** Does the release version given match the GitHub release (2.0.2)?\r\n- [x] **Authorship:** Has the submitting author (@cmutel) made major contributions to the software?\r\n\r\n### Functionality\r\n\r\n- [x] **Installation:** Does installation proceed as outlined in the documentation?\r\n- [x] **Functionality:** Have the functional claims of the software been confirmed?\r\n- [x] **Performance:** Have any performance claims of the software been confirmed?\r\n\r\n### Documentation\r\n\r\n- [x] **A statement of need:** Do the authors clearly state what problems the software is designed to solve and who the target audience is?\r\n- [ ] **Installation instructions:** Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.\r\n- [ ] **Example usage:** Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).\r\n- [x] **Functionality documentation:** Is the core functionality of the software documented to a satisfactory level (e.g. API method documentation)?\r\n- [x] **Automated tests:** Are there automated tests or manual steps described so that the function of the software can be verified?\r\n- [ ] **Community guidelines:** Are there clear guidelines for third parties wishing to 1) Contribute to the software 2) Report issues or problems with the software 3) Seek support\r\n\r\n### Software paper\r\n\r\n- [x] **Authors:** Does the `paper.md` file include a list of authors with their affiliations?\r\n- [x] **A statement of need:** Do the authors clearly state what problems the software is designed to solve and who the target audience is?\r\n- [x] **References:** Do all archival references that should have a DOI list one (e.g. papers, datasets, software)?\r\n"}}
{"actor":{"display_login":"arfon"}}