Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The submission instructions are not clear #11

Open
karthik opened this issue Jul 26, 2020 · 9 comments
Open

The submission instructions are not clear #11

karthik opened this issue Jul 26, 2020 · 9 comments

Comments

@karthik
Copy link
Member

karthik commented Jul 26, 2020

Hi EICs,
I just handled my first submission using these new instructions. I followed the readme closely but was confused the whole time. I get it now.

Things that are not clear:

  • Do I copy the article.pdf and metadata.yaml here and then run the scripts? OR
  • Do I copy the scripts over to the forked author repo and run it there?

This wasn't clear to me. I now realize I should have done the first and not the second.

Here is my first take on a revised README: https://gist.github.com/karthik/3907aae7b96a4d23ed885e78cc146804

Is this useful? Should I submit this as a pull-request?

@pdebuyl
Copy link
Member

pdebuyl commented Jul 30, 2020

Hello @karthik

I think that a PR will be welcome. I did just fine with the current instructions once I realized that they were location in the "articles" repository and not in the "edit" page of the website, which would warrant a PR to the website repo. Your proposal makes several steps more explicit, which is a good thing.

@oliviaguest
Copy link
Member

This stuff all confuses/d me too, so yes, please do the PR if you can.

@karthik
Copy link
Member Author

karthik commented Aug 3, 2020

Thanks both. I opened a PR.

@karthik
Copy link
Member Author

karthik commented Aug 3, 2020

You can see the rendered readme here

@rougier
Copy link
Member

rougier commented Aug 4, 2020

Thanks @karthik, it is much much better. And a bit scary bacause I realized there are 14 steps... I wrote the script to automatize things but now I realize it needs to be automatized mich more. In the meantime we are planning to move to JOSS infrastucture so maybe this full automatization is not needed.

@karthik
Copy link
Member Author

karthik commented Aug 4, 2020

In the meantime we are planning to move to JOSS infrastucture so maybe this full automatization is not needed.

That's great to hear and also want I came to suggest. Let me know if you need any help. I have a grant to generalize JOSS for use at rOpenSci but I'm sure we can also roll it out for ReScience easily, unless you've already kicked off that process.

@rougier
Copy link
Member

rougier commented Aug 4, 2020

That would be awsome. I did not started anything yet and I'm not sure where to start actually.

@karthik
Copy link
Member Author

karthik commented Aug 4, 2020

In that case I will start a email thread with Arfon Smith and the engineer we've hired to work on this.

@khinsen
Copy link
Contributor

khinsen commented Aug 5, 2020

@karthik This sounds excellent. We were a bit stuck with the idea of adopting the JOSS infrastructure because we didn't really know where to start and what to expect in terms of effort. Doing this in parallel with rOpenSci would certainly make this a lot easier!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants