I have just replaced the wiki by its archive, everything seems to be in
order.
Please look around a little to try to figure out if important
information is missing
or any bugs are present before I actually delete old VM in a few weeks
likely.
Also head over to the migration issue¹ to track progress, comment and help.
[1] https://foss.heptapod.net/mercurial/mercurial-devel/-/work_items/10001
Raphaël
On 7/24/25 3:51 PM, Raphaël Gomès wrote:
Hi all,
I will try to be short and to the point (also because I have limited
time to
handle this), but just in case...
TL;DR: the wiki¹ will become a static, read-only archive available at
the same
old URLs. Pages that are still active (release notes, extensions,
etc.) will
live in the new website.
Now for the longer version:
# Why the wiki has to go
The wiki has long been more of a thorn in Mercurial's side than a
helpful asset:
- it is attacked by spammers
- it has *very* out of date information
- it uses extremely old software which is insecure and requires
insecure
dependencies
- it serves a questionable usefulness to the project in its
current state
- it is hard to discover
- it makes the project look abandoned
# How it will go
To this end, here is the plan:
- make the wiki read-only
- back up the raw wiki data just in case
- make a list of still active pages (~15 of them)
- release notes
- news
- extension pages
- contribution guides
- MissingRequirement is also important
- redirect their old URLs to their new version
- move those pages to the new website as urgency demands, but not
necessarily immediately
- new developer plans (*Plan) pages will become issues in the
Heptapod
issue tracker² (another email will follow about this)
- new sprint pages will be issues/framaforms
- setup a static archive like what we have for phab³
- remove the wiki software
# The future
From then on, changes will be made through merge requests on the
hg-website
repo⁴, using Heptapod issues as an alternative for asking for changes
as well.
If a page hasn't been ported over to the new site and you feel like it
should,
feel free to ask and contribute.
This will make it much easier to keep track of what's being said on
our domain,
sets up a review process for "untrusted" people, and basically kills
off what
makes a wiki a wiki. It is my strong opinion (and it was at least
shared with
all the people I've talked to over the years) that the wiki has no use
in our
project now that we live in the era of forges.
If anyone has a strong objection to killing off the wiki format, we
can discuss
setting up a wiki using the feature in Heptapod, but I very much doubt
its
usefulness.
I will make the wiki read-only right after sending this email and get
to work.
Thanks,
Raphaël
[1] https://wiki.mercurial-scm.org
[2] https://foss.heptapod.net/mercurial/mercurial-devel/-/issues/10000
[3] https://phab.mercurial-scm.org
[4] https://foss.heptapod.net/mercurial/hg-website
_______________________________________________
Mercurial mailing list
Mercurial@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial
_______________________________________________
Mercurial mailing list
Mercurial@lists.mercurial-scm.org
https://lists.mercurial-scm.org/mailman/listinfo/mercurial
