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 <a href="http://git.sugarlabs.org">git.sugarlabs.org</a>, 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? kind Regards, David Van Assche <div class="gmail_quote">On Mon, May 25, 2009 at 6:15 PM, Gary C Martin <<a href="mailto:gary@garycmartin.com">gary@garycmartin.com</a>> wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="im">On 25 May 2009, at 12:33, David Van Assche wrote: <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Super... that methodology should be written up some place as its a great guide to follow... </blockquote> </div> 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 <a href="http://activity.sugarlabs.org" target="_blank">activity.sugarlabs.org</a>). Regards, --Gary<div><div></div><div class="h5"> <blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> David On Sun, May 24, 2009 at 5:32 PM, Gary C Martin <<a href="mailto:gary@garycmartin.com" target="_blank">gary@garycmartin.com</a>> 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: <a href="http://wiki.sugarlabs.org/go/Activity_Team/Activity_Status" target="_blank">http://wiki.sugarlabs.org/go/Activity_Team/Activity_Status</a> 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 <a href="http://git.sugarlabs.org/" target="_blank">http://git.sugarlabs.org/</a> and start hacking on your code - Request a trac component for you activity at <a href="http://dev.sugarlabs.org/" target="_blank">http://dev.sugarlabs.org/</a> - Open a trac ticket to request addition to Pootle (if your strings/release is reasonably mature/ready) - Create a page at <a href="http://wiki.sugarlabs.org/go/Activities/" target="_blank">http://wiki.sugarlabs.org/go/Activities/</a><actvity-name> If it's a new release: - Update your activities wiki page at <a href="http://wiki.sugarlabs.org/go/Activities/" target="_blank">http://wiki.sugarlabs.org/go/Activities/</a><actvity-name> - Upload the .xo bundle, screenshots, notes to <a href="http://activities.sugarlabs.org/" target="_blank">http://activities.sugarlabs.org/</a> - Upload .bz2 source to <a href="http://shell.sugarlabs.org" target="_blank">shell.sugarlabs.org</a> /upload/sugar/sources/honey - Edit wiki table <a href="http://wiki.sugarlabs.org/go/Development_Team/Source_Code" target="_blank">http://wiki.sugarlabs.org/go/Development_Team/Source_Code</a> and make sure it's pointing to your latest .bz2 - Edit wiki table <a href="http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap" target="_blank">http://wiki.sugarlabs.org/go/Sugar_on_a_Stick/Roadmap</a> 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 <a href="http://dev.laptop.org/" target="_blank">http://dev.laptop.org/</a> - Migrate open trac tickets from <a href="http://dev.laptop.org/" target="_blank">http://dev.laptop.org/</a> - Track down relevant <a href="http://wiki.laptop.org" target="_blank">wiki.laptop.org</a> pages and indicate the migration - For deployed activities make sure relevant <a href="http://wiki.laptop.org/go/Activities" target="_blank">http://wiki.laptop.org/go/Activities</a> 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 <<a href="mailto:tomeu@sugarlabs.org" target="_blank">tomeu@sugarlabs.org</a>> wrote: Hi Mohammad, On Tue, May 19, 2009 at 06:36, Mohammad Hamed <<a href="mailto:m.hamed@paiwastoon.com.af" target="_blank">m.hamed@paiwastoon.com.af</a>> 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 <a href="http://activities.sugarlabs.org" target="_blank">activities.sugarlabs.org</a>. 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: <a href="mailto:m.hamed@paiwastoon.com.af" target="_blank">m.hamed@paiwastoon.com.af</a> > Mobile: 0093 786 876546 > Phone: 0093 794 195494 > > PAIWASTOON Networking Services Ltd. > 1st street Kart-e-Se, Darul Aman Road > Kabul, Afghanistan > > <a href="http://www.paiwastoon.com.af" target="_blank">www.paiwastoon.com.af</a> > <a href="http://www.olpc.af" target="_blank">www.olpc.af</a> > > > _______________________________________________ > IAEP -- It's An Education Project (not a laptop project!) > <a href="mailto:IAEP@lists.sugarlabs.org" target="_blank">IAEP@lists.sugarlabs.org</a> > <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a> > _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) <a href="mailto:IAEP@lists.sugarlabs.org" target="_blank">IAEP@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a> _______________________________________________ IAEP -- It's An Education Project (not a laptop project!) <a href="mailto:IAEP@lists.sugarlabs.org" target="_blank">IAEP@lists.sugarlabs.org</a> <a href="http://lists.sugarlabs.org/listinfo/iaep" target="_blank">http://lists.sugarlabs.org/listinfo/iaep</a> </blockquote> </div></div></blockquote></div>