Migration to Zanata

[Noriko Mizumoto]

Hi Docs team

Some of you have already noticed, we FLP (aka translation team) have
started the process of migration to new fedora.zanata.org instance from
Transifex. First all translators started to migrate in November 2014
(still going on).

It is time to migrate all projects. This is expected to start after
F21 GA. The documentation is prepared and ready at [1]. If any concern
or question, feel free to ask at zanata-devel ml.
Could you now please advise the contacts of the dedicated owners for
migration?

Package Name
anaconda-addon-development-guide
Community Services Infrastructure Security Policy
Common_Content for Publican
Defensive Coding Guide
Documentation website
docbook-locales
Accessibility Guide
Amateur Radio Guide
Burning ISOs
Cloud Guide
Fedora Cookbook
Documentation Guide
Elections Guide
FreeIPAGuide
Installation Quick Start Guide ---> depricated
Installation Guide
Fedora Jargon Buster ---> depricated
Live Images
Fedora Managing Confined Services ---> depricated
Musicians' Guide
Multiboot Guide
Networking Guide
OpenSSH Guide
Packager's Guide
Power Management Guide
Release Notes
Resource Management Guide ---> depricated
Fedora Respin Guide ---> depricated
Fedora RPM Guide ---> depricated
Security Guide
Fedora Selinux FAQ ---> depricated
Fedora Selinux Guide ---> depricated
Software Collections Guide
Software Management Guide
Storage Administration Guide
System Administrator's Guide
System Administrator's Reference Guide
Technical Notes
Translation Quick Start Guide
UEFI Secure Boot Guide
Virtualization Deployment and Administration Guide
Virtualization Getting Started Guide
Virtualization Security Guide
Wireless Guide ---> depricated
Publican branding for Fedora
rdo docs ---> depricated

Many thanks in advance.

[1]:http://zanata.org/help/

Noriko Mizumoto
Fedora Localization Project

[Petr Kovar]

On Wed, 26 Nov 2014 15:34:37 +1000
Noriko Mizumoto  wrote:
> Hi Docs team
>
> Some of you have already noticed, we FLP (aka translation team) have
> started the process of migration to new fedora.zanata.org instance from
> Transifex. First all translators started to migrate in November 2014
> (still going on).
>
> It is time to migrate all projects. This is expected to start after
> F21 GA. The documentation is prepared and ready at [1]. If any concern
> or question, feel free to ask at zanata-devel ml.
> Could you now please advise the contacts of the dedicated owners for
> migration?

Thanks for the update, Noriko.

I'm volunteering. I hope more people will step up, though. For the
migration, it would be good to have a team of 3-4 dedicated people to help
alleviate the bottleneck problem when someone becomes unavailable.

Cheers,
pk

[Noriko Mizumoto]

(2014年11月28日 04:40), Petr Kovar wrote:
> On Wed, 26 Nov 2014 15:34:37 +1000
> Noriko Mizumoto  wrote:
> > Hi Docs team
> >
> > Some of you have already noticed, we FLP (aka translation team) have
> > started the process of migration to new fedora.zanata.org instance from
> > Transifex. First all translators started to migrate in November 2014
> > (still going on).
> >
> > It is time to migrate all projects. This is expected to start after
> > F21 GA. The documentation is prepared and ready at [1]. If any concern
> > or question, feel free to ask at zanata-devel ml.
> > Could you now please advise the contacts of the dedicated owners for
> > migration?
>
> Thanks for the update, Noriko.
>
> I'm volunteering. I hope more people will step up, though. For the
> migration, it would be good to have a team of 3-4 dedicated people to help
> alleviate the bottleneck problem when someone becomes unavailable.

Hi Petr

Thank you so much for your prompt reply!
I added you as owner contact for all books. Please advise when more 
volunteers come up, so that I can add them.

I will archive the projects on or after F21 GA (archiving will block 
accepting translation at tx and make the project unsearchable).

Could you please advise the scheduled date for migration whenever ready? 
We are tracking the projects migration entirely below.

https://fedoraproject.org/wiki/L10N_Move_To_Zanata#Packages_to_Migrate

Thanks

noriko
> Cheers,
> pk

[Petr Kovar]

Hi Noriko,

On Mon, 01 Dec 2014 14:47:31 +1000
Noriko Mizumoto  wrote:
> (2014年11月28日 04:40), Petr Kovar wrote:
> > On Wed, 26 Nov 2014 15:34:37 +1000
> > Noriko Mizumoto  wrote:
> > > Hi Docs team
> > >
> > > Some of you have already noticed, we FLP (aka translation team) have
> > > started the process of migration to new fedora.zanata.org instance from
> > > Transifex. First all translators started to migrate in November 2014
> > > (still going on).
> > >
> > > It is time to migrate all projects. This is expected to start after
> > > F21 GA. The documentation is prepared and ready at [1]. If any concern
> > > or question, feel free to ask at zanata-devel ml.
> > > Could you now please advise the contacts of the dedicated owners for
> > > migration?
> >
> > Thanks for the update, Noriko.
> >
> > I'm volunteering. I hope more people will step up, though. For the
> > migration, it would be good to have a team of 3-4 dedicated people to help
> > alleviate the bottleneck problem when someone becomes unavailable.
>
> Hi Petr
>
> Thank you so much for your prompt reply!
> I added you as owner contact for all books. Please advise when more 
> volunteers come up, so that I can add them.

I'll ask around, thanks.
> I will archive the projects on or after F21 GA (archiving will block 
> accepting translation at tx and make the project unsearchable).

Ack.
> Could you please advise the scheduled date for migration whenever ready? 
> We are tracking the projects migration entirely below.
>
> https://fedoraproject.org/wiki/L10N_Move_To_Zanata#Packages_to_Migrate
> From looking at the proposed schedule plan, I think we should

aim for mid-January with the migration. This should give us enough time to
make sure TX projects have been archived and the translation effort is not
duplicated. Thoughts?

Cheers,
pk

[Noriko Mizumoto]

(2014年12月02日 03:41), Petr Kovar wrote:
> Hi Noriko,
>
> On Mon, 01 Dec 2014 14:47:31 +1000
> Noriko Mizumoto  wrote:
> > (2014年11月28日 04:40), Petr Kovar wrote:
> > > On Wed, 26 Nov 2014 15:34:37 +1000
> > > Noriko Mizumoto  wrote:
> > > > Hi Docs team
> > > >
> > > > Some of you have already noticed, we FLP (aka translation team) have
> > > > started the process of migration to new fedora.zanata.org instance from
> > > > Transifex. First all translators started to migrate in November 2014
> > > > (still going on).
> > > >
> > > > It is time to migrate all projects. This is expected to start after
> > > > F21 GA. The documentation is prepared and ready at [1]. If any concern
> > > > or question, feel free to ask at zanata-devel ml.
> > > > Could you now please advise the contacts of the dedicated owners for
> > > > migration?
> > >
> > > Thanks for the update, Noriko.
> > >
> > > I'm volunteering. I hope more people will step up, though. For the
> > > migration, it would be good to have a team of 3-4 dedicated people to help
> > > alleviate the bottleneck problem when someone becomes unavailable.
> >
> > Hi Petr
> >
> > Thank you so much for your prompt reply!
> > I added you as owner contact for all books. Please advise when more
> > volunteers come up, so that I can add them.
>
> I'll ask around, thanks.
> > I will archive the projects on or after F21 GA (archiving will block
> > accepting translation at tx and make the project unsearchable).
>
> Ack.
> > Could you please advise the scheduled date for migration whenever ready?
> > We are tracking the projects migration entirely below.
> >
> > https://fedoraproject.org/wiki/L10N_Move_To_Zanata#Packages_to_Migrate
>
> From looking at the proposed schedule plan, I think we should
> aim for mid-January with the migration. This should give us enough time to
> make sure TX projects have been archived and the translation effort is not
> duplicated. Thoughts?

Sure, it would be nice to have clear dates, so that I can inform to 
translators. If preferred, projects under docs group (aka books) in Tx 
can be archived by yourself at your preferred timing. Let me know.

For software, there are 76 projects to migrate. Having some input from 
developer, I have approached dev team with two options, 1) delegate 
auto-migration to zanata team or 2) manual self migration. Assuming 
majority of projects choose option 1), we need to schedule the migration 
work load to spread across Dec and Jan. All projects under main and 
upstream group (aka software) may be archived on same date.

Once all the dates for Software, Documentation and Websites are 
scheduled, I will inform to translators.

Thanks
noriko
> Cheers,
> pk

[Pete Travis]

On 11/25/2014 10:34 PM, Noriko Mizumoto wrote:
> Hi Docs team
>
> Some of you have already noticed, we FLP (aka translation team) have
> started the process of migration to new fedora.zanata.org instance from
> Transifex. First all translators started to migrate in November 2014
> (still going on).
>
> It is time to migrate all projects. This is expected to start after
> F21 GA. The documentation is prepared and ready at [1]. If any concern
> or question, feel free to ask at zanata-devel ml.
> Could you now please advise the contacts of the dedicated owners for
> migration?
>
> Package Name
> anaconda-addon-development-guide
> Community Services Infrastructure Security Policy
> Common_Content for Publican
> Defensive Coding Guide
> Documentation website
> docbook-locales
> Accessibility Guide
> Amateur Radio Guide
> Burning ISOs
> Cloud Guide
> Fedora Cookbook
> Documentation Guide
> Elections Guide
> FreeIPAGuide
> Installation Quick Start Guide ---> depricated
> Installation Guide
> Fedora Jargon Buster ---> depricated
> Live Images
> Fedora Managing Confined Services ---> depricated
> Musicians' Guide
> Multiboot Guide
> Networking Guide
> OpenSSH Guide
> Packager's Guide
> Power Management Guide
> Release Notes
> Resource Management Guide ---> depricated
> Fedora Respin Guide ---> depricated
> Fedora RPM Guide ---> depricated
> Security Guide
> Fedora Selinux FAQ ---> depricated
> Fedora Selinux Guide ---> depricated
> Software Collections Guide
> Software Management Guide
> Storage Administration Guide
> System Administrator's Guide
> System Administrator's Reference Guide
> Technical Notes
> Translation Quick Start Guide
> UEFI Secure Boot Guide
> Virtualization Deployment and Administration Guide
> Virtualization Getting Started Guide
> Virtualization Security Guide
> Wireless Guide ---> depricated
> Publican branding for Fedora
> rdo docs ---> depricated
>
> Many thanks in advance.
>
> Noriko Mizumoto
> Fedora Localization Project

Hi Noriko,
(sorry for posting out of order, I wanted to reply to the list of books)

FWIW, the coordinator for each of our guides are shown in
https://fedoraproject.org/wiki/Docs_Project_guides_table or
https://fedoraproject.org/wiki/Docs_Project_old_guides . As Petr said,
hopefully the migration will be a group effort, but if Zanata has a
concept of an "owner" then it should match the people in those tables.

Ideally, all Fedora Docs writers should be able to push new strings to
all of the Fedora guides.  We can add maintainers on the fly, of course,
but if there's going to be mass creation of projects and assignment of
maintainers, is it possible to have all the members of docs-writers[0]
added up front ? Better yet, since I signed in with my FAS account -
could Zanata use the group membership to identify us as maintainers of
these projects?

[0] https://admin.fedoraproject.org/accounts/group/members/docs-writers/

[Petr Kovar]

Hey,

On Wed, 03 Dec 2014 19:51:23 -0700
Pete Travis  wrote:
> On 11/25/2014 10:34 PM, Noriko Mizumoto wrote:
> > Hi Docs team
> >
> > Some of you have already noticed, we FLP (aka translation team) have
> > started the process of migration to new fedora.zanata.org instance from
> > Transifex. First all translators started to migrate in November 2014
> > (still going on).
> >
> > It is time to migrate all projects. This is expected to start after
> > F21 GA. The documentation is prepared and ready at [1]. If any concern
> > or question, feel free to ask at zanata-devel ml.
> > Could you now please advise the contacts of the dedicated owners for
> > migration?
> >
> > Package Name
> > anaconda-addon-development-guide
> > Community Services Infrastructure Security Policy
> > Common_Content for Publican
> > Defensive Coding Guide
> > Documentation website
> > docbook-locales
> > Accessibility Guide
> > Amateur Radio Guide
> > Burning ISOs
> > Cloud Guide
> > Fedora Cookbook
> > Documentation Guide
> > Elections Guide
> > FreeIPAGuide
> > Installation Quick Start Guide ---> depricated
> > Installation Guide
> > Fedora Jargon Buster ---> depricated
> > Live Images
> > Fedora Managing Confined Services ---> depricated
> > Musicians' Guide
> > Multiboot Guide
> > Networking Guide
> > OpenSSH Guide
> > Packager's Guide
> > Power Management Guide
> > Release Notes
> > Resource Management Guide ---> depricated
> > Fedora Respin Guide ---> depricated
> > Fedora RPM Guide ---> depricated
> > Security Guide
> > Fedora Selinux FAQ ---> depricated
> > Fedora Selinux Guide ---> depricated
> > Software Collections Guide
> > Software Management Guide
> > Storage Administration Guide
> > System Administrator's Guide
> > System Administrator's Reference Guide
> > Technical Notes
> > Translation Quick Start Guide
> > UEFI Secure Boot Guide
> > Virtualization Deployment and Administration Guide
> > Virtualization Getting Started Guide
> > Virtualization Security Guide
> > Wireless Guide ---> depricated
> > Publican branding for Fedora
> > rdo docs ---> depricated
> >
> > Many thanks in advance.
> >
> > Noriko Mizumoto
> > Fedora Localization Project
>
> Hi Noriko,
> (sorry for posting out of order, I wanted to reply to the list of books)
>
> FWIW, the coordinator for each of our guides are shown in
> https://fedoraproject.org/wiki/Docs_Project_guides_table or
> https://fedoraproject.org/wiki/Docs_Project_old_guides . As Petr said,
> hopefully the migration will be a group effort, but if Zanata has a
> concept of an "owner" then it should match the people in those tables.

The problem with the Docs_Project_guides_table is that it also lists
inactive contributors. If we want to use the table as a primary resource
for assignments, we should first review it, I think.

As for https://fedoraproject.org/wiki/Docs_Project_old_guides, I wouldn't
bother migrating projects listed there.

Just my 2 hellers,
pk

[Noriko Mizumoto]

(2014年12月04日 12:51), Pete Travis wrote:
> On 11/25/2014 10:34 PM, Noriko Mizumoto wrote:
> > Hi Docs team
> >
> > Some of you have already noticed, we FLP (aka translation team) have
> > started the process of migration to new fedora.zanata.org instance from
> > Transifex. First all translators started to migrate in November 2014
> > (still going on).
> >
> > It is time to migrate all projects. This is expected to start after
> > F21 GA. The documentation is prepared and ready at [1]. If any concern
> > or question, feel free to ask at zanata-devel ml.
> > Could you now please advise the contacts of the dedicated owners for
> > migration?
> >
> > Package Name
> > anaconda-addon-development-guide
> > Community Services Infrastructure Security Policy
> > Common_Content for Publican
> > Defensive Coding Guide
> > Documentation website
> > docbook-locales
> > Accessibility Guide
> > Amateur Radio Guide
> > Burning ISOs
> > Cloud Guide
> > Fedora Cookbook
> > Documentation Guide
> > Elections Guide
> > FreeIPAGuide
> > Installation Quick Start Guide ---> depricated
> > Installation Guide
> > Fedora Jargon Buster ---> depricated
> > Live Images
> > Fedora Managing Confined Services ---> depricated
> > Musicians' Guide
> > Multiboot Guide
> > Networking Guide
> > OpenSSH Guide
> > Packager's Guide
> > Power Management Guide
> > Release Notes
> > Resource Management Guide ---> depricated
> > Fedora Respin Guide ---> depricated
> > Fedora RPM Guide ---> depricated
> > Security Guide
> > Fedora Selinux FAQ ---> depricated
> > Fedora Selinux Guide ---> depricated
> > Software Collections Guide
> > Software Management Guide
> > Storage Administration Guide
> > System Administrator's Guide
> > System Administrator's Reference Guide
> > Technical Notes
> > Translation Quick Start Guide
> > UEFI Secure Boot Guide
> > Virtualization Deployment and Administration Guide
> > Virtualization Getting Started Guide
> > Virtualization Security Guide
> > Wireless Guide ---> depricated
> > Publican branding for Fedora
> > rdo docs ---> depricated
> >
> > Many thanks in advance.
> >
> > Noriko Mizumoto
> > Fedora Localization Project
>
> Hi Noriko,
> (sorry for posting out of order, I wanted to reply to the list of books)
>
> FWIW, the coordinator for each of our guides are shown in
> https://fedoraproject.org/wiki/Docs_Project_guides_table or
> https://fedoraproject.org/wiki/Docs_Project_old_guides . As Petr said,
> hopefully the migration will be a group effort, but if Zanata has a
> concept of an "owner" then it should match the people in those tables.
>
> Ideally, all Fedora Docs writers should be able to push new strings to
> all of the Fedora guides.  We can add maintainers on the fly, of course,
> but if there's going to be mass creation of projects and assignment of
> maintainers, is it possible to have all the members of docs-writers[0]
> added up front ? Better yet, since I signed in with my FAS account -
> could Zanata use the group membership to identify us as maintainers of
> these projects?

Hi Pete
Atm, for docs books projects, we like and expect that the delegated 
people in docs team will perform the migration manually, and we won't 
touch any book. In order to avoid any confusion within translators, I am 
tracking the migration process in the list [1]. It is appreciated if you 
can advise me the date(s) or directly edit the list to add the date(s). 
It would be nice if the project migration complete btw end of Jan to 
early Feb, leaving some room for checking rest of Feb. When everything 
good to go, all projects at Tx can be deleted (it means delete all data 
in Tx permanently).

For the group membership, I don't have an answer for you. Could you 
please ask at zanata-devel ML?

Besides we will give auto-migration for some software projects if the 
maintainer prefers (this was suggested by some developer). If you prefer 
this option, please advise as I need to schedule it. Auto-migration 
should happen btw Dec and Jan.

[1]:https://fedoraproject.org/wiki/Docs_Books_To_Migrate

Thanks

noriko
> [0] https://admin.fedoraproject.org/accounts/group/members/docs-writers/

[Petr Kovar]

Hi Noriko and others,

On Tue, 09 Dec 2014 14:10:53 +1000
Noriko Mizumoto  wrote:
> Hi Pete
> Atm, for docs books projects, we like and expect that the delegated 
> people in docs team will perform the migration manually, and we won't 
> touch any book. In order to avoid any confusion within translators, I am 
> tracking the migration process in the list [1]. It is appreciated if you 
> can advise me the date(s) or directly edit the list to add the date(s). 
> It would be nice if the project migration complete btw end of Jan to 
> early Feb, leaving some room for checking rest of Feb. When everything 
> good to go, all projects at Tx can be deleted (it means delete all data 
> in Tx permanently).
>
> For the group membership, I don't have an answer for you. Could you 
> please ask at zanata-devel ML?
>
> Besides we will give auto-migration for some software projects if the 
> maintainer prefers (this was suggested by some developer). If you prefer 
> this option, please advise as I need to schedule it. Auto-migration 
> should happen btw Dec and Jan.

I think there has been some misunderstanding in this thread. I'm
volunteering to serve as a temporary owner for the migrated guides but I
certainly don't have time to manually migrate all the guides in question.
Not sure what others think, but I'm afraid a manual process would be
extremely time consuming.

Because the migrated guides store their translation files in a standardized
directory structure set by publican, I believe it should be possible to use
the same migration tools as with the software projects. Now, I don't know
the tooling you are going to use to migrate the software projects, but I
hope I could help out with some tweaking to make them work with
publican-based projects, if necessary.

If nobody objects, let's schedule the auto-migration for the active docs
projects in https://fedoraproject.org/wiki/Docs_Books_To_Migrate

Thanks,
pk

[Noriko Mizumoto]

Hi
> If nobody objects, let's schedule the auto-migration for the active docs
> projects in https://fedoraproject.org/wiki/Docs_Books_To_Migrate

Ok, I will start scheduling them in. Earliest ones might start next 
week. All the books will be archived in a few days. Let me know if any 
priority you mind, otherwise it will be scheduled alphabetical order.

For the request of maintainers by Pete, I counted the number of writers 
in the list[0]. There is more than 90 people in this group. I am not 
sure if you really like them all as maintainer for all books. Zanata 
team will add Petr as maintainer for all books this time.

About the group membership[1], I believe Carlos can give better answer.

[0]:https://admin.fedoraproject.org/accounts/group/members/docs-writers/
[1]:https://lists.fedoraproject.org/pipermail/docs/2014-December/015930.html

cheers

noriko

(2014年12月10日 02:31), Petr Kovar wrote:
> Hi Noriko and others,
>
> On Tue, 09 Dec 2014 14:10:53 +1000
> Noriko Mizumoto  wrote:
> > Hi Pete
> > Atm, for docs books projects, we like and expect that the delegated
> > people in docs team will perform the migration manually, and we won't
> > touch any book. In order to avoid any confusion within translators, I am
> > tracking the migration process in the list [1]. It is appreciated if you
> > can advise me the date(s) or directly edit the list to add the date(s).
> > It would be nice if the project migration complete btw end of Jan to
> > early Feb, leaving some room for checking rest of Feb. When everything
> > good to go, all projects at Tx can be deleted (it means delete all data
> > in Tx permanently).
> >
> > For the group membership, I don't have an answer for you. Could you
> > please ask at zanata-devel ML?
> >
> > Besides we will give auto-migration for some software projects if the
> > maintainer prefers (this was suggested by some developer). If you prefer
> > this option, please advise as I need to schedule it. Auto-migration
> > should happen btw Dec and Jan.
>
> I think there has been some misunderstanding in this thread. I'm
> volunteering to serve as a temporary owner for the migrated guides but I
> certainly don't have time to manually migrate all the guides in question.
> Not sure what others think, but I'm afraid a manual process would be
> extremely time consuming.
>
> Because the migrated guides store their translation files in a standardized
> directory structure set by publican, I believe it should be possible to use
> the same migration tools as with the software projects. Now, I don't know
> the tooling you are going to use to migrate the software projects, but I
> hope I could help out with some tweaking to make them work with
> publican-based projects, if necessary.
>
> If nobody objects, let's schedule the auto-migration for the active docs
> projects in https://fedoraproject.org/wiki/Docs_Books_To_Migrate
>
> Thanks,
> pk

[Pete Travis]

On 12/11/2014 12:27 AM, Noriko Mizumoto wrote:
> Hi
> > If nobody objects, let's schedule the auto-migration for the active
>
> docs
> > projects in https://fedoraproject.org/wiki/Docs_Books_To_Migrate
>
> Ok, I will start scheduling them in. Earliest ones might start next
> week. All the books will be archived in a few days. Let me know if any
> priority you mind, otherwise it will be scheduled alphabetical order.
>
> For the request of maintainers by Pete, I counted the number of
> writers in the list[0]. There is more than 90 people in this group. I
> am not sure if you really like them all as maintainer for all books.
> Zanata team will add Petr as maintainer for all books this time.
>
> About the group membership[1], I believe Carlos can give better answer.
>
> cheers
>
> noriko
>
> (2014年12月10日 02:31), Petr Kovar wrote:
> > Hi Noriko and others,
> >
> > On Tue, 09 Dec 2014 14:10:53 +1000
> > Noriko Mizumoto  wrote:
> > > Hi Pete
> > > Atm, for docs books projects, we like and expect that the delegated
> > > people in docs team will perform the migration manually, and we won't
> > > touch any book. In order to avoid any confusion within translators,
> > > I am
> > > tracking the migration process in the list [1]. It is appreciated if
> > > you
> > > can advise me the date(s) or directly edit the list to add the date(s).
> > > It would be nice if the project migration complete btw end of Jan to
> > > early Feb, leaving some room for checking rest of Feb. When everything
> > > good to go, all projects at Tx can be deleted (it means delete all data
> > > in Tx permanently).
> > >
> > > For the group membership, I don't have an answer for you. Could you
> > > please ask at zanata-devel ML?
> > >
> > > Besides we will give auto-migration for some software projects if the
> > > maintainer prefers (this was suggested by some developer). If you
> > > prefer
> > > this option, please advise as I need to schedule it. Auto-migration
> > > should happen btw Dec and Jan.
> >
> > I think there has been some misunderstanding in this thread. I'm
> > volunteering to serve as a temporary owner for the migrated guides but I
> > certainly don't have time to manually migrate all the guides in
> > question.
> > Not sure what others think, but I'm afraid a manual process would be
> > extremely time consuming.
> >
> > Because the migrated guides store their translation files in a
> > standardized
> > directory structure set by publican, I believe it should be possible
> > to use
> > the same migration tools as with the software projects. Now, I don't
> > know
> > the tooling you are going to use to migrate the software projects, but I
> > hope I could help out with some tweaking to make them work with
> > publican-based projects, if necessary.
> >
> > If nobody objects, let's schedule the auto-migration for the active docs
> > projects in https://fedoraproject.org/wiki/Docs_Books_To_Migrate
> >
> > Thanks,
> > pk

Hey Noriko,

For the maintainers list, I do think that using that group as the list
of people that can push strings for all guides is good, even if the list
is large, because if Zanata can use the FAS group instead of just
inputting the list of people, we can manage the group membership in FAS
instead of Zanata.  I would like all guide writers to update POs for any
books they work on.  I would also like to not need to manage the group
memberships in two places.  If Zanata can't know about FAS groups
though, I agree we should have a shorter list.

I also wanted to make sure you were aware of
https://bugzilla.redhat.com/show_bug.cgi?id=1147332 since it might
affect your migration tools.