On Nov 13, 2012 1:19 PM, "Kévin Raymond" <shaiton@xxxxxxxxxxxxxxxxx> wrote:
>
> > Thanks for CCing trans@ - I need to sort out my subscriptions.
> >
> > I want to make sure I understand the structure, please correct if I'm wrong
> > :
> >
> > Resources are paired with a document's pot files, and are a subset of the
> > Transifex project. Each project is a subset of the Transifex release.
>
> It's not really a subset of the Transifex release, it's more a link that is
> created.
>
> > Updating a release requires a maintainer to manually add resources from
> > each child project. There is no version-style iteration in the context I
> > expected.
>
> Exactly. When we add a ressources, we give the name of the ressource including
> the project name. Here is an example: "Fedora Release Notes: Amateur_Radio".
>
> >
> > The manual adding of resources confuses me. I had some trouble getting tx
> > set up for this document, and manually generated much of .tx/config. When I
> > pushed to tx, there were messages about creating new resources. Are you
> > saying that even though the resources appear in the project, they need to
> > be added to the release by a more privileged maintainer?
>
> The messages about the new created ressource is about the new files that was not
> already existing on the transifex Fedora Release Notes project.
> There are two sort of maintainers:
> * Those able to edit a project push new POT (then update ressources). There are
> named at [1].
> * Those able to edit the Transifex releases available under the Fedora Project
> Hub available at [2].
>
> >
> > I don't quite understand the part about cleaning the projects, but it will
> > probably make more sense when I'm looking at Transifex - I'm on a mobile
> > browser at the moment . Is it something I can/should do?
>
> If we remove all ressources from [1] before pushing the new ones, the old files
> won't be here. I don't know about the transifex release, if they will still be
> linked. If so, this is a bug. We should test :)
>
>
> I don't know if we should do. In any case I understand that all and I am a
> maintainer in [1] and [2] therefore I can do it.
> I just want to know which is the best way (to keep the project clean or the
> release one. Or both).
> Ok, I can certainly update the transifex release first but I need to look which
> files are used this release (I can check that on the repo easily) and remove
> (hide) the old ones.
> But this could certainly leads to a Fedora release notes SOP
>
>
> [1] https://fedora.transifex.com/projects/p/fedora-release-notes/
> [2] https://fedora.transifex.com
>
>
>
> --
> Kévin Raymond
> (Shaiton)
>
> --
Much clearer now, thanks.
I suggest we test our SOP revisions against the technical notes. The project has a dynamic nature similar to the release notes, but the minimal translation required means minor impact on progress if something breaks, especially if we can recycle strings.
Would it be more effective to meet up in #fedora-docs and work on the process? I'm usually available for much of my evening, 2300 UTC and after. A little in the morning too, around 1400 UTC.
-- docs mailing list docs@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/docs
