Hey CodeMeta'ers :0 Anyone want to review my PR for the SCWG document about the codemeta crosswalk; see force11/force11-scwg#125
@cboettig@danielskatz@ashleysa (the latter two may not be in Gitter): we should try to resolve the authorship question
@kyleniemeyer@danielkatz@ashleysa indeed. open to ideas but here's one proposal for you: If no one wants to take on a leadership role in wrangling and seeing it out the door; I'm happy to cover that and play first-author. If someone (cough Kyle) wants to do that I'd love to make them first author, maybe Ashley as second, and propose I go at the end ("senior author"). We order the others by some arbitrary metric, and we say authorship order was determined by "the consensus of the workshop" if we comment on it at all. Does this sound fair?
Daniel S. Katz
As I said at the meeting, I think we either should list authors based on contribution (perhaps determined via the general consensus of the participants), or we should alphabetize (other than the lead author), as people who see a citation to the document will assume that we are doing one of these: If the order is alphabetic, it will be assumed that we used alphabetic order, and if the order is anything else, it will be assumed that we ordered according to contribution. (I can't believe I'm writing this badly while listening to a talk on bad writing)
Since @cboettig suggested it (and @danielskatz has done the lion’s share of the work on the software citation principles doc), I can take the helm on this one
(was trying to fit as many cliches in there as I could)
I agree with Dan's assessment of ordering -- first author, then alphabetical. Otherwise, it should go by order of contribution, and that is much harder to determine, especially as several people have bene working off and on on this for several years.
Daniel S. Katz
That's another good point - this shouldn't just be based on contributions to the paper but really to the whole ball of wax (trying to follow Kyle's example of the use of cliches)