Add authors to project metadata#31
Conversation
Automated Review URLs |
335f741 to
e117246
Compare
|
maybe a way forward would be
Eventually one could order by contributions to that particular spec version or some other kind of optimization. Currently it seems like it is ordered by |
|
@lubianat thanks for the feedback. One can do Which constructs the cff file from the myst.yaml. The CI just would need to make sure to also commit the built file 🤔 As for authorship I thinkthe issue with contrib is that this doesn't reflect contributions to the rfc process. In the case of rfc5, a bunch of people deserve acknowledgement, but the main contributor of the respective PR is just me ^^"
Not sure who can decide this, though. |
|
I agree, it is complex. Though the version 0.6 is different from RFC 5, so one has to consider how to balance previous contributions to the spec and the contributions to a particular version. I think that using the size of total contributions is what was done in 0.5 (https://zenodo.org/records/14755796). It may make sense to keep the simpler/straightforward heuristic for the 0.6 time frame and perhaps organize it better for 1.0. The OME meeting seems like a good moment to make these kinds of tweaks. |
Good idea 👍 It *is an ome repository after all so it seems fitting for the OME body to make this kind of decisions. |
|
My ORCID: 0000-0003-0632-8296 |
|
name: Douglas Shepherd Thanks! |
|
Hey, I am not complaining about a mention obviously, but my contribution to this repo was merely a fix to a small website bug, so I am not really sure if I should really appear as an author regarding the ngff spec. Just wanted to actively mention this and let you know that you can feel free to remove me from the author list! Thanks for all the effort you put into this |
|
@jo-mueller Can we also add @lorenzocerrone (RFC-8 co-author, so I think that qualifies under the proposed author guidelines)? |
Co-authored-by: Ziwen Liu <67518483+ziw-liu@users.noreply.github.com>
|
as a note, on the PR Review on Monday, we tentatively set May 1st as the target day for comments/changes to this PR before we merge it changes afterwards are still welcome, but will need separate PRs |
|
@bogovicj @LucaMarconato @d-v-b @will-moore @thewtex @toloudis @fcollmann @dyf @jburel @jrswedlow @ilan-gold @jbms @dstansby @sbesson @chris-allan @clbarnes @LDeakin @imagejan @glyg @xgui3783 @yarikoptic @matthewh-ebi @minnerbe @mkitti @tlambert03 @melissalinkert @jni @giovp @constantinpape @perlman @sebi06 @normanrz @virginiascarlett @tischi @vuhlmann @melonora @ivirshup @jwindhager @kevinyamauchi @yuriyzubov Just a small note: This will likely get merged next week in case you want to have your authorship here edited or removed. Also, because it came up further up (cc @JulianHn): If you want me to remove you from the authorlist I'll totally do it. But except for RFC contributions I won't triage contributions by size or impact, it'll be hard to draw a line there. So yeah, unless you explicitly raise your hand to be removed from the list it's entirely legitimate for all of you to be part of it:) |
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
No explicit removal requested - just wanted to make sure in during the discussion ! |
Co-authored-by: toloudis <toloudis@users.noreply.github.com>
Co-authored-by: Yaroslav Halchenko <debian@onerussian.com>
|
sorry for being late, my ORCID is: |
Fixes ome/ngff#315
Acknowledgement
Authors and Contributors to the ngff specification should be acknowledged for their contributions, as pointed out in ome/ngff#315. At the 2025 NGFF Hackathon in Zürich, it was suggested to use the following list as a criterion for inclusion as an author:
Authorship order
Right now, authorship for the next release is divided in two categories:
A future update to this "policy" may expand eligibility for authorship to contributions to the broader community, such as
all of which are valid and helpful, but the criteria need to be fleshed out in more clarity before adding this.