3 ms·

I had opened issues and MRs with projects that David Lord was a maintainer (since he's been handling lots of Pallet Team's open source projects now). Wasn't ver

by devy 4y ago

I had opened issues and MRs with projects that David Lord was a maintainer (since he's been handling lots of Pallet Team's open source projects now). Wasn't very impressive with his "my way or the high way" approach. Take a look them yourself: https://github.com/pallets/flask/issues?q=is%3Aissue+is%3Aclosed https://github.com/pallets/flask/issues?q=is%3Aissue+is%3Acl... I am quite disgusted by his self-congratulatory tweet like that, TBH. Those tickets that the community posts questions and asked for help, he just shut people down.

bscphil 4y ago
Issues are not a help forum, they are a way of reporting definite problems with a piece of software.
CameronNemo 4y ago
I thought you were just some disgruntled person. I clicked one of the recently closed issues at random. Oh boy. Closed without even a discussion about expected behavior and documentation, never followed up on. https://github.com/pallets/flask/issues/4653 https://github.com/pallets/flask/issues/4653
- deleted 4y ago
  [deleted]
- deleted 4y ago
  [deleted]
- JoshCole 4y ago
  Went into that expecting something terrible - but he closed the issue because his implementation of JSON parsing conforms to what is actually valid JSON. Post issue closure a documentation update was suggested. It seems pretty reasonable to me for someone to close an issue asking for a deviation from valid JSON parsing behavior and it seems unreasonable to me to expect him to have been able to fortell the future, being aware of the comment that would be brought up after this closing of the issue.
refulgentis 4y ago
I think there's been some wear and tear on your relationship with him, the tweet seems fine and I picked 5 random issues, all look like fine engagement, if not always saying yes. (Which is good! This is how you maintain a good workload)
vgel 4y ago
what, like this: https://github.com/pallets/flask/issues/4661 https://github.com/pallets/flask/issues/4661 where he straightforwardly explains the problem, why it's complex to port the whole Flask ecosystem, offers a potential solution, and invites contribution both from the asker and invites the other person in the thread to their collaboration channel? That was the first issue I clicked on, and if that's being rude I wish every maintainer was as rude.
SOLAR_FIELDS 4y ago
I came upon a similar situation recently with the guy who owns pre-commit and related projects too. Valid use cases being closed as won’t fix even though there are legitimate issues being brought up by the community. And I’ve never interacted with the person in this case, just come across issues where he has responded. I don’t blame these people for that kind of behavior though, I feel like shrugging your shoulders and saying “If you want that feature, pay to sponsor the project” is a legitimate response. I just think that actively shutting down discussion is going a little bit too far.
- Beltalowda 4y ago
  I don't know the context of the project you're talking about, but in general I think it's fine to not cover all the possible use cases, even if they're valid and reasonable – not everything needs to solve all use cases.

by devy 4y ago

bscphil 4y ago

Issues are not a help forum, they are a way of reporting definite problems with a piece of software.

CameronNemo 4y ago

I thought you were just some disgruntled person. I clicked one of the recently closed issues at random. Oh boy. Closed without even a discussion about expected behavior and documentation, never followed up on. https://github.com/pallets/flask/issues/4653 https://github.com/pallets/flask/issues/4653

deleted 4y ago
[deleted]
deleted 4y ago
[deleted]
JoshCole 4y ago
Went into that expecting something terrible - but he closed the issue because his implementation of JSON parsing conforms to what is actually valid JSON. Post issue closure a documentation update was suggested. It seems pretty reasonable to me for someone to close an issue asking for a deviation from valid JSON parsing behavior and it seems unreasonable to me to expect him to have been able to fortell the future, being aware of the comment that would be brought up after this closing of the issue.

refulgentis 4y ago

I think there's been some wear and tear on your relationship with him, the tweet seems fine and I picked 5 random issues, all look like fine engagement, if not always saying yes. (Which is good! This is how you maintain a good workload)

vgel 4y ago

what, like this: https://github.com/pallets/flask/issues/4661 https://github.com/pallets/flask/issues/4661 where he straightforwardly explains the problem, why it's complex to port the whole Flask ecosystem, offers a potential solution, and invites contribution both from the asker and invites the other person in the thread to their collaboration channel? That was the first issue I clicked on, and if that's being rude I wish every maintainer was as rude.

SOLAR_FIELDS 4y ago

I came upon a similar situation recently with the guy who owns pre-commit and related projects too. Valid use cases being closed as won’t fix even though there are legitimate issues being brought up by the community. And I’ve never interacted with the person in this case, just come across issues where he has responded. I don’t blame these people for that kind of behavior though, I feel like shrugging your shoulders and saying “If you want that feature, pay to sponsor the project” is a legitimate response. I just think that actively shutting down discussion is going a little bit too far.

Beltalowda 4y ago
I don't know the context of the project you're talking about, but in general I think it's fine to not cover all the possible use cases, even if they're valid and reasonable – not everything needs to solve all use cases.