On Mar 18, 2010, at 10:50 AM, Raphael Hertzog wrote:
>
>
>> You need to find the concrete points where this working group can be
>> useful to the MeeGo project strategy and goals. Otherwise it is easy to
>> consider this activity as unofficial or alternative, since it is not
>> essential to the project goals.
I would propose that part of this working groups goals would be to identify
ways to facilitate technology transfer between Maemo and MeeGo. The concrete
goals might be:
- Identify software that is in one platform and missing from the other
- Create a 'best practice' that would show how one could bring
identified software to the other platform
- Re-package and maintain software that has be brought from one
platform to the other
>
>> You also need to propose the coordinators of the working group, who will
>> be the ones interfacing directly to the TSG. Having someone with an
>> official role in the MeeGo project definitely helps. This is also a
>> reason why a first row of nominations is needed.
>
> I don't have any role in the MeeGo project (yet) but I'm willing to
> help as coordinator of the working group. I have modified the wiki page so
> that coordinators stand out of the contributor list. I will gladly expand
> the list to include someone else with an official Meego role but as you
> point out, it's difficult at this point.
My role as Maemo debmaster is to serve the community packaging their software.
Perhaps if I proposed my participation to the council and the community at
large the community might feel this is a valuable addition to my time. Plus we
could develop a path for developers who want to migrate from Maemo to MeeGo and
from MeeGo/Moblin to Maemo/MeeGo.
>
>> Now, I'm not involved in any discussion or decision about packaging
>> technologies and the future of this working group proposal. But if you
>> want to know my opinion I think a point to look at is the objective fact
>> that MeeGo developers targeting Nokia devices this year will need to
>> deal with deb packages as well as rpm if they want to cover all the
>> devices offering a MeeGo API. This means that at least someone at Nokia
>> will need to work making life easier for those MeeGo developers. Some
>> work in OBS and SDK will be needed.
>
> Indeed, but I don't work at Nokia so I don't know who that someone is.
> CCing meego-dev@ as that someone is more likely to read that list.
> Please get in touch with me if you are that someone. :-)
I hope to help out but I am not an official Nokia employee, just someone who
Nokia provides to the community. I am happy to help. I wonder if others like
perhaps Marcus Vollmer might want to participate? Carsten Munk? I am certain
there are others. :-)
>> alternative to the rpm based that is planned. If building such
>> alternative is the only purpose of this working group and official MeeGo
>> roles are not needed, then I wouldn't be surprised if the priority to
>> recognize this working work as official is low. I guess such working
>> group could still do all the necessary work using the MeeGo OBS and
>> tools without any official approval from the TSG.
>
> I think official approval is important to be legitimate in the community.
> We will have to request commit access to all repositories for the purpose
> of maintaining the debian directories for example. It's best if the TSG
> blesses the people who are able to tell "foo can be trusted in terms of debian
> packaging, he knows what he does, please grant him access to the
> repositories".
This seems to be a good way to go. I currently have access to the Maemo
repositories and have done some work on them in the past. If we could create a
reliable group then perhaps MeeGo might give us some space and bandwidth on the
servers to serve debs via reprepro for example? That might be un-obtrusive and
not too resource intensive.
Jeremiah_______________________________________________
Meego-community mailing list
[email protected]
http://lists.meego.com/listinfo/meego-community
