|
|
|
|
|
|
by franciscop
1250 days ago
|
|
|
I explained the other day to a friend how Prisma looks great but it's very unresponsive on Github [1], specially surprising since they raised a lot of money so I thought they'd have more resources. So he introduced me to the concept of FOSS-washing (in relation to greenwashing). Launch a cool open source piece of software, get big clients and funding thanks to it and then basically ignore Github or just dedicate enough resources to it so that it doesn't seem "dead". I had seen and complained about this before here in HN, how when Github said they were sunsetting Atom for lack of engagement I pointed out that the lack of engagement was... by them, not a single commit in few years so of course there was no activity [2] Edit: looking at the Github tracker now, it seems that now they use Github as the main tracking software? So there's a bunch of new issues by internal contributors with "bad description" (meaning it's probably the tip of the iceberg of an internal issue just for tracking, not the typical issue someone finds and reports), but the old ones sit there unanswered. [1] https://github.com/prisma/prisma/issues/4433 [2] https://news.ycombinator.com/item?id=31670443 |
|
|
For example, I want to add ltree support to Prisma (which could also extend to MSSQL’s Hierarchy). I’ve shepherded this whole thing through at least 4 repos, adding the necessary pieces in order to make it work.
Their communication and follow up has been generally poor. The engineers they have on staff are capable but they either don’t see the value in larger OSS contributions or don’t have the time to manage both the internal and external roadmapping?
Idk, I just want my PRs reviewed and merged lol