Closed rabernat closed 5 years ago
Nominee: Ryan Abernathey (@rabernat) Affiliation: Department of Earth and Environmental Sciences at Columbia University / Lamont Doherty Earth Observatory
Ryan is a critical member of the community, with a unique vision for the future of data analytics in the earth and environmental sciences. Ryan's unique vision can, arguably, be considered the reason this community exists today. Ryan is not only a unique visionary in this field, but he is a driving force behind many of the community's efforts.
Nominee: Dr Niall Robinson (@niallrobinson) Affiliation: UK Met Office Rationale: Niall has been a creative and active partipant in Pangeo and in his position as Deputy Head of the UK Met Office Informatics Lab, brings a breadth of perspective informed by the diversity of climate and forecasting projects he is associated with.
Rachel Prudden (@RPrudden), Met Office, Visual Weather Developer In the years I've known her professionally, Rachel Prudden has been mainly interested in bridging the gap between technology and meteorological science. She puts considerable effort into documentation and communication, as you can see in articles linked from her Met Office page (e.g. this). She brings expertise in meteorology, machine learning and smartphone application development, which could give insight into approaches towards projects that others without such expertise might not think of.
I think she is well suited to serve the mission statement:
Our mission is to cultivate an ecosystem in which the next generation of open-source analysis tools for ocean, atmosphere and climate science can be developed, distributed, and sustained. These tools must be scalable in order to meet the current and future challenges of big data, and these solutions should leverage the existing expertise outside of the geoscience community.
Chiara Lepore (@chiaral), Lamont-Doherty Earth Observatory, Associate Research Scientist This nomination should be clear from reading this posting by Chiara. It shows many qualities I would like to see on the governing council:
Nominee: Joe Hamman (@jhamman ) Affiliation: NCAR
Joe has contributed the most to the project in terms of actual code and PRs, and has also lead the development of some critical new functionalities (i.e. Binder) within Pangeo. He knows the technical side of the platform better than anyone else and his knowledge is key to support the community and identify the feasibility of future steps. He was a major contributor to both NASA and NSF proposals, and also believed from the start in making Pangeo more accessible to the community and developed many tutorials related to both xarray (for which he is one of the core developers), and dask.
Nominee: Amanda Tan (@amanda-tan) Affiliation: University of Washington eScience
Amanda is the the UW Research Cloud Computing Cloud Technology Lead Developer. Her extensive experience with cloud deployments, particularly with JupyterHub is a great technical resource to the Pangeo community. She was an early adopter of Pangeo, deploying the Pangeo helm chart on AWS in the very early days of the project. Amanda is going to be working with Pangeo directly as the new NASA-Pangeo project. She also has an extensive background (PhD/post-doc) in the geosciences.
Nominee: Jacob Tomlinson (@jacobtomlinson ) Affiliation: Met Office
Jacab has been one of the core developers of the Pangeo system for a long time, in particular developing capabilities in cloud computing and Kubernetes. His (new) day-job is to work with Small/Medium Enterprises (SMEs) to use Met Office data, much of which will be facilitated with Pangeo. This gives him a good combination of technical expertise and experience with a unique set of users.
Nominee: Rich Signell (@rsignell-usgs), USGS
Rich was an early adopter and proponent of pangeo. Through his work at ESIP and USGS, he has helped share our efforts with a broad audience. He also led the initial deployments of Pangeo on AWS. While Rich has always positioned himself as an outsider, it is evident to me that has has become an integral part of the collaboration and a valuable member of the team.
Nominee: Kevin Paul (@kmpaul ) Affiliation: NCAR
Kevin has been intimately involved in the development of new Python-based technologies at NCAR. He was key in bringing the Pangeo community for the 2018 developers meeting hosted at NCAR. Kevin is also the PI for the NSF program Earth Cube which was designed to develop cyberinfrastructure to meet the current and future requirements of geoscientists.
A reminder to everyone that this process is set to conclude tomorrow.
Thanks for the reminder Joe! The following people have been nominated:
...and all were seconded
There were two more nominations than there are spots on the council (7). An easy place to start is with the question: does everyone who was nominated actually want to be on the council? If you were nominated but you don't actually want to serve, please say so.
If this doesn't work, we can begin the discussion of how to whittle down the list.
Well, there were actually 9 in the Fellowship. I don't think they would have succeeded with just 7...
On a more serious note and because I am completely out of the loop, is there a reason there needs be 7 instead of 9?
On a more serious note and because I am completely out of the loop, is there a reason there needs be 7 instead of 9?
No, this was somewhat arbitrary. Maybe we just keep 9? That would be the easiest option for sure! š
Iām sorry for being quiet for a while. Iām on paternity leave, but I wanted to chime in here, briefly, before disappearing again to care for my wife and new little girl.
We have seconds for all 9 people, but have all of the nominees accepted their nomination? Considering the āsignificant contributionsā requirement, I might feel like @jhamman better represents Pangeo from the NCAR side of things. So, Iād be willing to step down.
Congrats Kevin!
Iām fine with 9 or 7. But I think itās best if we have an odd number to prevent deadlocks.
Sent from my iPhone
On Nov 14, 2018, at 4:00 PM, Kevin Paul notifications@github.com wrote:
Iām sorry for being quiet for a while. Iām on paternity leave, but I wanted to chime in here, briefly, before disappearing again to care for my wife and new little girl.
We have seconds for all 9 people, but have all of the nominees accepted their nomination? Considering the āsignificant contributionsā requirement, I might feel like @jhamman better represents Pangeo from the NCAR side of things. So, Iād be willing to step down.
ā You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread.
Agreed. If anyone takes themselves out of consideration, and we have an even number left, take me out to get to an odd number, again.
I would also be happy to step down in favor of @niallrobinson (who is also on paternity leave) as he can provide more strategic insight from the Met Office viewpoint.
I'm probably more suited to the potential future technical sub-group anyway :).
Ok, we are slightly past the deadline. Here is what I propose. Both @kmpaul and @jacobtomlinson have indicated that they are willing to step back. I would slightly favor the smaller council, because then we will have a better gender balance. UK Met office also already has two other reps on the council (@niallrobinson and @RPrudden).
So I am proposing that the following council.
Would it be fair to say we have a consensus on this?
There will be ample opportunities to evolve this in the council makeup in the future.
Personally, I think this is an excellent starting council. If everyone on this list is willing to give @rabernat's comment above a thumbs up, and we have no objections, then I think we have our first council.
We are seeking nominations for the Pangeo steering council. We will have seven members.
Nomination Process
Nominations of potential steering council members can be made by anyone from the community, provided that the nominee meets the liberally defined "Contributor" criteria defined above. Self nomination is not allowed. Nominations will take the form of responses to this issue. The nomination should include:
Nominations must be "seconded" by another community member via a like (š) of the post.
Nominations will remain open until Nov. 1, 2018.
Decision Process
We will try to reach a decision by consensus, via discussion here on the issue tracker, amongst the project contributors. There is no vote. We strongly hope and expect to achieve a consensus. If a consensus cannot be reached within two weeks, the interim steering council (myself and @kmpaul) will select the seven steering council members from among the nominees. The process will be concluded by Nov. 15, 2018.
The role of the steering council is described fully in the governance document, from which I quote excerpts here.
The Steering Council
The Project will have a Steering Council that consists of Project Contributors who have produced contributions that are substantial in quality and quantity, and sustained over at least one year. The overall role of the Council is to ensure, through taking input from the Community, the long-term well-being of The Project, both technically and as a community. As The Project draws its strength from representing the Community, it strives to avoid fragmentation of the Community into separate projects, if possible.
During the everyday Project activities, Council Members participate in all discussions, code review and other Project activities as peers with all other Contributors and the Community. In these everyday activities, Council Members do not have any special power or privilege through their membership on the Council. However, it is expected that because of the quality and quantity of their contributions and their expert knowledge of The Project Software and Services that Council Members will provide useful guidance, both technical and in terms of Project direction, to potentially less experienced Contributors.
The Steering Council and its Members play a special role in certain situations. In particular, the Council may:
Council Membership
To become eligible for being a Steering Council Member an individual must be a Project Contributor who has produced contributions that are substantial in quality and quantity, and sustained over at least six months. ~Potential Council Members are nominated by Community Contributors and voted upon by the existing Council, after asking if the potential Member is interested and willing to serve in that capacity. The Council will be initially formed from the set of existing most active Project Contributors as of August, 2018.~ [That does not apply here, as we are introducing a new, ad-hoc process to populate the initial steering council.]
When considering potential Members, the Council will look at candidates with a comprehensive view of their contributions. This will include but is not limited to code, code review, infrastructure work, mailing list and chat participation, community help/building, education and outreach, design work, etc. We are deliberately not setting arbitrary quantitative metrics (like ā100 commits in this repoā) to avoid encouraging behavior that plays to the metrics rather than The Projectās overall well-being. We want to encourage a diverse array of backgrounds, viewpoints and talents in our team, which is why we explicitly do not define code as the sole metric on which Council Membership will be evaluated.
Definition of Contributors
The Project is developed by a team of distributed developers, called Contributors. Contributors are individuals who have contributed to code, code reviews, documentation, design, and infrastructure, or to mailing lists, chats, community help and community building, education and outreach, or other work in relation to one or more Project repositories. Anyone can be a Contributor. Contributors can be affiliated with any legal entity or none. Contributors participate in The Project by submitting, reviewing and discussing GitHub Pull Requests and Issues and participating in open and public Project discussions on GitHub, Gitter chat rooms and mailing lists. The foundation of Project participation is openness and transparency.
Diversity
For the purposes of this initial steering council selection, we will interpret the definition of "contributors" as liberally as possible. We seek to increase the diversity of Pangeo, and this includes providing seats for members of underrepresented groups (specifically women and people of color) on the steering council. By increasing diversity in the project leadership, we hope to encourage diversity at all levels. The Pangeo code of conduct helps ensure that our community is safe and welcoming for people of all backgrounds.