[MeeGo-dev] Community infra resources & funds (was RE: MeeGo...)

[Matti Airas]

Hi Quim, Imad,

Has there been any update to this? The end of the year is fast 
approaching, and as far as we know, meego.com
future is completely uncertain after that. If the community has to 
migrate to another infrastructure, it would be good to know that well in 
advance  so that there is sufficient time to allow us for a smooth 
migration.

Best,

Matti Airas

On 03.10.2011 18:58, ext quim.gil at nokia.com wrote:
> Discussing resources&  funds is not as much fun as discussing brands or toolkits, but let me bring your attention to this point since it is probably important or plain critical for any plans forward discussed here.
>
> My assumption is that the current community doesn't have enough muscle to afford the whole cost of infrastructure of a project with the size and complexity of MeeGo. The options are either reuse free-as-in-beer infra from other projects or assure corporate sponsorship from different sources (I would trust less this one, but it is also a possibility).
>
> Imad Sousou wrote:
>> I will be working even harder to make sure that developers of MeeGo can also transition to Tizen.
> 1. Can we get any details about the availability of the current meego.com infrastructure under Intel's funding? End of this year? July 2012? End of 2012? Later? The answer to this question helps figuring out the urgency for a move.
>
> 2. What is the scope we can expect  for tizen.org in terms of community infrastructure? Will a "fortizen.org" like site be needed as well or the core tizen.org (plus AppUp?) will be inclusive enough to satisfy community initiative with a link to the Tizen project, even if it's indirect? The answer to this question helps figuring out the need to find/fund own infra for all the "non-official" development infra.
>
> Thank you.
>
> --
> Quim
> _______________________________________________
> MeeGo-dev mailing list
> MeeGo-dev at meego.com
> http://lists.meego.com/listinfo/meego-dev
> http://wiki.meego.com/Mailing_list_guidelines