#48 Fedora 28 translation sprint
Closed: Insufficient data 5 years ago by jibecfed. Opened 6 years ago by jibecfed.

We should probably run a translation sprint for Fedora 28 :)
https://fedoraproject.org/wiki/Releases/28/Schedule

Here is the draft todo list (to be improved):
Before:
* [x] agree on the schedule
* [ ] communicate one month before on the mailing list and community blog
* should be done before January 20th
* [ ] check our list of packages are up to date
* [ ] create a wiki page
* [ ] communicate one week before in the community blog
* should be done before January 13th
After:
* [ ] collect stats
* [ ] produce graphs
* [ ] produce and publish article


In meeting we said it has to last two weeks and to be before Software Translation Deadline.

So, translation sprint should start with:

2018-02-20 Change Checkpoint: Completion deadline (testable)
Branch Fedora 28 from Rawhide (Rawhide becomes future F29)

And end with:

2018-03-06 Software Translation Deadline

@jkurik as Fedora Program Manager, can you please tell us how to include in the F28 schedule, and in official communication this event?

If you would like to add new tasks/items to the F28 Translation schedule, just let me know the dates and names of tasks/items and I will add it there.

The dates might be absolute (exact date) or relative to other tasks.
For example:

  • Task name: Translation sprint
  • Starts: a day after Change Checkpoint: Completion deadline (testable)
  • Ends: a day before Software Translation Deadline

@jkurik what you wrote is perfect, can you please add it to F28 schedule and makes sure it is included in communications?

@jibecfed let me know how can i F28 as Language Coordinator

Looks like the Translation sprint 2018 didn't happen at the end (or I have missed that)?
Anyway, I do believe, many of us have translated a word or two in the given week. If you give me some stats from Zanata, I can create the figures about user translation activity during that period.
If you tell me how to get that stats from Zanata, I can obtain them by myself and prepare some report.

As you wish ;-)

Metadata Update from @jibecfed:
- Issue close_status updated to: Insufficient data
- Issue status updated to: Closed (was: Open)

5 years ago

Login to comment on this ticket.

Metadata