-
Notifications
You must be signed in to change notification settings - Fork 224
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
Adding a PyGMT team page #1212
Comments
Yes, I think it's a good way to demonstrate to people coming to the project that they can contribute, as it puts a face on the people they are interacting with. I think seeing that we're not all computer scientists encourages people who may doubt they have the skills and experience to work on the project.
For me personally, yes.
Why wouldn't this be on the PyGMT page? I think that would make more sense to someone coming to the project, as our goal is to improve our wrapper and documentation until users need only be familiar with PyGMT and not have to refer back to GMT documentation to learn the correct syntax. |
I had been looking at organizations like project Jupyter and Numpy when considering options for the placement of the teams page. For those projects, information about teams are on the organization webpages (https://jupyter.org/about and https://numpy.org/gallery/team.html) rather than inside the reference documentation for the packages (https://jupyter.readthedocs.io/en/latest/ and https://numpy.org/doc/stable/). I viewed https://www.generic-mapping-tools.org/ as the most analogous place for GMT (and possibly PyGMT/GMT-MEX/GMT.jl) teams, rather than inside the reference documentation (i.e., https://docs.generic-mapping-tools.org/latest/ and https://www.pygmt.org/latest/). |
Please note that the link https://www.generic-mapping-tools.org/team is already taken and is redirected to the https://github.com/GenericMappingTools/gmt/blob/master/AUTHORS.md file. |
I'm reopening the 3-year-old issue to post some thoughts on the "Team Gallery" page:
References: Ping @GenericMappingTools/pygmt-maintainers for thoughts. |
"PyGMT Team" as title sounds good to me.
I am fine with having different sections related to the different roles. What's about "Core Developer"? However, we should not have more then four / five sections, as there are currently ten people listed on the Team Gallery page.
pandas separates between "active maintainers" and "inactive maintainers".
This makes sense 😬. |
Yes, I agree. I also prefer to not list one person in multiple sections.
Maintainers are contributors with more permissions and more responsibilities (tasks listed in https://www.pygmt.org/dev/maintenance.html). A maintainer should be marked as "inactive" if he/she no longer manage issues, review PRs, manage releases and participate in discussions. |
I prefer the left one with three sections. I think we just need to add a few sentences explaining that distinguished contributors include current or past contributors and past maintainers. |
I submitted PR #3240 for the three-sections variant. |
Background information:
So here are my questions regarding PyGMT specifically:
Originally posted in #1113 (comment).
The text was updated successfully, but these errors were encountered: