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

WEB: Remove self (Marco Gorelli) from "active maintainers" list #61163

Merged
merged 3 commits into from
Mar 25, 2025

Conversation

MarcoGorelli
Copy link
Member

This is a bit overdue, but I haven't been active (barring minor PRs) for some time. This isn't anything personal against anyone, nor against pandas, I'm just recognising that my involvement has waned, and that unfortunately I don't have capacity for pandas maintenance

Thanks everyone for having involved me, I really appreciate it. A highlight for me was meeting many of you in Basel, and on the technical side a personal highlight was working on PDEP-4 and PDEP-6

There are some changes I've made which affect 3.0, and I'm happy to be pinged and to take responsibility for them, but I can do so even just as contributor, no need for me to be in the "active maintainers" list for that

All the best 🤗

@MarcoGorelli MarcoGorelli marked this pull request as ready for review March 21, 2025 22:13
@MarcoGorelli MarcoGorelli requested a review from mroeschke as a code owner March 21, 2025 22:13
Comment on lines 140 to +142
responsibilities: "Share relevant information with the broader community, mainly via our social networks, as well as being the main point of contact between NumFOCUS and the core team."
members:
- Marco Gorelli
- datapythonista
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

wasn't sure what to put here, as removing myself would leave the team empty - @datapythonista is it ok if I put you here?

@datapythonista
Copy link
Member

Thank you Marco for all the amazing work in pandas, it's been amazing working with you and having your conttibutions. And looking forward to continue working together in what makes sense, regardless of your availability to maintain pandas.

For the workgroup, @Dr-Irv is the expert for what I know, maybe it can advice if this group should simply be removed or what's the plan with the new governance. Or if the CI and web rendering doesn't break, maybe just leave it empty. Also ok to put me there to get this merged, and we see later if needed.

For this PR, can you also remove the quansight logo image please? It was noted to me in #61121, I also forgot it. Other than that, lgtm

@Dr-Irv
Copy link
Contributor

Dr-Irv commented Mar 22, 2025

For the workgroup, @Dr-Irv is the expert for what I know, maybe it can advice if this group should simply be removed or what's the plan with the new governance. Or if the CI and web rendering doesn't break, maybe just leave it empty. Also ok to put me there to get this merged, and we see later if needed.

It's on my list to update the various teams in a few places.

For that workgroup (communications), include the following people:

@WillAyd Will Ayd
@rhshadrach Richard Shadrach
@jorisvandenbossche Joris Van den Bossche

@datapythonista datapythonista added the Web pandas website label Mar 24, 2025
@mroeschke mroeschke added this to the 3.0 milestone Mar 25, 2025
@mroeschke mroeschke merged commit 4de503d into pandas-dev:main Mar 25, 2025
42 checks passed
@mroeschke
Copy link
Member

Thanks for all the great contributions to pandas, @MarcoGorelli! Happy to have you back at any time 😄 but I know you're working on great things in the ecosystem 🚀

@MarcoGorelli
Copy link
Member Author

Thanks all, very kind and much appreciated!

(sorry I didn't get to removing the logo in time, thanks for getting this through)

@rhshadrach
Copy link
Member

Thanks for all your contributions - and pandas and everything else!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Web pandas website
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants