Anthony Lavado@lemmy.caM to Jellyfin: The Free Software Media System@lemmy.mlEnglish · 1 year agoA Call for Developersjellyfin.orgexternal-linkmessage-square59fedilinkarrow-up1529arrow-down18cross-posted to: selfhosted@lemmit.online
arrow-up1521arrow-down1external-linkA Call for Developersjellyfin.orgAnthony Lavado@lemmy.caM to Jellyfin: The Free Software Media System@lemmy.mlEnglish · 1 year agomessage-square59fedilinkcross-posted to: selfhosted@lemmit.online
minus-squaregardner@lemmy.nzlinkfedilinkEnglisharrow-up39arrow-down7·edit-21 year agoI submitted a pull request that was shut down and the only feedback was “I don’t think this is the way we’d do it.” I know managing community contributions is a big task but if you want people to volunteer, a baseline amount of effort should be made to enable it. It’s also helpful to have automated tests to increase confidence that a change won’t break existing features.
minus-squareredfellow@sopuli.xyzlinkfedilinkEnglisharrow-up8·1 year agoThere was a baseline effort there. Your PR wasn’t a proper fix, but more of a hack which also isn’t in line with how a proper UI would display things.
minus-squarelud@lemm.eelinkfedilinkEnglisharrow-up15·1 year agoThey are probably talking about this one: https://github.com/jellyfin/jellyfin-web/pull/3522
I submitted a pull request that was shut down and the only feedback was “I don’t think this is the way we’d do it.”
I know managing community contributions is a big task but if you want people to volunteer, a baseline amount of effort should be made to enable it.
It’s also helpful to have automated tests to increase confidence that a change won’t break existing features.
There was a baseline effort there. Your PR wasn’t a proper fix, but more of a hack which also isn’t in line with how a proper UI would display things.
Link?
They are probably talking about this one: https://github.com/jellyfin/jellyfin-web/pull/3522