-
Notifications
You must be signed in to change notification settings - Fork 19
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
F1000 Bugfixes #385
Comments
What a lovely report. Lots of good points in there |
I think this is a confusion we had at different phases and indeed we are probably not consistent (let's check the tables again, for example). I think that we have converged to "RSEs should have these", but we arrive on these points partially based on the what RSEs already have.
Probably a nice forward-reference to the institutions paper(s)? I really like the following suggestions for more text:
How do we proceed with the editing/revision? Continue editing normally here, or is that complicated to port to the system again? Do we need patches, instead? Where do we write the reply to the reviewers? |
with regards to the icons. I wonder if we should drop them for the F1000 publication and keep them for the arxiv version. a suitable latex conditional could do the trick. This might also help with the workflow for addressing the issues/suggestions raised by the reviewers:
That way we get to stick our tried and tested workflow and also update the arxiv version of the paper |
For the time being, I cannot upload a RTF, or DOC Version.... Their download is broken... |
So we now have a file from F1000. I can open it with the MS365 word version, but not with loffice.
|
I would prefer working with a rtf file to be honest |
their rtf download is broken, sorry. |
Feel free to add here, so that we can fix that when the reviews are in!
The text was updated successfully, but these errors were encountered: