All,
Now that the 50 most active projects have been migrated to Mailman3
(available through https://mailman3.common-lisp.net/), I've disabled the
web-ui for Mailman2. This means that the page listing the available mailing
lists (https://mailman.common-lisp.net/listinfo) now forwards to mailman3's
list management page (https://mailman3.common-lisp.net/postorius). All
related entry-points for managing lists also have been disabled (meaning:
/admin, /admindb, /create, etc.).
The old archives are still available. They're listed at
https://mailman.common-lisp.net/pipermail/ (which is where they've always
been). I have no intention to remove these archives at this point, although
we may want to point users to the fact that mailman3 is where new archives
are being accumulated, especially on the thread/date index pages.
Regards,
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
All,
Yesterday and today I've migrated mailing lists named by our community
which need to be retained for future use. I will keep taking names, but
I'll now start mass migration of the 50 mailing lists which have had
activity over the last 5 years.
In the mean time, we can discuss whether we need to extend these 5 years to
8 years - or any other limit.
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
All,
Over the past years (as early as 2014, I think), there have been many times
we've seen the need to move off Mailman2: it's implemented in python2.7
which has long seen the end of its life.
The alternative has always been Mailman3, which is the technological
successor of Mailman3, but a complete rewrite. As early as its initial
release in 2015, I've been eyeballing moving to it.
Back then, there was no migration path from 2 to 3, but it was on the
roadmap, which made the choice to move or stay easy: wait for the release
which makes it possible.
A lot of time has gone by since. The situation gradually worsened, because
the migration to Mailman3 became a blocker to upgrade the operating system
on common-lisp.net: python2.7 was phased out, which means the mailman2 list
software wouldn't run on it anymore (that is, without significant
maintenance burden to maintain our own python2.7 install).
Long story short: Yesterday, I installed the containers which allow us to
run mailman3 in an isolated environment. There's a lot of tweaking to be
done, but I've been able to configure mailman3 to run alongside of
mailman2, which is a good start.
As of right now, I've started migrating to mailman3, which I'm doing in
steps:
- basic validations
- archives of defunct lists
- active mailman2 lists with configuration and archives
Before going the route of migrating active lists, I may do an assessment of
the activity of mailing lists, asking owners of mailing lists which have
gone without activity for 5 years, whether there's still an active interest.
Regards,
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
All,
As part of the migration from Mailman2 to Mailman3, I have checked which
lists are actively used. The outcome allows for some rigorous cleanup.
Out of 236 mailing lists, 180 have not had a mail added to their archives *over
the last 5 years(!)*. My proposal is to decommission these mailing lists,
meaning that only the archives will be migrated to Mailman3. These mailing
lists can always be re-instated at a later time.
Rationale for this clean-up is that some owners of the mailing lists have
fallen out of contact, causing additional work to fall on the shoulders of
the site maintainers: mailing lists require moderation of non-member posts,
where those moderation requests which can't be delivered to the list owner,
are sent to the site admins. Additionally, unused mailing lists may accrue
spam mail in their archives, lowering the value of the archive.
(Temporarily) Closing mailing lists can prevent this.
What do you think?
It concerns these lists:
alexandria-cvs
anaphora-cvs
anaphora-devel
ansi-test-cvs
ansi-test-devel
armedbear-announce
armedbear-cvs
asdf-install-devel
asdf-packaging-announce
aspiwork-pdm-cvs
aspiwork-pdm-devel
bese-devel
bordeaux-threads-announce
bordeaux-threads-ticket
boston-lisp-announce
boston-lisp-organizers
cello-devel
cells-gtk-devel
cffi-objects-cvs
cl-berkeley-db-devel
cl-bzip2-devel
cl-containers-devel
cl-dbf-cvs
cl-dwim-devel
cl-ec2-devel
cl-emb-devel
cl-facebook-devel
cl-fuse-devel
cl-glpk-devel
cl-graph-devel
cl-gsl-devel
cl-gtk2-devel
cl-heap-announce
cl-jpeg-devel
cl-json-announce
cl-kanren-trs-cvs
cl-kanren-trs-devel
cl-l10n-devel
cl-monad-macros-cvs
cl-mpi-devel
cl-muproc-devel
cl-ncurses-devel
cl-neo4j-cvs
cl-neo4j-devel
cl-openid-devel
cl-openid-ticket
cl-org-mode-devel
cl-pdf-announce
cl-pdf-devel
cl-perec-devel
cl-plus-j-announce
cl-plus-j-devel
cl-plus-ssl-cvs
cl-plus-ssl-devel
cl-pop-devel
cl-proc-devel
cl-sbml-cvs
cl-selenium-devel
cl-smtp-devel
cl-soap-devel
cl-sqlite-announce
cl-sqlite-devel
cl-store-devel
cl-table-cvs
cl-twitter-devel
cl-typesetting-announce
cl-typesetting-devel
cl-unification-devel
cl-utilities-devel
cl-walker-devel
cl-xmlspam-devel
cl-xmpp-devel
cl-yacc-ebnf-devel
clbuild-devel
cldoc-devel
cleric-announce
cleric-devel
clfswm-announce
clfswm-cvs
clfswm-devel
climacs-devel
climplayer-devel
clonsigna-announce
clonsigna-devel
closer-announce
closer-devel
clouchdb-cvs
clouchdb-devel
clsql-fluid-devel
clx-devel
cmucl-ticket
common-lisp-beginner-cvs
de-setf-amqp-cvs
definer-announce
docudown-devel
eager-future-devel
ecl-readline-devel
eclipse-devel
editor-hints-devel
elephant-devel
elephant-ticket
f2cl-ticket
fetter-devel
fiveam-announce
fset-devel
gecol-devel
ginseng-cvs
gsharp-devel
gtk-cffi-cvs
gtk-cffi-devel
heresy-devel
implementation-hackers
iolib-announce
iolib-devel
ip-interfaces-devel
isidorus-devel
kpax-devel
l-math-announce
l-math-devel
langutils-devel
lgtk-devel
lift-devel
linedit-cvs
linedit-devel
lisp-interface-library-devel
lisp-machine
lispbox-cvs
lispbox-devel
lisplab-cvs
lisplab-devel
lisppaste-devel
lisppaste-requests
lispy-devel
lmud-devel
local-time-devel
mel-base-devel
metabang-bind-devel
metacopy-devel
metatilities-base-devel
mit-cadr-cvs
mod-lisp-devel
movitz-devel
names-and-paths-devel
nixies-devel
noctool-cvs
oct-cvs
oct-ticket
pal-devel
parenscript-announce
pg-devel
plexippus-xpath-devel
protobuf-devel
python-on-lisp-devel
rfc2388-cvs
rucksack-cvs
rucksack-devel
s-xml-devel
sicl-announce
sicl-devel
slime-cvs
snow-announce
snow-cvs
snow-devel
spray-devel
teepeedee2-devel
the-feebs-war-devel
tinaa-devel
travisci
trivial-backtrace-devel
trivial-gray-streams-devel
trivial-utf-8-devel
uri-template-devel
usocket-announce
usocket-ticket
vivace-graph-devel
web4r-devel
web4r-devel-ja
xcvb-devel
xuriella-devel
zip-devel
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
All,
The clo-devel mailing list has been migrated to mailman3. For the moment
it's the only list and this message serves as a test-email to see that the
setup works.
Migration of the archives of dead lists (lists that have existed in the
past, but don't exist anymore) is on-going. While that's continuing, I'm
waiting with further migrations of active lists a bit to see whether the
new system functions properly.
Regards,
--
Bye,
Erik.
http://efficito.com -- Hosted accounting and ERP.
Robust and Flexible. No vendor lock-in.
Erik et al,
I have managed to lock myself out of the payments host. I attempted to
install ufw as a simpler interface on top of iptables and/or nftables, but
after a failed attempt at the ufw installation, I'm not able to get in at
all.
Erik: Sorry to have to ask you this especially in the middle of mailman
migration, but I think you're the only one who maybe has access to a
virtual console to the VM through hetzner. Could you have a look at the
machine (payments.common-lisp.net) and see about opening up firewall for
ssh on the standard port (I think i'm still running sshd on 22 on there)
If the VM needs to be wiped and reinstalled (hopefully not) then it won't
be the end of the world - i can certainly reinstall the payments
application -- but there are some log files on there which I would very
much like to get off the machine if possible (all under ~dcooper8/ --
transaction logs for donations and print sales etc).
Sorry again..
Dave
--
My Best,
Dave Cooper, david.cooper(a)genworks.com
genworks.com, gendl.org
+1 248-330-2979