On 27 Apr 2010, at 10:16, Quim Gil wrote: > The plan is to have in few weeks a first complete MeeGo release followed > by a roadmap to work on the next release. Once this is out the MeeGo > project shouldn't have any obstacle to have all the daily work and > routines in the open. >
Thanks for the honest reply Quim. I think a LOT of misunderstandings and anxiety about what's happening could have been avoided if this had been clearly stated from the get go. We've been getting mixed messages as others have commented on today. On Day 0 we where told all things would be clear come Day 1. Day 1 came and went and the party line was that all is open now and happening, but we're all seeing a lot of nothing. Certainly kernel discussions have been happing more over the last 2 weeks which is great. Simply knowing what's happening is enough to settle a lot of my own concerns and I'm happy to sit back and wait for the 1.0 release. > There might still be some areas under the shadow, but always related to > new developments e.g. imagine the arrival of a new cool UX category or > key platform feature. Once they are released they go to open business as > usual. > > All this is related to two main factors: > > - One that is quite unique now: two big teams having to sync on 1001 > little things before going public & common. I'm sure having discussions out in the open would have actually aided in that. There still seems to be a lot of misunderstanding between the teams from Intel and Nokia which is seeping through to the public level. Even from departments within Intel. That's my perception anyways. > - One that will be around basically always: marketing factors making > company X or even the MeeGo project itself to go for a sound release > instead of an open development since the first line of code. This is something that is of great concern to me. We've seen this before plenty of times. Specifically, partner releases, which coincide with the main product release. It seems incredibly unfair and disrespectful to a community to deny them access to the product, many of whom would possibly like to further the use in a commercial setting. But at the same time to provide access to "key partners" in order to have a big reveal for launch day. I am still very disappointed that previously open code pertaining to the netbook projects where taken offline in order to facilitate a curtain of secrecy for the period of February to May. I think this was a mistake and a poor choice and has done little to assure us that things are changing and a project management level. However, I don't want to end on a negative note. Thanks again for the honest reply. I'm eagerly awaiting the release of MeeGo 1.0 both as a user and as an engineer hoping to use it in commercial projects -- Glen Gray <sla...@slaine.org> _______________________________________________ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
