So since I'm also the mindshare web/design contact, I'll elaborate a bit.

In websites@ we are moving to a new system for doing the websites as part of a larger re-design, yes. The goal for F30 is just to have getfedora.org done. The other sub-sites (alt.fp.o, arm.fp.o, spins.fp.o, labs.fp.o, etc, etc, etc) can (and hopefully will) happen in the future. Our focus for F30 is getfedora.org.

Part of the worry here is probably my fault for not opening this dialogue earlier, but I held off because I wasn't sure how things were going to shape up.

I don't mean to place a lot of sudden burden on the translations team and I feel bad about it. Please don't stress about this, I'd like to get done what we can (some translation is better than no translation), but if we don't hit 90% in every language, I'm not going to cry.

I can try to answer your first two questions, I'll leave the third for the more experienced mindshare members to discuss (I'm new to this team).

what's the actual action plan until the release ?

I don't know how long the translators need to translate the strings on average. I don't want to (or intend to) trivialize the translations work here. I don't know if it's a matter of someone just going through and spending a few minutes translating all the strings into languages they know, or if it requires a lot more effort than that.

In my mind a rough plan could be:

• Get the strings we have so far into Zanata, because at least translators could start on them. (Today, ideally, but I am not sure how Zanata projects work, so I'll need some hand-holding here for initial setup).
• Let translators translate all next week. There might be new strings that come up and get added before GA, but the more we can get done sooner, the better.

do the Fedora community cares about providing localized content to users?

I think localized websites is something that is worth continuing to do, personally. Others can comment if they agree.

@codeblock could we keep going with the existing text for a little bit in order to give the translation teams some time? Or are the redesign and the new content too tightly coupled?

What I'm concerned about is a regression in our web experience. If a language at 90% translation suddenly has 25%, that's bad for our users. Do we have a sense of the traffic to the translated pages versus English?

@bcotton They are pretty tightly coupled, I think.

If someone could help me get the strings into Zanata, translators could at least start on them. That's why I sent the original trans@ email. I know I can make a project, but I don't know how to get translators to join it or so on. I was hoping somebody more experienced could set up the project, and I could just drop in the file with the source strings.

We don't have any hard stats on traffic here, but I worked with smooge to do a quick grep matching getfedora.org/<language code>/ across getfedora logs:

Here are the top 30:

1335945 en
 273402 es
 221550 zh_CN
 181919 pt_BR
 168737 de
 153366 fr
 149705 ru
 126236 en_GB
  89845 it
  77564 pl
  56867 ja
  36149 zh_TW
  32296 ko
  30953 nl
  29879 cs
  24534 tr
  23057 id
  21467 da
  21094 ar
  18445 hu
  17010 sv
  13569 el
  13307 bg
  11514 fi
  10809 uk
   8230 sk
   6937 th
   6679 nb
   6463 fa
   6145 vi

Is the new website what we can find on stg=2Egetfedora=2Eorg? Is this reall=
y ready for translation? Btw, there is some obvious bugs using mobile=2E

If uploading to zanata is the issue, here is the doc:
http://docs=2Ezanata=2Eorg/en/release/user-guide/project-maintainer-guide/
If you want contribution, please tell us where is the code=2E

I'm fine with short delay of mindshare wish it, but please set the appropr=
iate action plan=2E

Is the new website what we can find on stg=2Egetfedora=2Eorg? Is this reall=
y ready for translation? Btw, there is some obvious bugs using mobile=2E

Yes, stg.getfedora.org is what will become the new site. And yes, we're aware it's not quite mobile ready yet, @ryanlerch and I are working on that.

As far is "really ready for translation" - there's enough there that translation can start, yes. There will be new strings going forward. For example, we're not going to have the "emerging editions" content to start with (they will link to pre-existing sites like silverblue.fp.o instead). Later on (after release) when those pages show up, there will of course be new strings.

If uploading to zanata is the issue, here is the doc:
http://docs=2Ezanata=2Eorg/en/release/user-guide/project-maintainer-guide/
If you want contribution, please tell us where is the code

So I just create a new project (following that guide) and link you to it? Okay: https://fedora.zanata.org/iteration/view/websites/getfedora.org?dswid=-3753

I'm fine with short delay of mindshare wish it, but please set the appropr=
iate action plan=2E

I don't speak for all of Mindshare, but I think the action plan is "get done what can be done reasonably without stressing too much." It should be easy to do a redeploy of the site for updated translations, so getting them live quickly isn't a huge issue going forward.

Ok thanks=2E

Please keep the existing fedora website project in zanata=2E Rename the cu=
rrent getfedora component to make it clear it's the old one, lock this comp=
onent and create a new getfedora component=2E Ask Piotr drag to get the rig=
hts if you don't have it already=2E You need to be maintainer of this proje=
ct=2E

Last sentence is unclear to me=2E Current pipeline is automatic publicatio=
n of translations once per day=2E This is perfect for us like this=2E Can y=
ou confirm you'll continue this once a day publication from the first day?

We discussed this tonight and have decided:

The new website design is blocked for 2 weeks after the strings are pushed to the right place in Zanata.

@jibecfed can you help @codeblock with Zanata?

good decision, thank you all for taking care of translations <3
yes, I'm ok to help! @codeblock what's your timezone (Is see US in FAS) and where can we discusss? fedora-websites?

Evening for me are OK, after 9 PM (French time)

@jibecfed I'm US Eastern, but I tend to keep crazy hours (such is the life of a college student), so can talk pretty much whenever.

I did email @piotrdrag asking for maintainer permissions on the 'web' zanata group but haven't heard back. I'm not sure how to proceed with moving the project to that space.

@jibecfed Any update here? Can you just move the project for me, as an admin or something?

What can I do to unblock this?

For other participants
We discussed together this morning, I tested content pushed to Zanata
Codeblock/rick already did almost everything and only advices were needs
Communication to translators from rick should come soon, with expected milestones from publication on staging to production (english and translations are expected to come at the same time)

We discuss in meeting that this can count as complete

thanks for your work
can you please confirm the publication rate still is once a day?

It is really important for us to have regular updates, so we can adapt fast to content change/typo/new languages

The websites still in the fedora-websites repo are updated approximately once every 1.5 hours (build at :00 and publish at :25).

@codeblock what is the situation with the new website?