-
Notifications
You must be signed in to change notification settings - Fork 38
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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Eitsupi as co-author #307
Comments
Thank you for considering this! Could you also consider adding @etiennebacher to aut or ctb? |
I don't mind being listed or not being listed in |
+1 to @etiennebacher's comment. I'm grateful to be included as a contributor (ctb) and this corresponds to my understanding of the R package contribution conventions... but won't lose any sleep if not. I imagine the same is true for @vincentarelbundock. @sorhawell and @eitsupi as dual authors/maintainers feels very appropriate. Thanks to you both for your tireless work on this cool project! |
I looked at commit statistics and considered consistent cutoff rules. I have added only etiennerbacher as ctb as otherwise likely a handful more ctb's should be added immediately.
I will remain the 'cre'. If it becomes relevant, I don't mind swapping. |
Dear admins
@etiennebacher @grantmcdermott @eitsupi 馃巶 馃帀 馃殌
( CC @vincentarelbundock )
Measured on various variables such as commits and code-lines @eitsupi has contributed >15% . Also there are several aspects of the polars package, where eitsupi is clearly the expert.
For these reasons I argue eitsupi should be added as co-author in DESCRIPTION. If we agree, as above could be the thumb rule for future co-authorship.
The text was updated successfully, but these errors were encountered: