it’s not trivial. it means storing the pronouns field in the database separately from the display name and then updating frontends. and there’s issues with length limits that have to be sorted out. I’m also not sure if the lemmy devs would accept the PR as they seemed kinda sour on the idea of adding pronoun tags when it got suggested in an issue.
So somebody makes it, they send the change over using a pull-request, and the other side has the choice of accepting it declining it?
yes
Why wouldn’t they just trust our devs? They’re clearly competent.
it’s not really about that. it’s a process thing to make sure changes are well-thought through, do what they’re purported to do, and don’t have any knock-on effects that would be unexpected. the model is used in basically all forms of software development – most projects use them even for core devs. people only push changes directly into the repo when there’s an emergency and something needs to be fixed immediately.
I know nothing about tech, is that an easy thing? Based on context I assume it’s not an arduous thing.
it’s not trivial. it means storing the pronouns field in the database separately from the display name and then updating frontends. and there’s issues with length limits that have to be sorted out. I’m also not sure if the lemmy devs would accept the PR as they seemed kinda sour on the idea of adding pronoun tags when it got suggested in an issue.
By PR do you mean public relations? I’ve seen many comments saying they are comrades. Hopefully the sourness was only because of the amount of work?
pull-request, it’s how code changes are reviewed, tested, and accepted. here’s a link to the issue so you can read it for yourself
So somebody makes it, they send the change over using a pull-request, and the other side has the choice of accepting it declining it?
Our devs were kinda crucial in improving lemmy because of how active we are iirc
Why wouldn’t they just trust our devs? They’re clearly competent.
yes
it’s not really about that. it’s a process thing to make sure changes are well-thought through, do what they’re purported to do, and don’t have any knock-on effects that would be unexpected. the model is used in basically all forms of software development – most projects use them even for core devs. people only push changes directly into the repo when there’s an emergency and something needs to be fixed immediately.
That makes sense. Thank you for explaining.