Beginning to believe that @Gargron doesn't want me contributing to #mastodon — he's now partially recreated three of my pull requests that I've worked on.

Xavier Levaux

@kate @thisismissem @Gargron It is so frustrating to have PR’s remaining open for long. This is the most unproductive situation.
Personally I way more prefer to review code in a synchronous manner with my peers. But with large open source projects, I understand this becomes difficult if not impossible.

Xavier Levaux

@kate @thisismissem @Gargron You can own a project or be at the origin of a project. But if you open source it, you have to play the game. If changes need to be done before being merged, give a reason, discuss, exchange and come together to some outcome.
Moving projects forward is all about collaboration.

Renaud Chaput

@wild1145 @thisismissem we merge 250-300 PRs in a good month. Yes many of those are small, but it already takes a big part of the team’s time (which is still 2.5 people). We are trying to see how to improve this but PRs are opened at a faster rate than what we manage to process, even if we focus on them. So either we should merge without reviewing as much (bad) or have more people to review them (hard)

Julian Fietkau

@thisismissem I had read about similar things happening years ago, but was really hoping the project had grown out of it. I wish you the best and I hope it can be resolved amicably still.

Emelia 👸🏻

@CatherineFlick the direction I'd probably take for bulk actions is like an "add to cart" as you review reports, then at the end you go "yeah, these were all about that spam we dealt with, close"

Emelia 👸🏻

@LeXav @kate I don't mind PRs being open a long time, but the goal should be to work towards merging them not duplicating them.

I'm quite used to waiting and know the team is short staffed, I'm happy to wait if I open something at not a good time (those PRs were trying to get into 4.3, but missed)

Emelia 👸🏻

@renchap @wild1145 right and I'm always happy to wait for reviews; what I'm not happy about is seeing stuff I put a lot of time & energy into getting duplicated for no good reason, especially when that person could've paid attention to the issues I'm working on years before I started my work, but didn't so much as even triage the tickets.

Valerie Aurora

@thisismissem @Gargron @MartinVuilleme you all might be interested in a Contributions and Credit Policy, which would lay out exactly how a project handles the case of a maintainer rewriting a contributor's code. At least everyone will know what to expect and can decide whether or not they want to contribute to the project 🫠

Thiago Holanda

I feel really sorry for you @thisismissem.

What is even more sad is to see that @Gargron doesn't even feel bothered to come out and say sorry. This is really shameful!

Thanks for raising this up to the whole fediverse.

And @Gargron, being the Founder/Lead Developer doesn't make you a god. Show some respect for people's contributions to your project and show up to give some explanation for your actions, mate!

Emelia 👸🏻

@tholanda @Gargron

The first time it happened, he apologised, but then seemingly went and did the exact same thing only a few hours later, after I'd explicitly told him I was working on allowing moderators to forward reports in a conversation where I'd said what I was working on and how different open PRs interact & why I'd made certain choices based on other work I knew was happening.

Julian Fietkau

@vaurora @thisismissem Mastodon's contribution docs have been revamped this year: https://github.com/mastodon/.github/blob/main/CONTRIBUTING.md I have no expertise on this topic but I'm reading more guidance than policies there - no judgment intended. I believe suggestions for improving this document would ideally land on @andypiper's desk.

Emelia 👸🏻

@julian @vaurora @andypiper

Yeah, those are the guidelines I follow when contributing, or at least try to.

Charlie O’Hara

@thisismissem Has @Gargron actually bothered responding to this? Because that feels like the most egregious part - him just carrying on and ignoring criticism, despite people talking openly about this toxic habit for several years now.

wendinoakland for Kamala

@stinerman @thisismissem @Gargron Deeply embedded misogyny is tough to extinguish. Someone other than Emelia needs to weigh in & see what’s what.

Emelia 👸🏻

@awfulwoman not publicly, and I know the team is discussing this situation.

Emelia 👸🏻

@wendinoakland @stinerman @Gargron I don't think this is misogyny, and I don't believe Eugen is participating in that sort of problematic behavior. Overall my interactions have generally been okay, but with room for improvement.

Erin Kissane

@thisismissem Ugh, I do not like this. ️

Julien Colomb

@renchap @wild1145 @thisismissem

Shouldn't you think about stopping any coding activity and doing only PR reviews and strategy/prioritisation ? And if you do not want to do that, I would think finding people who want to do it should be the priority.
Community work is tough, but if it is not done, the community will fade away.

One way may also be to structure the review process so you can outsource the review process to (part of) the community ?

Emelia 👸🏻

@jcolomb @renchap @wild1145 the core team can't just stop writing code, since there's a lot only they understand in the project, and they have been doing a fantastic job generally reviewing code / PRs.

It's just the progress made there keeps getting undercut by actions of Eugen.

Miah Johnson

@thisismissem I'm thankful for your work Emelia, I'm also excited for somebody to fork Mastodon.

@Gargron