Some unfixed bugs or feature requests have had many upvotes for a long time, but are still not implemented. I would like to know is there a way to expedite such implementation.

For ordinary questions on any site you can start a bounty to draw additional attention. But what if you want to see a bug report or feature request here on Stack Exchange? Per-site metas don't have bounties. Also, while MSE has bounties, as far as I can see SE employees don't want my rep.

Probably if we could start some crowdfunding project, to fund our own community developer, who would make what we want in order to make the SE network better for us. What do you think about it?

Some small bugs are annoying for me; in several cases there are already answers from other users how to implement fixes. There is even the SOUP patch, which offers client-side fixes for over a hundred bugs across the network packaged in a handy user script. The author has specifically given permission for any of those fixes to be incorporated into the SE code base. But neither of these happen and I don't know the reason.

The SE team has stated that they prefer that even trivial issues be reported, as they are "super easy and trivial to fix".

  • 1
    @rene where I can put my money for it? Nov 27, 2017 at 16:32
  • 1
    At the VC desk ...
    – rene
    Nov 27, 2017 at 16:32
  • Your question title has little to do with having a special developer in your pocket... what do you actually want?
    – Catija StaffMod
    Nov 27, 2017 at 16:33
  • @rene what is this? Nov 27, 2017 at 16:47
  • @Catija the last paragraph. Nov 27, 2017 at 16:47
  • I don't really see how that makes sense... why would SO allow someone they're not able to direct to have access to their code base to know how to change it?
    – Catija StaffMod
    Nov 27, 2017 at 16:49
  • @Catija I mean some dev inside SO, but receiving a salary from community. Nov 27, 2017 at 16:51
  • 1
    @alexolut With VC I meant Venture Capitalist. The companies that only invest for a minimum of 10 million dollars.
    – rene
    Nov 27, 2017 at 17:09
  • Companies really can't work well with staff who have divided priorities. They either need their staff doing what they need them to do... or they don't.
    – Catija StaffMod
    Nov 27, 2017 at 17:14
  • 5
    I feel this question is related to Can we have a guaranteed pipeline for responses from Stack Exchange?
    – rene
    Nov 27, 2017 at 19:10
  • I think you should check out my answer on the duplicate target. Mar 5, 2018 at 23:27

1 Answer 1


When the code compiles, it's about 20% done. Maybe 10%. The fact that somebody has posted a userscript to change a behavior is helpful, but far from sufficient.

Some additional things that need to happen:

  • Design review. That it's the behavior that you or I want doesn't mean it's right for all of SE's users. Somebody needs to review for generality, UX, localization considerations, behavior in different browsers and at different sizes, accessibility, how well it plays with different sites' designs, etc.

  • Code review, including performance and security (does this new code leak anything out of the DB that ought not be leaked?).

  • Testing.

  • Other impacts. Does this change require corresponding changes to the mobile (web) interface, apps, the API?

Now sometimes a user-submitted change really is nearly ready to go out of the box. Mi Yodeya has a Hebrew keyboard that was written by one of our users as a userscript and then adapted as a built-in feature (on selected sites) by SE. It can happen. But you can't assume that just because there's code, it's easy for SE to stick it in the code base for everybody.

So, how to prioritize? Well, SE's devs get their priorities from lots of different sources -- product management, the community team, internal initiatives, user feedback, and presumably funders. The best we can do is to make a strong case and draw attention. The strongest cases demonstrate some awareness of and consideration for all these other factors beyond just writing the code. In your feature request, be sure to describe the actual problem you're trying to solve (not just the implementation you want), what approaches you considered, why you think this is the right approach, how it interacts with all those design things I mentioned, etc.

Addendum after question edit: I do think that widely-used, minor bug fixes like those in SOUP should be considered by the team because they've been user-tested in a variety of settings and there's active maintenance. That's different from somebody posting code in an answer and saying "use this".

  • Does it really hard to fix such small things like these: one, two, three, four? All of them contain a possible solution. Nov 27, 2017 at 21:16
  • 1
    @alexolut why should such minor cosmetic issues be priorities? Nov 27, 2017 at 22:14
  • 1
    @RobertLongson because they annoying and I see them everyday. Just imagine what would you say if there was a typo in “Stack Overglow” logo. Design issues is a face of the company, it should be well-groomed. Nov 28, 2017 at 4:45
  • 1
    @alexolut Fixing them means that the developers are not fixing something more important is my point. This is called opportunity cost Nov 28, 2017 at 7:19
  • Can you please give me feedback on my answer to the duplicate target? Mar 5, 2018 at 23:31
  • @Ano that looks reasonable. I agree with the comment about bounties for FRs, and I disagree on some minor points but overall, it's a good description. Mar 6, 2018 at 3:41
  • @RobertLongson dev team could create Roadmap with priorities, so community can see, which tasks they are working on. Sep 10, 2018 at 12:46

Not the answer you're looking for? Browse other questions tagged .