---- On Tue, 18 Aug 2020 19:35:05 -0500 Michael Johnson <johnsomor@gmail.com> wrote ----
Yes! ask.openstack.org is no fun to attempt to be helpful on (see e-mail notification issues, etc.).
+1 on making it RO and redirect users to StackOverflow or ML(fast response)..
I would like to ask that we put together some sort of guide and/or guidence for how to use stack overflow efficiently for OpenStack questions. I.e. some well known or defined tags that we recommend people use when asking questions. This would be similar to the tags we use for the openstack discuss list.
I see that there is already a trend for "openstack-nova" "openstack-horizon", etc. This works for me.
In FC SIG, we check a set of tags for new contributors in ask.o.o [1] which we can switch to do in StackOverflow. Similarly, we can start monitoring the popular tags for project/area-specific. [1] https://wiki.openstack.org/wiki/First_Contact_SIG#Biweekly_Homework -gmann
This way we can setup notifications for these tags and be much more efficient at getting people answers.
Thanks Thierry for moving this forward!
Michael
On Tue, Aug 18, 2020 at 5:10 PM Jeremy Stanley <fungi@yuggoth.org> wrote:
On 2020-08-19 09:52:47 +1000 (+1000), Ian Wienand wrote: [...]
*If* we were to restore it now, it looks like 0.11 branch comes with an upstream Dockerfile [1]; there's lots of examples now in system-config of similar container-based production sites and this could fit in.
This makes it significantly easier than trying to build up everything it requires from scratch, and if upstream keep their container compatible (a big if...) theoretically less work to keep updated. [...]
Which also brings up another point: right now we're running it on Ubuntu Xenial (16.04 LTS) which is scheduled to reach EOL early next year, and the tooling we're using to deploy it isn't going to work on newer Ubuntu releases. Even keeping it up in a read-only state is timebound to how long we can safely keep its server online. If we switch ask.openstack.org to read-only now, I would still plan to turn it off entirely on or before April 1, 2021. -- Jeremy Stanley