523

submitted 10 months ago by anthonylavado@lemmy.ca to c/jellyfin@lemmy.ml

59 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] bradbeattie@lemmy.ca 45 points 10 months ago* (last edited 10 months ago)

In some cases, PRs that have no merge conflicts can sit and languish for months on end. Example: https://github.com/jellyfin/jellyfin/pull/8914. I'm not suggesting cavalierly accepting all PRs, but the devs could do a better job of communicating with prospective contributors. My desire to contribute to Jellyfin was somewhat dampened by that initial experience.

Edit: To be more constructive, I'd recommend not just a call to action (the blog post), but explicitly reaching out to devs who submitted their first PRs within the past year and finding out what their experiences were. Discovering a leaky onboarding process that you lose potential devs through could be instrumental!

[-] domi@lemmy.secnd.me 13 points 10 months ago

I know what you mean, my pull request also sat around for almost 6 months before it got merged.

Having some feedback whether something is wrong with the PR or just that nobody had time to look at it yet would go a long way.

I am once again waiting on a PR to get merged before I can continue working on mine but it seems like nobody is sharing their thoughts on PRs anymore because there is radio silence and open questions go unanswered. I'm not an expert on Jellyfin architecture so without a maintainer stepping in and telling me how it should be done I can't work on Jellyfin.

Probably a chicken an egg problem though. Without more maintainers responses are sparse and with sparse responses, less maintainers.