Hi again, I've been mostly looking at the SW architecture issues when it comes to porting MeeGo to new environments, so I'm not so well aware of the process issues and expecting someone else to describe those things.
The contacts that you can find from http://meego.com/about/governance/release-engineering should know how everything is supposed to be handled in terms of processes, tools etc. Regards, Jari From: ext Francisco Rivas [mailto:franciscojriv...@gmail.com] Sent: 21. kesäkuuta 2010 16:40 To: Palojarvi Jari (Nokia-D/Tampere) Cc: thi...@kde.org; meego-dev@meego.com Subject: Re: [MeeGo-dev] Porting meego to new hardware Hello *, that is great!. I would like to contribute with some information. I think, if you consider it appropriate, start filling the methodology (steps/tasks) to get ported meego to the preferred architecture. I am not pretty sure if always companies (manufacturers) of HW provide us with kernels, toolchains and rootfs, I think most of the time it happen, at least in my case, so we can manage those scenarios too. How can we organize, to make some contributions? Thank you very much for your effort, thank you in advanced and best regards. On Mon, Jun 21, 2010 at 14:51, <jari.paloja...@nokia.com<mailto:jari.paloja...@nokia.com>> wrote: Hi, Actually some thinking around this has happened already, but somewhat silently so far. Anyway, there's a draft table of contents for a MeeGo Porting Guide at http://wiki.meego.com/MPG. I'm planning to update the pages a bit during this week. In some areas, the HW adaptation SW interfaces are pretty clear and I'll try to reflect that in the pages. In some other areas, the underlying SW architecture in MeeGo is still open and hence we cannot say much about the adaptation SW interfaces either. I can mention something about those areas as well. Note that also the http://meego.com/developers/hardware-enabling-process page has some information about the porting issues. A mailing list about porting issues is not a bad idea. Other options include a dedicated MeeGo forum and even the discussion tab associated with the wiki pages themselves. Regards, Jari > -----Original Message----- > From: meego-dev-boun...@meego.com<mailto:meego-dev-boun...@meego.com> > [mailto:meego-dev-boun...@meego.com<mailto:meego-dev-boun...@meego.com>] > On Behalf Of ext Thiago Macieira > Sent: 21. kesäkuuta 2010 14:57 > To: meego-dev@meego.com<mailto:meego-dev@meego.com> > Subject: Re: [MeeGo-dev] Porting meego to new hardware > > Em Segunda-feira 21 Junho 2010, às 08:51:44, USA Linux UAE escreveu: > > Hello, > > I know this is early days of meego, but is there any plans to have > > something in place for helping developers to port meego to > > mips/powerpc and other new hardware. > > > > Android has android-porting mailing list , any plans for meego- > porting > > list?? > > I'd say that, if a list is needed, then it should be created. But I > think this list here is enough until the conversations specific to > porting get too widespread. > > As for the porting itself, it's up to the people who want to do it to > come up with tasks. I've never done porting of a distro, so I can't > comment on that. > What does it involve, besides rebuilding everything? > > Once the ports reach certain maturity, you should ask the TSG to bless > it and therefore gain OBS space. > > -- > Thiago Macieira - thiago (AT) macieira.info<http://macieira.info> - thiago > (AT) kde.org<http://kde.org> > Senior Product Manager - Nokia, Qt Development Frameworks > PGP/GPG: 0x6EF45358; fingerprint: > E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358 _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com<mailto:MeeGo-dev@meego.com> http://lists.meego.com/listinfo/meego-dev
_______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
