Alas, I don’t think so. The Github API here has historically been kind of a pain to work with. Not sure whether it’s impossible, but I can’t think of a way of doing this.
In a deep sense, the features and projects developers work on is both socially/individually determined, as well as in the direct control of a project manager or lead.
It seems really implausible that people could directly vote on them.
A major issue is the quality of information (internet crowd). If we ignored this and the upvotes somehow perfectly reflected the omniscient, ideal preferences of the community (and things along the lines of Arrow’s theorem weren’t an issue), it would still be different than what would be worked on for idiosyncratic/personal/planning reasons.
If this would be done, it would be by the leads/manager getting this would-be feedback...and that’s sort of what Lizka/Ben West/JPA/Habryka are doing, in this very thread.
Oh god, no. We have like 400 open Github issues, most of them random backend bugs that nobody should ever really engage, and that are quite unclear to people without context of software engineering experience.
Orgs I’ve been a product manager for want this information. And the EA community is higher signal than most. So I’m curious what your posture towards it is if it was easy to obtain.
Alas, I don’t think so. The Github API here has historically been kind of a pain to work with. Not sure whether it’s impossible, but I can’t think of a way of doing this.
What if there was a post that was automatically populated with all open github issues and people could up and downvote them with karma?
Do you think that would create value for you?
In a deep sense, the features and projects developers work on is both socially/individually determined, as well as in the direct control of a project manager or lead.
It seems really implausible that people could directly vote on them.
A major issue is the quality of information (internet crowd). If we ignored this and the upvotes somehow perfectly reflected the omniscient, ideal preferences of the community (and things along the lines of Arrow’s theorem weren’t an issue), it would still be different than what would be worked on for idiosyncratic/personal/planning reasons.
If this would be done, it would be by the leads/manager getting this would-be feedback...and that’s sort of what Lizka/Ben West/JPA/Habryka are doing, in this very thread.
Oh god, no. We have like 400 open Github issues, most of them random backend bugs that nobody should ever really engage, and that are quite unclear to people without context of software engineering experience.
What if any with the label “frontend” went here?
Orgs I’ve been a product manager for want this information. And the EA community is higher signal than most. So I’m curious what your posture towards it is if it was easy to obtain.