On Wed, Dec 14, 2016 at 06:00:58PM -0000, Josh Boyer wrote:
> However, I'm concerned about setting the precedent of paying to host
> a service. The cost to Fedora to host it is not in machine time or
> bandwidth, but in sysadmin and maintenance. Ideally, some of those
This is a good point that I hadn't considered. It wasn't really the
hosting per se that I'm interested in, but getting the service overall
into a better place, and this seemed like a possible way to do that.
But, if we were to try to directly sponsor every upstream project on
which we depend in some way, we'd use up not just our budget but pretty
much all the money in the world.
> same passionate Fedora Ask community members would step forward to
> help run the site by becoming part of FI, even if only to service
> Ask.
Okay, so.... needs here are:
Sysadminy/packager stuff:
- some more hands on deck for routine administration
- updating to newest codebase
- package as RPM?
- update ansible playbooks
- reconfiguration on site itself to better match high-load site
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....
--
Matthew Miller
<mattdm@xxxxxxxxxxxxxxxxx>
Fedora Project Leader
_______________________________________________
infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
