|
|
|
|
|
by armanckeser
67 days ago
|
|
Thanks a lot! I appreciate the kind words. I do want to clarify that I think in Jellyfin-web's case, the maintainer does mean well and doesn't really have the "benevolent dictat... er, maintainer" approach. But there seems to be this defeatist argument of: we have one maintainer which means 6 months per PR and features not being merged, that I think Open Source projects could do a better job at |
|
The problem is that despite using the same DVCS for source code management, other projects insist on a hub-and-spokes development model, which does not scale.
Projects would be a lot more productive (and a lot more resilient) if they also followed a model where "The <x> maintainer hasn't accepted my pull request" just wasn't a big deal.