Cleaning up the core teams #151
Replies: 5 comments 1 reply
-
my feedback: 🧹 👍 x3 - well done! Note that the April release will be a bit delayed, possibly May 🇬🇧 |
Beta Was this translation helpful? Give feedback.
-
Sounds good to me! We should be careful that we do recognize all kinds of activity, not just activity on GitHub, but also e.g. help with finding funding. |
Beta Was this translation helpful? Give feedback.
-
Would it make sense to list the members of the respective teams on our website or on readthedocs? Or are the GitHub teams sufficient? Note that we currently have this page, which would need to be updated. @ehogan recently suggested that we could write downs somewhere what people's specific skills or interests are, so it would be more clear to everyone who to contact for what. |
Beta Was this translation helpful? Give feedback.
-
I propose to keep this discussion open until the upcoming workshop in May 2024 (see #141) and then start enacting (i.e. contacting non-active members) what we decide then. |
Beta Was this translation helpful? Give feedback.
-
Perhaps for long-term (but currently inactive) contributors, a new group called something like "Founding members" could be established? |
Beta Was this translation helpful? Give feedback.
-
The ESMValTool proto-Steering Group proposes to start enforcing our no-activity policy, i.e. cleaning up the core teams and removing members who have been inactive for more than 2 years. In particular, we propose the following:
All of this would be implemented for the next release, which is currently scheduled for April 2024.
Please give us feedback on this idea and share your thoughts or concerns on this proposed cleanup.
@ESMValGroup/esmvaltool-developmentteam
@ESMValGroup/esmvaltool-coreteam
@ESMValGroup/scientific-lead-development-team
@ESMValGroup/technical-lead-development-team
@ESMValGroup/userengagementteam
Beta Was this translation helpful? Give feedback.
All reactions