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

Add all epiverse-trace members as contributors #7

Open
Bisaloo opened this issue Oct 5, 2022 · 4 comments
Open

Add all epiverse-trace members as contributors #7

Bisaloo opened this issue Oct 5, 2022 · 4 comments
Labels
good first issue Good for newcomers help wanted Extra attention is needed

Comments

@Bisaloo
Copy link
Member

Bisaloo commented Oct 5, 2022

Since this repo is a template, I'm not sure if it should be expected that the DESCRIPTION file reflects the actual contributions to the repo.

From a practical point of view, I would find it very convenient to have the details (including ORCID) of all epiverse-trace members since it's usually much easier to selectively remove people than to have to find their ORCID, maybe double check how their name is spelled, etc. whenever you want to create a new package.

@Bisaloo Bisaloo changed the title Add all epiverse-trace members are contributors Add all epiverse-trace members as contributors Oct 5, 2022
@jamesmbaazam
Copy link
Member

Hi Hugo, have you decided on how to collect this information?

@Bisaloo
Copy link
Member Author

Bisaloo commented Mar 29, 2023

The simplest solution is probably for every one of us to submit a PR with our data. Would you like to be the first?

@jamesmbaazam
Copy link
Member

I will do that now.

@Bisaloo Bisaloo added good first issue Good for newcomers help wanted Extra attention is needed labels May 31, 2023
@Bisaloo Bisaloo pinned this issue Oct 5, 2023
@Bisaloo
Copy link
Member Author

Bisaloo commented Jan 15, 2024

On a related note, once this task is finished, we need to harmonize aut vs ctb in this template. It doesn't have any functional impact since this is just a template but from a documentation point of view, everyone in the team should be indicated with the same level of contribution status.

@bahadzie bahadzie unpinned this issue Feb 8, 2024
@bahadzie bahadzie pinned this issue Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants