Rescience also does everything throught github: http://rescience.github.io/

On 18 October 2016 at 15:29, Robert M. Flight <rfligh...@gmail.com> wrote:
> You could definitely do the private thing on Gitlab, but if I were going to
> do something like this I would go with completely open review.
>
> The push journal sounds similar, where submissions were managed by GitHub
>
> http://push.cwcon.org
>
> Robert
>
>
> On Tue, Oct 18, 2016, 6:22 PM Noam Ross <noam.r...@gmail.com> wrote:
>>
>> We've been running rOpenSc package submissions in a similar way for a
>> couple of years and JOSS's process is derived from ours.  The main
>> difference is (1) reviews are not anonymous, but public, so no temporary
>> accounts are created or needed, and (2) in our case the author's repo is
>> merged in after acceptance, in JOSS's case the repo is never merged in, but
>> the paper (a markdown file), is extracted from the repo and compiled by a
>> bot.
>>
>> I think the workflow you describe could be enabled by a bot similar to
>> JOSS's wheedon bot, which could extract a paper, submit it to a private
>> repository and start a review chain.  I'm not sure how to enable anonymous
>> accounts.  If every paper was a private repository within an organization,
>> then you could limit access to just the reviewers, and then extract the
>> content to show the author. This wouldn't allow them to respond in the
>> thread, though.
>>
>> On Tue, Oct 18, 2016 at 6:04 PM Damien Irving <irving.dam...@gmail.com>
>> wrote:
>>>
>>> Hi Greg,
>>>
>>> I'm pretty sure that the Journal of Open Source Software runs its entire
>>> review process through GitHub. (Although I'm not sure how many of your dot
>>> points their process covers.)
>>> http://joss.theoj.org/
>>>
>>> There are a number of Software Carpentry people involved with that
>>> journal.
>>>
>>>
>>> Cheers,
>>> Damien
>>>
>>> On Wed, Oct 19, 2016 at 8:20 AM, Greg Wilson
>>> <gvwil...@software-carpentry.org> wrote:
>>>>
>>>> Hi,
>>>>
>>>> I was speaking with a colleague last week about the possibility of using
>>>> GitHub to manage paper submissions and reviews.  The journal in question
>>>> doesn't do open/accredited reviews, so I was wondering if anyone had any
>>>> experience with the following workflow:
>>>>
>>>> - author submits paper by sending URL of public GitHub repo to journal
>>>>
>>>> - journal creates private repo and merges author's submission into
>>>>
>>>> - journal creates temporary accounts with auto-generated names for
>>>> reviewers and gives them access to the newly-created private repo
>>>>
>>>> - reviewers post comments: authors and editors can see them/respond to
>>>> them, but identities of reviewers are known only to editors
>>>>
>>>> - authors make changes in the private repo in response to reviewers'
>>>> comments, and merge from that to their public repo when they want to
>>>>
>>>> Thanks,
>>>>
>>>> Greg
>>>>
>>>> --
>>>> Dr Greg Wilson
>>>> Director of Instructor Training
>>>> Software Carpentry Foundation
>>>>
>>>> _______________________________________________
>>>> Discuss mailing list
>>>> Discuss@lists.software-carpentry.org
>>>> http://lists.software-carpentry.org/listinfo/discuss
>>>
>>>
>>> _______________________________________________
>>> Discuss mailing list
>>> Discuss@lists.software-carpentry.org
>>> http://lists.software-carpentry.org/listinfo/discuss
>>
>> _______________________________________________
>> Discuss mailing list
>> Discuss@lists.software-carpentry.org
>> http://lists.software-carpentry.org/listinfo/discuss
>
>
> _______________________________________________
> Discuss mailing list
> Discuss@lists.software-carpentry.org
> http://lists.software-carpentry.org/listinfo/discuss
_______________________________________________
Discuss mailing list
Discuss@lists.software-carpentry.org
http://lists.software-carpentry.org/listinfo/discuss

Reply via email to