[Kst] Tasks for Google Code-In

[nicolas.brisset at free.fr]

Hi Andriy,

yes, I remember that mail very well, and one mail from this discussion is referenced in the Google Code-In proposal:
http://google-melange.appspot.com/gci/task/view/google/gci2011/7134268 which contains very interesting pointers.

My idea for this task is to define clearly the steps required to get Kst2 infrastruture set up so that translations can be done as for other KDE apps. 
I believe that things have changed a bit since KDE switched to git, but nobody in the Kst team is completely aware of how things work now. So a detailed list of steps would be nice, maybe we can even achieve some straight away:
- where to put the code? (svn or git, which repository, ...)
- how to pass messages on to translators (how to generate .pot files and back, as Marble does)?
- how to write the user manual? I think I saw a discussion in a blog regarding the use of userbase to put documentation, but I don't know if it's practicable as it would certainly make it difficult to have formalized release schedules. Any experience how to make documentation writing fun, easy and translatable would be interesting to know so that we can benefit from it
- any other related idea

I am aware that this is still a bit vague, but the whole point of this task is... to make it crystal clear!

Nicolas

----- Mail original -----
> De: "Andriy Shinkarchuck" <adriano32.gnu at gmail.com>
> À: kst at kde.org
> Envoyé: Vendredi 25 Novembre 2011 20:21:10
> Objet: Re: [Kst] Tasks for Google Code-In
> 
> Nicolas, what about translation? I remember Alexander Potashev's
> (http://mail.kde.org/pipermail/kst/2011-September/020089.html) with
> suggestion for translations?
> What should man do for task "Kst 2.x: get ready for translation"?
> Preparation of Messages.sh or some else?