{"action":"opened","issue":{"url":"https://api.github.com/repos/openjournals/joss-reviews/issues/141","repository_url":"https://api.github.com/repos/openjournals/joss-reviews","labels_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/141/labels{/name}","comments_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/141/comments","events_url":"https://api.github.com/repos/openjournals/joss-reviews/issues/141/events","html_url":"https://github.com/openjournals/joss-reviews/issues/141","id":195901857,"number":141,"title":"[REVIEW]: vbvs.concurrent: Fitting Methods for the Functional Linear Concurrent Model","user":{"login":"whedon","id":18508068,"avatar_url":"https://avatars.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":330465313,"url":"https://api.github.com/repos/openjournals/joss-reviews/labels/review","name":"review","color":"fbca04","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-12-15T20:00:49Z","updated_at":"2016-12-15T20:00:50Z","closed_at":null,"body":"**Submitting author:** @jeff-goldsmith (<a href=\"http://orcid.org/0000-0002-6150-8997\">Jeff Goldsmith</a>)\n**Repository:** <a href=\"https://github.com/jeff-goldsmith/vbvs.concurrent\" target =\"_blank\">https://github.com/jeff-goldsmith/vbvs.concurrent</a>\n**Version:** v0.1\n**Editor:** @cMadan\n**Reviewer:** @fabian-s\n**Archive:** Pending\n\n## Status\n\n[![status](http://joss.theoj.org/papers/a3884174f17dbb9a695f7b8658887eff/status.svg)](http://joss.theoj.org/papers/a3884174f17dbb9a695f7b8658887eff)\n\nStatus badge code:\n\n```\nHTML: <a href=\"http://joss.theoj.org/papers/a3884174f17dbb9a695f7b8658887eff\"><img src=\"http://joss.theoj.org/papers/a3884174f17dbb9a695f7b8658887eff/status.svg\"></a>\nMarkdown: [![status](http://joss.theoj.org/papers/a3884174f17dbb9a695f7b8658887eff/status.svg)](http://joss.theoj.org/papers/a3884174f17dbb9a695f7b8658887eff)\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/jeff-goldsmith/vbvs.concurrent\" 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.)\n\n## Reviewer questions\n\n### Conflict of interest\n\n- [ ] 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).\n\n### General checks\n\n- [ ] **Repository:** Is the source code for this software available at the <a target=\"_blank\" href=\"https://github.com/jeff-goldsmith/vbvs.concurrent\">repository url</a>?\n- [ ] **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- [ ] **Version:** Does the release version given match the GitHub release (v0.1)?\n- [ ] **Authorship:** Has the submitting author (@jeff-goldsmith) made major contributions to the software?\n\n### Functionality\n\n- [ ] **Installation:** Does installation proceed as outlined in the documentation?\n- [ ] **Functionality:** Have the functional claims of the software been confirmed?\n- [ ] **Performance:** Have any performance claims of the software been confirmed?\n\n### Documentation\n\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- [ ] **Installation instructions:** Is there a clearly-stated list of dependencies? Ideally these should be handled with an automated package management solution.\n- [ ] **Example usage:** Do the authors include examples of how to use the software (ideally to solve real-world analysis problems).\n- [ ] **Functionality documentation:** Is the core functionality of the software documented to a satisfactory level (e.g. API method documentation)?\n- [ ] **Automated tests:** Are there automated tests or manual steps described so that the function of the software can be verified?\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\n\n### Software paper\n\n- [ ] **Authors:** Does the `paper.md` file include a list of authors with their affiliations?\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- [ ] **References:** Do all archival references that should have a DOI list one (e.g. papers, datasets, software)?\n"}}
{"actor":{"display_login":"whedon"}}