On Wed, Dec 14, 2016 at 08:02:57PM -0200, Athos Ribeiro wrote: > On Wed, Dec 14, 2016 at 03:42:37PM -0500, Matthew Miller wrote: > > > > Developery stuff (in my rough order of priority) > > > > - Fix the "closed: answered" reason (as I've discussed before) > > > > - Make duplicate handling useful — include voting system > > > > - Creation of a real "meta" subsite > > > > - A flagging system for issues beyond "offensive" > > > > - Insight into things like most viewed, most duplicated, and most > > upvoted questions, so we can consider creating Fedora Magazine > > articles and more formal documentation for those things. > > > > - Rework notifications so they more useful (broken down by > > categories, not punishing users for helping copy-edit questions) > > > > - Ability to put questions in need of help (for example, unclear > > with not enough information) on hold rather than closing outright > > > > - Community review queues a la Stack Exchange > > > > - Tie in better to Fedora Badges (possibly completely disable > > integrated badges) > > > > This doesn't all need to be instant, but I'd like to be moving towards > > it.... > > Why not adding it to the next GSoC then? It really seems like we need a > few very specific features. Also, it would possibly bring some potential > maintainer for ask on board. > > Of course it would have to wait until march/may, when students start > looking for projects, unless we add it to the gsoc page already and > maybe people would start working on it sooner. One of the issue we would hit here is mentoring. We do not really have someone knowing the code base well-enough to effectively mentor a student on these questions. We could likely spend some time on this, figure a way to make it working somehow but having it integrated upstream would be a different battle. And having out of tree patches isn't going to make maintainer simpler. The best would be if upstream was to accept GSoC student for these questions, but then they would have to have the time and will to do so. Pierre _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
