Roundup Tracker - Issues

Issue 2551045

classification
Title: Implementing wiki move to Waldmann-EDV
Type: Severity: normal
Components: Infrastructure Versions:
process
Status: new Resolution:
Dependencies: Superseder:
Assigned To: ber Nosy List: ThomasAH, ber, rouilj
Priority: Keywords:

Created on 2019-06-03 15:23 by ber, last changed 2019-08-08 08:51 by ber.

Messages
msg6513 Author: [hidden] (ber) Date: 2019-06-03 15:23
In issue2551027 (outgoing email does not work on sourceforge when
running own wiki) we've decided to move our wiki to a new moinmoin instance
hosted at Waldmann-EDV, a specialisted MoinMo.in hoster.

This issue is about implementing the decision technically.
Open tasks transfered:

[ ] Check for additional plugins (probably none)
[ ] Check that we and our theme works on MoinMoin 1.9 (hopefully)
[ ] Cleanout spam-pages
[ ] Cleanout or think about how to cleanout (spam) users
[ ] Give clean copy to waldmann-edv
[ ] Plan migration with everyone involve
[ ] Migrate
[ ] Announce migration
[ ] Enjoy better wiki! \o/


In addition I think we may start with a runnin beta version of the wiki
before switching.
msg6521 Author: [hidden] (ber) Date: 2019-06-04 19:26
Let us start setting up the new wiki in parallel, so
   wikibeta.roundup-tracker.org
so we need to point it to the same IP as wikiwikiweb.de (213.239.209.163)
msg6522 Author: [hidden] (ber) Date: 2019-06-04 19:50
== Access to old wiki
This runs on sourceforge.net, the access is documented in 
https://sourceforge.net/p/roundup/code/ci/7a570b1f0d675c1a1807c5d6041eb35d270daf6e/tree/website/README.txt

To download the data of the wiki, scp with an sf account with the
privileges for "roundup" as to be used.

A command like this does work,
check
https://sourceforge.net/p/forge/documentation/SSH%20Key%20Fingerprints/
to allow the connection
 scp -r
ber@web.sourceforge.net:/home/project-web/roundup/persistent/wiki/data .

(However the eventlog seems to be pretty big, we won't need it fully.
So maybe I'll be using "rsync" and exclude this file.)
msg6523 Author: [hidden] (ber) Date: 2019-06-04 19:51
The theme used by the wiki is in the roundup main repo at
https://sourceforge.net/p/roundup/code/ci/default/tree/website/wiki/
msg6526 Author: [hidden] (ber) Date: 2019-06-05 15:29
[ ] come up with a list of user account (email addresses)
[ ] come with the the list of people that shall be Wiki-admins
    to be able to create user accounts.
msg6527 Author: [hidden] (ber) Date: 2019-06-05 15:31
Note https://wikibeta.roundup-tracker.org/BetaWiki
is already running as early technical preview (that will be cleaned),
but with a TLS certificate for wikiwikiweb.de.
msg6579 Author: [hidden] (rouilj) Date: 2019-07-12 00:50
Bern, I noticed one of the items on your list was to come up with a list 
of accounts. Is there something special that needs to be done to export 
the current list of users to the new instance?
msg6587 Author: [hidden] (ber) Date: 2019-08-05 09:09
Hi John,
first sorry for the long break on this issue.
There was vacation time in Germany.

To answer your question:
Current spam protection for MoinMoin wikis recommends that we
allow editors screen by a person. Given it some thought I believe this is
fine (at least for the time being). Our list of accounts probably contains
a number of fake accounts which were only created for the purpose of
spamming, thus my suggestion is that we start with a fresh manual list
and transfer those accounts.

Technically we could transfer them all, but I think it will be
suboptimal for our purposes as outlined above.

Regards,
Bernhard
msg6588 Author: [hidden] (rouilj) Date: 2019-08-07 21:34
Hi Bern:

In message <1564996160.73.0.927879820611.issue2551045@roundup.psfhosted.org>,
Bernhard Reiter writes:
>first sorry for the long break on this issue.
>There was vacation time in Germany.

No problem.

>To answer your question:
>Current spam protection for MoinMoin wikis recommends that we
>allow editors screen by a person.

So the user user applies to get editor privs through MoinMoin and some
person/people can acknowledge the request and get them access?

Should we set up the notifications to go to the devel list? That's
where the project "admins" hang out.

>Given it some thought I believe this is
>fine (at least for the time being). Our list of accounts probably contains
>a number of fake accounts which were only created for the purpose of
>spamming, thus my suggestion is that we start with a fresh manual list
>and transfer those accounts.

That works for me. Is there a way to see the most recent editor on all
the wiki pages. That may be a good initial list of users to transfer.
As I assume the most recent editor would be the person who reverted
any spam, or the last non-spam editor.

Alternatively if we have last login time, delete all users
who have not logged in in the past two years?

>Technically we could transfer them all, but I think it will be
>suboptimal for our purposes as outlined above.

I agree. Even though I think I purged a bunch of spammers a few years
ago, there are probably more in the list.

Have a great week and thanks again for working on this.

BTW do you have the info you need to move DNS records for the host
(and get an SSL cert)?
msg6589 Author: [hidden] (ber) Date: 2019-08-08 08:51
Dear John,

thanks for your remarks! Just a few comments now,
details next time I work on it.

> So the user user applies to get editor privs through MoinMoin and some
> person/people can acknowledge the request and get them access?

Not sure, I'll have to find out. Probably people have to ask on
the devel list.

> Is there a way to see the most recent editor on all
> the wiki pages. That may be a good initial list of users to transfer.

Good idea.

> Alternatively if we have last login time, delete all users
> who have not logged in in the past two years?

Also a good idea.

> BTW do you have the info you need to move DNS records for the host
> (and get an SSL cert)?

DNS record: yes (as documented, it's still Richard handling this).
TLS cert is something that I believe Waldmann-EDV will handle once
we go further.

Regards
History
Date User Action Args
2019-08-08 08:51:39bersetmessages: + msg6589
2019-08-07 21:34:28rouiljsetmessages: + msg6588
2019-08-05 09:09:20bersetmessages: + msg6587
2019-07-12 00:50:48rouiljsetnosy: + rouilj
messages: + msg6579
2019-06-05 15:31:11bersetmessages: + msg6527
2019-06-05 15:29:56bersetmessages: + msg6526
2019-06-05 04:54:08ThomasAHsetnosy: + ThomasAH
2019-06-04 19:51:49bersetmessages: + msg6523
2019-06-04 19:50:11bersetmessages: + msg6522
2019-06-04 19:26:26bersetmessages: + msg6521
components: + Infrastructure
2019-06-03 15:30:25berlinkissue2551027 superseder
2019-06-03 15:23:49bercreate