Okay, so, this isn’t really about this site. It is, instead, about the planned finished site reorganization for Fedora Discussion. (This is separate from rmarko/HeeksCNC, but it’ll leave us better set up for that if we do go ahead with that.)
While the work was underway, I kept my tasklist / status here. But now I’ve moved it back to Task list for site reorganization.
This may rise to the level of an announce list post? A lot of people who participate in Discussion aren’t on devel.
Maybe an announce list post when it’s done?
Since it involves site downtime, I’d post to announce before and after. Alternatively (or better: additionally), we could ask infra to put this in the outage system so that it shows up on status.fp.o.
Outage message is a good idea, although I think the banner here will cover it pretty clearly.
My thinking on the announce-list post is: I think the notices on the site itself will be pretty visible to current users of the site. The announce list message is more to signal that things are complete and we’re set up for more growth and activity.
@mattdm, Did you take in count GOOGLE site redirect/search?
https://discussion.fedoraproject.org/admin/customize/permalinks
Maybe a silly Question/Suggestion but Really Important for this kind of taks…
Regards.,
I’ll take a look, thanks! The URLs for posts don’t contain the category, and so should stay the same with this plan. But I hadn’t considered the URLs for categories. Let me see if I can figure out if any of those have significant incoming traffic. My guess is that they aren’t likely to, or if they do that they’ll re-adjust quickly because the contents of the category view are so dynamic. But definitely worth checking!
Update! You can see I’ve checked off everything in the preliminary part. I’m going to ask Discourse to make Fedora Discussion read-only tomorrow morning and copy everything to the temporary site so I can do it for real.
Hey @mattdm how it is going so far?
Lots of boxes checked off! 
I wrote some (semi-kludgy) scripts to handle most of the work via API (Tree - discourse-site-reorg-scripts - Pagure.io) and am tweaking them as I go.
There is a queue of messages wating for aporval in discussion.fp.o about COPR repo add it daily could you please stop the script until you’ve completed your tasks… and enable it again after that…
in Projects in Copr Category…
Regards.,
Yeah I checked with Miroslav and they should just repeat once the site is out if read only mode. The messages are kind of annoying but just ignore them for now please.
Okay, I’m basically done and have asked Discourse to bring up what I did on the main site. I’m not expecting that until the morning (whew, look at the time!), but we’ll see what happens.
As you may have noticed, the re-launched site is now live!
I’m going to hold off on announcing until January 1st — those of you who happen to be around and notice can help find any problems
@mattdm do you consider enable the solved plug-in on discourse instance?
Or you can enable by tags?
,this will be useful in join tag or magazine or others team, for don’t left topic open forever.
And of course ask fedora category on discusion when the migration will be ready
Regards.,
It’s installed but I didn’t turn it on for most categories. We could do so for the Magazine and Join categories, though. It’s on for Site Help.
I don’t think it can be done on a per tag basis, but we might be able to fake that with a theme component.
Regards.,
Oh, cool! That’s awesome. I’ll definitely enable that where useful.