[Sugar-devel] [IAEP] Help to Find the PO file of Some Activities to able me to Translate Them

[Gary C Martin]

On 25 May 2009, at 21:02, David Van Assche wrote:

> Well the main thing here is about demoing... I've taken it upon  
> myself to package about 50 activities... including fructose and  
> glucose... now... we have things like flash which isnt an xo bundle,  
> though many people believe it could/should be, and that would/should  
> be considered a honey app, but it must be installed via rpm....  
> Really the only process required with the new jhconvert alexey has  
> been working on is upload to git, then jhconvert creates the  
> packages for the all the distros, including the .xo bundles... so  
> really we want to make it as easy as authors not having to worry  
> about packaging at all... just about uploading their latest source  
> to git.sugarlabs.org, the only place the source really needs to  
> be... we can automate the rest... but your process is currently the  
> only sane thing I've seen written up and it'd be a shame to loose it  
> in the anals of archived emails... so better wiki than nothing, no?

OK, well I've added the relevant information into the Activity Team  
FAQ for now, but it still seems like a high barrier to ask of  
potential new authors (though one step less now thanks to alsroot  
making activities.sugarlabs.org send out the [RELEASE] emails):

	http://wiki.sugarlabs.org/go/Activity_Team/FAQ

Regards,
--Gary

> kind Regards,
> David Van Assche
>
> On Mon, May 25, 2009 at 6:15 PM, Gary C Martin  
> <gary at garycmartin.com> wrote:
> On 25 May 2009, at 12:33, David Van Assche wrote:
>
> Super... that methodology should be written up some place as its a  
> great guide to follow...
>
> I'd much rather try and find some agreement to cut un-necessary  
> steps, rather than to wikify/formalise it and push every unfortunate  
> Activity author through the same sausage factory! :-)
>
> /me puts on tinfoil hat and asbestos socks
>
> I've still not heard a good argument for why Activity authors  
> currently need to create two bundles with identical source content  
> (one .xo zip and one .bz2), upload them to two different locations,  
> and document them in several different places. It's really easy to  
> get out of sync. I'm also still not convinced about the sanity of  
> distros needing to package up each individual Activity (other than  
> perhaps sucrose as one collection). If, for a moment, you think of  
> Sugar as a Firefox, and Activities as Addons, does each distro  
> really consider packaging up every Addon kicking about for Firefox?  
> Once a Sugar release and its platform dependancies are yum,  
> aptitude, or whatever installed; the Sugar UI should then be the one  
> to add/update additional Activities (via Browse as currently, or via  
> a future update control panel checking with activity.sugarlabs.org).
>
> Regards,
> --Gary
>
>
> David
>
> On Sun, May 24, 2009 at 5:32 PM, Gary C Martin  
> <gary at garycmartin.com> wrote:
> Hi David,
>
>
> On 24 May 2009, at 11:47, David Van Assche wrote:
>
> Overall it would be nice if we had an activitiy matrix that showed  
> the stages of projects.
>
> The Activity Team have been making contact with past authors,  
> slowly, slowly we're moving along even if it means adopting extra  
> activities ourselves:
>
>
>       http://wiki.sugarlabs.org/go/Activity_Team/Activity_Status
>
> The best thing folks can do If they have a favourite activity that  
> is not yet migrated to Sugar Labs infrastructure is make some noise  
> about it. Email the IAEP and/or sugar-devel and advocate or ask  
> about it, email the author/s, see if they are still working on it or  
> have future plans. Many activity developers seem to think no one is  
> interested/using their work and often seem pleasantly surprised when  
> they get an email about their past efforts.
>
>
> This would be helpful to show what people could work on to.  
> Something like, name of activity on one side, and on the other stage  
> (planning, pre-source, alpha, beta, rc, release, packaged, xo  
> bundled, translated) Something along those lines, but I'm sure  
> someone can come up with a better matrix. If this was up at some  
> place, we could know pretty quickly what people could be working on.  
> It could even be split by distro too... The idea came to me because  
> there are a ton of git projects with no code in them.
>
> If there are git projects with no code in them, what makes you think  
> the developer will edit another page somewhere else with project  
> status information! ;-b
>
> With my activity developer hat on, I do find it a pain how many  
> seemingly random places there are to work on when releasing a new  
> version, even more for a new project, or migrated one. My check-list/ 
> todo-list is something like:
>
> If it's a new project:
>
> - Create a Gitorious project repository for it http://git.sugarlabs.org/ 
>  and start hacking on your code
>
> - Request a trac component for you activity at http://dev.sugarlabs.org/
>
> - Open a trac ticket to request addition to Pootle (if your strings/ 
> release is reasonably mature/ready)
>
> - Create a page at http://wiki.sugarlabs.org/go/Activities/<actvity- 
> name>
>
> If it's a new release:
>
> - Update your activities wiki page at http://wiki.sugarlabs.org/go/Activities/ 
> <actvity-name>
>
> - Upload the .xo bundle, screenshots, notes to http://activities.sugarlabs.org/
>
> - Upload .bz2 source to shell.sugarlabs.org /upload/sugar/sources/ 
> honey
>
> - Edit wiki table http://wiki.sugarlabs.org/go/Development_Team/Source_Code 
>  and make sure it's pointing to your latest .bz2
>
> - Edit wiki table http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap 
>  to get it on Soas
>
> - Write a [RELEASE] <activity-name-version> email and send it to  
> sugar-devel
>
> If the project is migrating from olpc infrastructure:
>
> - Migrate git repository from http://dev.laptop.org/
>
> - Migrate open trac tickets from http://dev.laptop.org/
>
> - Track down relevant wiki.laptop.org pages and indicate the migration
>
> - For deployed activities make sure relevant http://wiki.laptop.org/go/Activities 
>  page version templates point to the correct/latest working bundles.
>
> I'm sure I missed a step or two, but I think you get the picture!
>
>
> On Sat, May 23, 2009 at 1:51 PM, Tomeu Vizoso <tomeu at sugarlabs.org>  
> wrote:
> Hi Mohammad,
>
> On Tue, May 19, 2009 at 06:36, Mohammad Hamed <m.hamed at paiwastoon.com.af 
> > wrote:
> > Dear Software Translators,
> >
> > Could you please tell me how can I translate some Activities like:
> > Physics, X2O, WFP, Implode, Conozco Uruguay to my language?
>
> FWIW: Having spoken with Alex Levenson yesterday, I've started to  
> migrate Physics over to Suage Labs infrastructure (X2o is next on my  
> list). It runs fine on sugar-jhbuild, but does need some UI work and  
> clean-up before I request addition to pootle for translation, or  
> upload a bundle to activities.sugarlabs.org. I also mailed Jo Lee  
> (Implode) about his availability, will migrate that over as well if  
> he doesn't have the time at the moment.
>
> Regards,
> --Gary
>
>
> >
> > If you could tell me that how can I find the PO file of the  
> activities it
> > would be easier for me to translate them.
>
> Looks like these activities are not in pootle yet. What I think we
> should do is to contact the maintainers and work with them so their
> activities are translatable in pootle. If the activities have no
> active maintainers, then perhaps the Activity Team could adopt them?
>
> Regards,
>
> Tomeu
>
> > Sincerely,
> >
> > --------
> > Mohammad Hamed
> > User Service Officer
> > One Laptop Per Child (OLPC) Project
> > PAIWASTOON Networking Services Ltd.
> >
> > Email: m.hamed at paiwastoon.com.af
> > Mobile: 0093 786 876546
> > Phone:  0093 794 195494
> >
> > PAIWASTOON Networking Services Ltd.
> > 1st street Kart-e-Se, Darul Aman Road
> > Kabul, Afghanistan
> >
> > www.paiwastoon.com.af
> > www.olpc.af
> >
> >
> > _______________________________________________
> > IAEP -- It's An Education Project (not a laptop project!)
> > IAEP at lists.sugarlabs.org
> > http://lists.sugarlabs.org/listinfo/iaep
> >
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
> _______________________________________________
> IAEP -- It's An Education Project (not a laptop project!)
> IAEP at lists.sugarlabs.org
> http://lists.sugarlabs.org/listinfo/iaep
>
>
>
>