Wiki i18n/l10n Setup #609
Labels
No labels
announcement
anubis
authentication
aws
backlog
blocked
bodhi
ci
cloud
communishift
copr
database
day-to-day
dc-move
deprecated
dev
discourse
dns
downloads
easyfix
epel
firmitas
forgejo_migration
Gain
High
Gain
Low
Gain
Medium
gitlab
greenwave
hardware
help wanted
high-trouble
koji
koschei
lists
low-trouble
medium-trouble
mirrorlists
monitoring
Needs investigation
odcs
OpenShift
ops
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
release-monitoring
releng
request-for-resources
s390x
security
SMTP
sprint-0
sprint-1
src.fp.o
staging
unfreeze
waiverdb
websites-general
wiki
Backlog Status
Needs Review
Backlog Status
Ready
chore
documentation
points
01
points
02
points
03
points
05
points
08
points
13
Priority
High
Priority
Low
Priority
Medium
Sprint Status
Blocked
Sprint Status
Done
Sprint Status
In Progress
Sprint Status
Review
Sprint Status
To Do
Technical Debt
Work Item
Bug
Work Item
Epic
Work Item
Spike
Work Item
Task
Work Item
User Story
No milestone
No project
No assignees
7 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
infra/tickets#609
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Since Mediawiki isn't MoinMoin, we need a different way to do i18n/l10n, this would mean setting up separate wiki's, this needs to be coordinated etc which I'm happy to do.
Steps that I can see that we need to do is:
{{{
14:35 < mmcgrath> well lang.fp.o got a firm "no" last I asked. Well, actually
a firm "not right now"
14:36 < ianweller> mmcgrath: so does the other url setup work for you?
14:37 < mmcgrath> yeah
14:37 < mmcgrath> do we want /en/wiki/ or /wiki/en/
14:37 < mmcgrath> I suppose we already have the /en/ convention
14:37 < G> I like en/wiki
14:38 < G> fp.o -> fp.o/en/
14:38 < G> fp.o/wiki -> fp.o/en/wiki
14:38 < G> de.fp.o -> fp.o/de etc
}}}
Personally, I can't believe I could do it so quickly...
Features/Whizbangs:
I think the /xx/w/skins/ folder in htaccess can be all pointed to a common folder...
Configs are on publictest1:
I give this about a +10!
Just a slight update, I've made a couple of changes, common settings are now at {{{/var/www/njwiki/common.php}}}, HNP etc works okay so everything seems to be fine for implementation. (I like it this way too but a more suitable location may be /etc/wiki.common.php or something.
My only comment would be, that before we setup any alternative language interwikis, https://fedoraproject.org/wiki/MediaWiki:Sidebar and the Main_Page is 'translated'.
Thoughts?
Some extra pages to add to the "required before doing a new wiki", would include:
and possibly stuff like ForbiddenItems, Infrastructure/AccountSystem, L10N and L10N/Join.
Maybe even add the requirement that the static site should be translated and published before going ahead with adding a language-specific wiki (just to be sure).
Replying to [comment:3 couf]:
Anyway, an update I've been playing with puppet and publictest10 and it works (surprise, surprise).
fr wiki has it's own image stash, but if it can't find an image it will turn to en for help locating it. HNP works, Shared Interwikis work, I can't think of much more that needs doing.
I need to clean up my addwiki process and then post the code for peer review :) and then I think we are well on the way!
There would need to be a slight migration window where I think it'd be best to say to folks "look the wiki is going to be down for XX00 UTC to XX00+1 UTC as we are making these changes" just in case something goes wrong (I hope not), in addition, depending on the timing it might be an idea/possible to perform the changes during the db1 switch over.
Small update:
It's nearly ready, I want to sort out a couple of policy things etc but we are basically there.
I'll be taking a discussion to the translation list soon with what needs to be done now for furthur discussion.
Nigel, is there an update on this? I think it'd be great if we could get the ball rolling and start testing.
Err thanks for bugging me about this.
There have been a few 'changes' that effect the immediate deployment:
In addition Apache doesn't seem to like me anymore and I'd like to beat that into place first...
I think there are a couple of other things that I'm waiting on/need to do, but I can't think of them off the top of my head.
Replying to [comment:9 nigelj]:
These are related, in that one reason to get CMS is to have an ACL'd place outside of the wiki. :)
Nigel has been helpful in getting some test instances of CMSes up; we need to rally some folks to test them for feature and UI. I've been focused on project management for Docs (really for the first time), and at worst case am just going to jump on it hard toward the end of October.
REGARDLESS ... we can move the ACL'd content sooner, just to a permanent URL and give Spot a super-fast turnaround on updates from his wiki content. I can do that, at least, although I need to find out how to get my check-ins for fedoraproject.org to go live fastest.
Then we can move the ACL'd content and upgrade the MediaWiki instance independently of Docs CMS. We pretty much decided ''not'' to update the tools underneath fedoraproject.org until after F10; too late for Infra freeze, etc. That means the moving of the ACL'd material is more a procedural situation.
Nigel, let's chat with Spot next time the three of us are on IRC. I want to make sure in realtime that we get his priorities covered. He basically wants a wysiwyg method where he can control who has write access; he doesn't mind changing to a CMS that does that as long as it all fits in to FAS etc.; we might have to move all the content under e.g. Legal/* to a sandbox so he can work on it there until we get the CMS up.
Moving this to F11.
Request to add "zh" wiki for chinese documents.
We (we call ourselves FZUG) need a wiki to write documents. The main wiki does not support zh-autoconvert. Currently We have set up a test wiki here as http://wiki.fedora-zh.org/w/ , but according to Fedora leads, we should ask Infrastructure team for help, and work within Fedora Project instead of creating our own groups.
Since multiple wiki is planned, is it possible to set up "zh" wiki first?
Thanks!
Just some updates here:
I've taken another shot for:
https://.fedoraproject.org/wiki/
It works like so:
http://.fedoraproject.org has a set of Rewrites that read:
RewriteCond %{HTTP_HOST} ^(..).fedora
RewriteRule ^/wiki/(.)$ http://localhost:10001/%1/w/index.php?title=$1 [P]
RewriteCond %{HTTP_HOST} ^(..).fedora
RewriteRule ^/w/(.)$ http://localhost:10001/%1/w/$1 [P]
RewriteCond %{HTTP_HOST} ^(..).fedora
RewriteRule ^(.*)$ /srv/web/fedoraproject.org/$1 [E=prefer-language:%1]
It needs a slight modification for items like pt_BR, which I'm going to tackle now, but as apache uses the same language codes as Mediawiki we should be good.
The only issue is: I think the rewrite should be something like:
RewriteCond %{HTTP_HOST} ^(en|fr|de|pt-br).
RewriteRule ^/wiki/(.)$ http://localhost:10001/%1/w/index.php?title=$1 [P]
RewriteCond %{HTTP_HOST} ^(en|fr|de|pt-br).
RewriteRule ^/w(.)$ http://localhost:10001/%1/w$1 [P]
RewriteCond %{HTTP_HOST} ^(en|fr|de|pt-br|nl|etc).
RewriteRule ^(.*)$ /srv/web/fedoraproject.org/$1 [E=prefer-language:%1]
Followed with:
RewriteRule ^/wiki/(.)$ http://localhost:10001/en/w/index.php?title=$1 [P]
RewriteRule ^/w(.)$ http://localhost:10001/en/w$1 [P]
RewriteRule ^(.*)$ /srv/web/fedoraproject.org/$1 [E=prefer-language:en]
As the catchall for English.
Errr that looks ugly... Take 2
Just some updates here:
I've taken another shot for:
https://.fedoraproject.org/wiki/
It works like so:
http://.fedoraproject.org has a set of Rewrites that read:
{{{
RewriteCond %{HTTP_HOST} ^(..).fedora
RewriteRule ^/wiki/(.)$ http://localhost:10001/%1/w/index.php?title=$1 [P]
RewriteCond %{HTTP_HOST} ^(..).fedora
RewriteRule ^/w/(.)$ http://localhost:10001/%1/w/$1 [P]
RewriteCond %{HTTP_HOST} ^(..).fedora
RewriteRule ^(.*)$ /srv/web/fedoraproject.org/$1 [E=prefer-language:%1]
}}}
It needs a slight modification for items like pt_BR, which I'm going to tackle now, but as apache uses the same language codes as Mediawiki we should be good.
The only issue is: I think the rewrite should be something like:
{{{
RewriteCond %{HTTP_HOST} ^(en|fr|de|pt-br).
RewriteRule ^/wiki/(.)$ http://localhost:10001/%1/w/index.php?title=$1 [P]
RewriteCond %{HTTP_HOST} ^(en|fr|de|pt-br).
RewriteRule ^/w(.)$ http://localhost:10001/%1/w$1 [P]
RewriteCond %{HTTP_HOST} ^(en|fr|de|pt-br|nl|etc).
RewriteRule ^(.*)$ /srv/web/fedoraproject.org/$1 [E=prefer-language:%1]
}}}
Followed with:
{{{
RewriteRule ^/wiki/(.)$ http://localhost:10001/en/w/index.php?title=$1 [P]
RewriteRule ^/w(.)$ http://localhost:10001/en/w$1 [P]
RewriteRule ^(.*)$ /srv/web/fedoraproject.org/$1 [E=prefer-language:en]
}}}
As the catchall for English.
This is done and has been done since July. It's template based, not separate-wiki based. No additional infra required.