{"action":"created","issue":{"url":"https://api.github.com/repos/openjournals/joss-reviews/issues/1721","repository_url":"https://api.github.com/repos/openjournals/joss-reviews","labels_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/1721/labels{/name}","comments_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/1721/comments","events_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/1721/events","html_url":"https://github.com/openjournals/joss-reviews/issues/1721","id":491745089,"node_id":"MDU6SXNzdWU0OTE3NDUwODk=","number":1721,"title":"[REVIEW]: MiSTree: a Python package for constructing and analysing Minimum Spanning Trees","user":{"login":"whedon","id":18508068,"node_id":"MDQ6VXNlcjE4NTA4MDY4","avatar_url":"https://avatars3.githubusercontent.com/u/18508068?v=4","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":330465313,"node_id":"MDU6TGFiZWwzMzA0NjUzMTM=","url":"https://api.github.com/repos/openjournals/joss-reviews/labels/review","name":"review","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":{"login":"xuanxu","id":6528,"node_id":"MDQ6VXNlcjY1Mjg=","avatar_url":"https://avatars3.githubusercontent.com/u/6528?v=4","gravatar_id":"","url":"https://api.github.com/users/xuanxu","html_url":"https://github.com/xuanxu","followers_url":"https://api.github.com/users/xuanxu/followers","following_url":"https://api.github.com/users/xuanxu/following{/other_user}","gists_url":"https://api.github.com/users/xuanxu/gists{/gist_id}","starred_url":"https://api.github.com/users/xuanxu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xuanxu/subscriptions","organizations_url":"https://api.github.com/users/xuanxu/orgs","repos_url":"https://api.github.com/users/xuanxu/repos","events_url":"https://api.github.com/users/xuanxu/events{/privacy}","received_events_url":"https://api.github.com/users/xuanxu/received_events","type":"User","site_admin":false},"assignees":[{"login":"xuanxu","id":6528,"node_id":"MDQ6VXNlcjY1Mjg=","avatar_url":"https://avatars3.githubusercontent.com/u/6528?v=4","gravatar_id":"","url":"https://api.github.com/users/xuanxu","html_url":"https://github.com/xuanxu","followers_url":"https://api.github.com/users/xuanxu/followers","following_url":"https://api.github.com/users/xuanxu/following{/other_user}","gists_url":"https://api.github.com/users/xuanxu/gists{/gist_id}","starred_url":"https://api.github.com/users/xuanxu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xuanxu/subscriptions","organizations_url":"https://api.github.com/users/xuanxu/orgs","repos_url":"https://api.github.com/users/xuanxu/repos","events_url":"https://api.github.com/users/xuanxu/events{/privacy}","received_events_url":"https://api.github.com/users/xuanxu/received_events","type":"User","site_admin":false},{"login":"zonca","id":383090,"node_id":"MDQ6VXNlcjM4MzA5MA==","avatar_url":"https://avatars3.githubusercontent.com/u/383090?v=4","gravatar_id":"","url":"https://api.github.com/users/zonca","html_url":"https://github.com/zonca","followers_url":"https://api.github.com/users/zonca/followers","following_url":"https://api.github.com/users/zonca/following{/other_user}","gists_url":"https://api.github.com/users/zonca/gists{/gist_id}","starred_url":"https://api.github.com/users/zonca/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/zonca/subscriptions","organizations_url":"https://api.github.com/users/zonca/orgs","repos_url":"https://api.github.com/users/zonca/repos","events_url":"https://api.github.com/users/zonca/events{/privacy}","received_events_url":"https://api.github.com/users/zonca/received_events","type":"User","site_admin":false},{"login":"melissawm","id":3949932,"node_id":"MDQ6VXNlcjM5NDk5MzI=","avatar_url":"https://avatars2.githubusercontent.com/u/3949932?v=4","gravatar_id":"","url":"https://api.github.com/users/melissawm","html_url":"https://github.com/melissawm","followers_url":"https://api.github.com/users/melissawm/followers","following_url":"https://api.github.com/users/melissawm/following{/other_user}","gists_url":"https://api.github.com/users/melissawm/gists{/gist_id}","starred_url":"https://api.github.com/users/melissawm/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/melissawm/subscriptions","organizations_url":"https://api.github.com/users/melissawm/orgs","repos_url":"https://api.github.com/users/melissawm/repos","events_url":"https://api.github.com/users/melissawm/events{/privacy}","received_events_url":"https://api.github.com/users/melissawm/received_events","type":"User","site_admin":false}],"milestone":null,"comments":39,"created_at":"2019-09-10T15:27:05Z","updated_at":"2019-10-16T23:13:29Z","closed_at":null,"author_association":"COLLABORATOR","body":"**Submitting author:** @knaidoo29 (<a href=\"http://orcid.org/0000-0002-9182-1802\">Krishna Naidoo</a>)\n**Repository:** <a href=\"https://github.com/knaidoo29/mistree\" target =\"_blank\">https://github.com/knaidoo29/mistree</a>\n**Version:** v1.0\n**Editor:** @xuanxu\n**Reviewer:** @melissawm, @zonca\n**Archive:** Pending\n\n## Status\n\n[![status](https://joss.theoj.org/papers/461d79e9e5faf21029c0a7b1c928be28/status.svg)](https://joss.theoj.org/papers/461d79e9e5faf21029c0a7b1c928be28)\n\nStatus badge code:\n\n```\nHTML: <a href=\"https://joss.theoj.org/papers/461d79e9e5faf21029c0a7b1c928be28\"><img src=\"https://joss.theoj.org/papers/461d79e9e5faf21029c0a7b1c928be28/status.svg\"></a>\nMarkdown: [![status](https://joss.theoj.org/papers/461d79e9e5faf21029c0a7b1c928be28/status.svg)](https://joss.theoj.org/papers/461d79e9e5faf21029c0a7b1c928be28)\n```\n**Reviewers and authors**:\n\nPlease avoid lengthy details of difficulties in the review thread. Instead, please create a new issue in the <a href=\"https://github.com/knaidoo29/mistree\" target=\"_blank\">target repository</a> and link to those issues (especially acceptance-blockers) by leaving comments 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.)\n\n## Reviewer instructions & questions\n\n@melissawm & @zonca, please carry out your review in this issue by updating the checklist below. If you cannot edit the checklist please:\n1. Make sure you're logged in to your GitHub account\n2. Be sure to accept the invite at this URL: https://github.com/openjournals/joss-reviews/invitations\n\nThe reviewer guidelines are available here: https://joss.readthedocs.io/en/latest/reviewer_guidelines.html. Any questions/concerns please let @xuanxu know.\n\n✨ **Please try and complete your review in the next two weeks** ✨ \n\n## Review checklist for @melissawm\n### Conflict of interest\n\n- [x] As the reviewer I confirm that I have read the [JOSS conflict of interest policy](https://github.com/openjournals/joss/blob/master/COI.md) and that there are no conflicts of interest for me to review this work.\n\n### Code of Conduct\n\n- [x] I confirm that I read and will adhere to the [JOSS code of conduct](https://joss.theoj.org/about#code_of_conduct).\n\n### General checks\n\n- [x] **Repository:** Is the source code for this software available at the <a target=\"_blank\" href=\"https://github.com/knaidoo29/mistree\">repository url</a>?\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?\n- [x] **Contribution and authorship:** Has the submitting author (@knaidoo29) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?\n\n### Functionality\n\n- [x] **Installation:** Does installation proceed as outlined in the documentation?\n- [x] **Functionality:** Have the functional claims of the software been confirmed?\n- [x] **Performance:** If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)\n\n### Documentation\n\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?\n- [x] **Installation instructions:** Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.\n- [x] **Example usage:** Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).\n- [x] **Functionality documentation:** Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?\n- [x] **Automated tests:** Are there automated tests or manual steps described so that the functionality of the software can be verified?\n- [x] **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\n\n### Software paper\n\n- [x] **Summary:** Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?\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?\n- [x] **State of the field:** Do the authors describe how this software compares to other commonly-used packages?\n- [x] **Quality of writing:** Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?\n- [x] **References:** Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper [citation syntax]( https://rmarkdown.rstudio.com/authoring_bibliographies_and_citations.html#citation_syntax)?\n\n## Review checklist for @zonca\n### Conflict of interest\n\n- [x] As the reviewer I confirm that I have read the [JOSS conflict of interest policy](https://github.com/openjournals/joss/blob/master/COI.md) and that there are no conflicts of interest for me to review this work.\n\n### Code of Conduct\n\n- [x] I confirm that I read and will adhere to the [JOSS code of conduct](https://joss.theoj.org/about#code_of_conduct).\n\n### General checks\n\n- [x] **Repository:** Is the source code for this software available at the <a target=\"_blank\" href=\"https://github.com/knaidoo29/mistree\">repository url</a>?\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?\n- [x] **Contribution and authorship:** Has the submitting author (@knaidoo29) made major contributions to the software? Does the full list of paper authors seem appropriate and complete?\n\n### Functionality\n\n- [x] **Installation:** Does installation proceed as outlined in the documentation?\n- [x] **Functionality:** Have the functional claims of the software been confirmed?\n- [x] **Performance:** If there are any performance claims of the software, have they been confirmed? (If there are no claims, please check off this item.)\n\n### Documentation\n\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?\n- [x] **Installation instructions:** Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.\n- [x] **Example usage:** Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).\n- [x] **Functionality documentation:** Is the core functionality of the software documented to a satisfactory level (e.g., API method documentation)?\n- [x] **Automated tests:** Are there automated tests or manual steps described so that the functionality of the software can be verified?\n- [x] **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\n\n### Software paper\n\n- [ ] **Summary:** Has a clear description of the high-level functionality and purpose of the software for a diverse, non-specialist audience been provided?\n- [ ] **A statement of need:** Do the authors clearly state what problems the software is designed to solve and who the target audience is?\n- [ ] **State of the field:** Do the authors describe how this software compares to other commonly-used packages?\n- [ ] **Quality of writing:** Is the paper well written (i.e., it does not require editing for structure, language, or writing quality)?\n- [ ] **References:** Is the list of references complete, and is everything cited appropriately that should be cited (e.g., papers, datasets, software)? Do references in the text use the proper [citation syntax]( https://rmarkdown.rstudio.com/authoring_bibliographies_and_citations.html#citation_syntax)?\n\n"},"comment":{"url":"https://api.github.com/repos/openjournals/joss-reviews/issues/comments/542928725","html_url":"https://github.com/openjournals/joss-reviews/issues/1721#issuecomment-542928725","issue_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/1721","id":542928725,"node_id":"MDEyOklzc3VlQ29tbWVudDU0MjkyODcyNQ==","user":{"login":"knaidoo29","id":24586977,"node_id":"MDQ6VXNlcjI0NTg2OTc3","avatar_url":"https://avatars1.githubusercontent.com/u/24586977?v=4","gravatar_id":"","url":"https://api.github.com/users/knaidoo29","html_url":"https://github.com/knaidoo29","followers_url":"https://api.github.com/users/knaidoo29/followers","following_url":"https://api.github.com/users/knaidoo29/following{/other_user}","gists_url":"https://api.github.com/users/knaidoo29/gists{/gist_id}","starred_url":"https://api.github.com/users/knaidoo29/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/knaidoo29/subscriptions","organizations_url":"https://api.github.com/users/knaidoo29/orgs","repos_url":"https://api.github.com/users/knaidoo29/repos","events_url":"https://api.github.com/users/knaidoo29/events{/privacy}","received_events_url":"https://api.github.com/users/knaidoo29/received_events","type":"User","site_admin":false},"created_at":"2019-10-16T23:13:29Z","updated_at":"2019-10-16T23:13:29Z","author_association":"NONE","body":"Hi @xuanxu, possibly a dumb question but just to clarify does the title have to be the title of the paper or title of the code?"}}
{"actor":{"display_login":"knaidoo29"}}