it isn’t clear to me what you mean by “archiving the Wiki.” Could you please clarify this? This needn’t be an either/or choice.
I mean turning it into a read-only archive, as mentioned by @sclv. The idea being that there is valuable knowledge that needs to be preserved, but so many articles are so out of date that any effort to get the wiki back up to date would be at this point nearly impossible. And those articles vastly outnumber the gems. So making the wiki read-only, and curating the immutably useful articles would be i our best interest.
Wikis are not meant to host official content. I’m not suggesting that the Haskell wiki should be used for this purpose.
Unfortunately, this happened, and that’s part of the problem. Sometime in the past, it was used for Hackage announcements, package tutorials, etc etc, and it spiraled into something less useful than we want it to be.
However, I still believe that the Haskell wiki can be a useful place to collect “organic” content that users generate and allow other users to edit (I categorically reject @Nycticorax’s statement that “wikis are a ‘poisoned gift’ to offer the community.”)
FWIW, i disagree with @Nycticorax’s comment as well - I’m much more sympathetic than that, considering I got my start in the Typeclassopedia and other great articles!
I think this will expose my bias: I don’t think wikis serve a purpose beyond aggregating immutable data (this is rarely the case for software), but we’re past that point. Even implementation-specific GHC pages, like the performance-oriented wiki articles are completely out of date and actually liable to get people into trouble, or turned around in the wrong direction.
There are better ways of aggregating and indexing blog posts/announcements/etc. For example, we have Planet Haskell which does this.
I have the sense that the Haskell wiki isn’t expensive to maintain (Is this correct?), so I hope it will be kept alive and improved (for example, by linking topics to official content stored elsewhere and removing or annotating old content that no longer applies).
It’s inexpensive, sure, but for the Haskell wiki to serve a purpose, we must keep it small, immutable, and community-managed. At the moment, we are none of these things. I know you and Gershom have been great at keeping the lights on, but maintenance is not the goal here: progressive maintenance is the goal. Wikis must be kept up to date, and have janitorial processes as part of what we call maintenance.