Hello,
No surprise here but the MeeGo TSG has decided it does not want to
provide any official resources to the Debian community to help with porting /
maintaining software inside MeeGo to Debian. See the proposal's wiki page for
more information.
This may turn out to be a Good Thing since we'll not have to please our
corporate overlords and can use the tools we have as well as leverage our
substantial community. Yes, this is a bit of a fork I suppose, but MeeGo seems
unwilling to change the situation at this moment so I think this is really the
only option. I think we ought to look into creating separate support tools,
like mailing lists for example inside Debian if that is needed. Perhaps people
will prefer to use the MeeGo dev list.
I suppose a Debian working group inside MeeGo is not really needed -
that is the impression I get from some Moblin devs anyway, but I think that
MeeGo missed an opportunity to enable easier effective communication between
the two projects, and I think that is unfortunate. In any case, now it is time
to rally the troops to make sure anything we want in Debian is ported from
MeeGo. Please provide any feedback you may have on how we can best identify,
package and build useful MeeGo software for Debian - perhaps we should just
pull from upstream for example (i.e. ofono, connman, etc.) instead of using
MeeGo repos?
Regards,
Jeremiah
_______________________________________________
MeeGo-dev mailing list
[email protected]
http://lists.meego.com/listinfo/meego-dev
