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

RIOpaper - prepare list of authors #281

Open
dimpase opened this issue Jan 23, 2019 · 5 comments
Open

RIOpaper - prepare list of authors #281

dimpase opened this issue Jan 23, 2019 · 5 comments

Comments

@dimpase
Copy link
Contributor

dimpase commented Jan 23, 2019

The list of authors for the RIOpaper is (in draft) in https://github.com/OpenDreamKit/OpenDreamKit/tree/master/Proposal/Paper
(see further details in README.md there).

Each author should get an email address - please provide them

@mikecroucher @lawrennd @minrk @videlec @haraldschilly @serge-sans-paille @saraedum
@kohlhase @alex-konovalov @VivianePons

@dimpase
Copy link
Contributor Author

dimpase commented Jan 23, 2019

@dimpase
Copy link
Contributor Author

dimpase commented Jan 23, 2019

@fangohr

@vinklein
Copy link
Contributor

@dimpase
Hi, my contact info is updated here #284

@marijanbeg
Copy link
Contributor

List reviewed and updated for XFEL and UOS sites.

@pdehaye
Copy link
Contributor

pdehaye commented Jan 25, 2019

I have a philosophical problem with the idea of submitting to this type of journal what is explicitly framed as a proposal, while doing so under such an extensive list of names.

Some people were not even in the picture by the time the money was on the bank accounts, since they were hired later. This is not at all an attempt to fight for authorship/credits. I am just concerned this might give the wrong impression on the amount of work necessary in preparing a proposal.

I suggest:

  • keeping the idea of an extensive list of authors;
  • a paragraph to be added explaining the rationale for doing so;
  • some "footnote ticks" affording basic categorization of the roles of each of us (PI, administrative assistant, RSE, etc), as well as formal affiliations;
  • to add a section on "how the proposal has turned out", i.e. a narrative description of the twists and turns of career changes, etc, and how we could have made the proposal better in hindsight (how we were stupid and tied our hands, how we were clever and didn't, where the commission let us change the agreement, etc);
  • choose a title that reflects this dynamic perspective on the initial proposal;
  • not going overboard with additional work.

If the paper was written as such, I think it would be very useful in the future to build new consortia. I don't mean the narrow part of writing a good proposal. I mean the part where you approach an entity that has never participated in such consortia and convince them to do so, overcoming instinctive fear of the administrative burden of European projects.

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

4 participants