Re: [MeeGo-dev] MeeGo Reconstructed - a plan of action and direction for MeeGo
> > My personal view (which is partly based on my marketing job) is that > > you have to start off focused on a very visible end user experience in > > order to get the project the necessary publicity. For your own > > governance reasons you will probably want to make sure the split > > between core and "vendor" is clear, but from the outside world they have > to look like one to start with. > > > > Probably this is the correct way to maintain this project alive. Probably. > Probably, an error of Nokia with the N900 is trying to mix both developers > and users. This is an error. Can you explain this a bit more? Do you mean Nokia N900 as a product, or what we are doing with MeeGo Community edition? If you mean latter, I probably understand what you mean. Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] N900 Community Edition and the relation to MeeGo
Thanks Carsten for making this! Just to add, now that MeeGo 1.2 Harmattan devices have been announced. We are adding those devices (Nokia N9 and N950) into scope for the Community Edition work. Planning and execution for this happens in the open. So, follow us in IRC or check back for some "big reveal" hopefully in the near future .) Jukka From: meego-dev-boun...@meego.com [meego-dev-boun...@meego.com] on behalf of ext Carsten Munk [cars...@maemo.org] Sent: 20 June 2011 09:16 To: meego-dev Subject: [MeeGo-dev] N900 Community Edition and the relation to MeeGo Hi all, There has been some confusion regarding the Community Edition (formerly Developer Edition) work (http://wiki.meego.com/ARM/N900 ), calling it a fork of MeeGo, etc. We're not a MeeGo fork beyond what any vendor would do - we're an active effort to improve MeeGo. And I wanted to help clear up the air for once, get everyone on the same page and state facts about what we're exactly doing, in order to lessen the confusion. I have collected those facts in a handy Community Edition Factsheet wiki page: http://wiki.meego.com/ARM/N900/CE_Factsheet Please read this page before answering this post - if there are any remaining problems/questions you want answered/issues you still see you are more than welcome to respond. Let's have an open and honest discussion about any problems and/or benefits you see with the Community Edition work. I personally think Community Edition is a benefit for the MeeGo project and I'm seeing a lot more people activated and interested in contributing to MeeGo because of it. And if you have a Nokia N900 - try it out. It shows MeeGo can be great on handsets too and quite usable. MeeGo.com in your pocket. Best regards, Carsten Munk ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] sdk 1.2+N900 DE
> Hi, Hi, > is possible to use this SDK > http://wiki.meego.com/SDK/Docs/1.2/Installing_and_configuring_MeeGo_S > DK_for_Linux > to develop with this http://wiki.meego.com/ARM/N900/DeveloperEdition? > N. It should be possible of course. Please let us know if you run into problems. Thanks, Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Dialer Project meetings announcement
Hi, > > Just wanted to say thank you for this. How about SMS application, > > anything similar going to happen? > > Don't know, you could ping the owner of meego-handset-sms though to > find > out. Check git commit logs for who that most likely is (I believe it > would be Ben). > > Shane... Thanks, will do! Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Dialer Project meetings announcement
> In an attempt to improve communication among the currently active (and > increasing daily) dialer contributors and to increase general community > awareness, I will be kicking off the first weekly Dialer Project > meeting on #meego-meeting starting next Tuesday, April 5th, at 15:00 > UTC (07:00 PST). Just wanted to say thank you for this. How about SMS application, anything similar going to happen? Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] 'EasyFix' keyword implemented in bugzilla
Hi, We have now keyword 'EasyFix' in bugzilla, to indicate "low hanging" bugs or features that the community could tackle. So let's start to use that! Thanks Eric :) Br, Jukka http://wiki.meego.com/ARM/N900/DeveloperEdition ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Announcing MeeGo 1.2 Developer Edition for N900
Hello, Did we get a reply for this question? Looking forward, Jukka From: Gil Quim (Nokia-MS/SiliconValley) Sent: 6. maaliskuuta 2011 3:39 To: ext Arjan van de Ven; Eklund Jukka (Nokia-MS/Tampere) Cc: meego-dev@meego.com Subject: Re: [MeeGo-dev] Announcing MeeGo 1.2 Developer Edition for N900 Arjan wrote: > we've been bitten rather badly > in MeeGo in the past in this respect (promising of features as part of > architecture choices, but then never getting those open sourced) Anything documented to compare? What promised features are missing? We have lost something with this change of plans in the Nokia-Intel relationship in MeeGo, but we could gain real openness in the roadmapping and architecture processes now. At least I don't see any reason for Nokia to have non-public commitments with the MeeGo project, and this is why I'm asking the questions above. -- Quim ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Announcing MeeGo 1.2 Developer Edition for N900
Hi, > Can you add some information about the different images? > > N900 Handset images: weekly build, Trunk-daily, Trunk-Testing > > Weekly build and daily build sound obvious, but maybe they are not? > - How does the weekly build differ from the 7th daily build? > - What is trunk-testing? How does it differ from trunk-daily? > - Which image shall be used for testing? > > Thanks, > -Rolf I added a link to this wiki: http://wiki.meego.com/Release_Engineering/Repo_List Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Announcing MeeGo 1.2 Developer Edition for N900
>Since you mentioned you were responsible for the actual content of this >edition, may I request 3G video >calling in the initial/first release of DE. 3G video calling has almost become >some basic standard now and it's >that we (N900) users have never experienced >it. So much for purchasing a developer device! Our edition is based on MeeGo 1.2 trunk, which doesn't have 3G video call support. Also video call support for VoIP/IM backends is not planned until 1.3. Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Announcing MeeGo 1.2 Developer Edition for N900
> I would like to urge you to push on this; we've been bitten rather > badly > in MeeGo in the past in this respect (promising of features as part of > architecture choices, but then never getting those open sourced), > and I'm sure that you, as the lead of this new project, can fix a > bunch of these; after all it sounds like you're serious about MeeGo. Noted, but I still prefer our architect and other management to comment on those issues. I'm the product manager, so I mainly concentrate on the actual content of this edition. Thanks, Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Announcing MeeGo 1.2 Developer Edition for N900
Hi, > does this include Nokia open sourcing the pieces they previously > committed to open source (including policy etc) and the pieces that are > essential for running the N900 ? I'm going to let our architecture fellows to comment on that one specifically, but the principle is to do everything in the open that is possible. Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
Re: [MeeGo-dev] Announcing MeeGo 1.2 Developer Edition for N900
Hi, > It is excellent to hear that Nokia are putting some resources into > this. > I realise it's early days, but I'm interested to know roughly how many > people at Nokia will be working on this, and how you will be liasing > with the existing MeeGo N900 hardware adaptation team? Hard to say any exact amounts, so I won't even try. There will more information coming. N900 adaptation team is an integral part of this. Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] Announcing MeeGo 1.2 Developer Edition for N900
Hi there, I am thrilled to announce a little thing we started at Nokia. Basically we want to have MeeGo running in N900 device, so that it's really usable as your daily development device. Basic Handset UX should work, phone calls, SMS, web browsing. So we are concentrating on a few selected features and polish those to be "perfect". It might mean that we leave out some things in MeeGo 1.2 trunk for this edition, but that is not the default intention. We are doing this fully on the open, and I hope this is an interesting project where we all in the community work towards the same goal: have a great MeeGo edition in the N900. This work is naturally based on the great work done already by N900 adaptation team lead by Harri and Carsten. The wiki is up here: http://wiki.meego.com/ARM/N900/DeveloperEdition. It will populated with more information as we go, thanks for the patience. Br, Jukka Developer Edition product manager twitter.com/jukkaeklund IRC: jukka http://www.linkedin.com/in/jukkaeklund ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev http://wiki.meego.com/Mailing_list_guidelines
[MeeGo-dev] MeeGo Product management wiki created, and Change management process kicking off
(cross-posting from meego-pm, let's carry on discussion there) Hello, I have corrected the issue of missing wiki for PM function, by creating a page and linked it also to main page: http://wiki.meego.com/Product_Management. The wiki is (of course) a work in progress, and missing stuff. One of the key items on the wiki is the Change management process, which we are now kicking off. I will right away say the process is modeled very much after Architecture team process. As said on the wiki, we shall discuss the topics right here in this email list and document the actions on the wiki. Looking forward to community participation also on the product management side of MeeGo! Br, Jukka ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] progressing on compliance spec
Hi, Did this proceed, is there a meeting(s) scheduled on IRC? Jukka > -Original Message- > From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] > On Behalf Of ext Sivan Greenberg > Sent: 7. joulukuuta 2010 18:16 > To: Ylinen Mikko.K (Nokia-MS/Tampere) > Cc: meego-dev@meego.com > Subject: Re: [MeeGo-dev] progressing on compliance spec > > I'm at UTC+2 currently, so late evening would be best unless it is > friday. > > -Sivan > > On Tue, Dec 7, 2010 at 2:24 PM, wrote: > > Hi, > > > >>-Original Message- > >>From: Wichmann, Mats D > >>Sent: 03 December, 2010 18:50 > >> > >> > >>since there still seem to be a number of open questions, > >>I'd like to set up a #meego-meeting on a regular basis > >>until we've come to more agreement. For those who are > >>interested, are there particular times that would be bad > >>(obviously already taken times are out since the meeting > >>channel is single-threaded) > > > > Would you have any proposals? In general, afternoon/early > > evening EEST times are bad for me. > > > > http://wiki.meego.com/MeeGo-Meeting_IRC_Schedule > > > > -- > > Mikko > > ___ > > MeeGo-dev mailing list > > 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 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Or actually new feature requests go to 'unspecified' first and then the product manager decides on the release? Really good points everyone so far, and it seems a lot of confusion comes from the fact using Bugzilla as the "featurezilla" :) AFAIK there was a plan to have a separate "landing page" for Features, I think that would go a long way helping this. One thing I am slightly confused.. I've understood MeeGo is about "contribution is king" ie. whoever is making a new feature (request) will have to have at least an idea on where the actual contribution (code in most cases) is coming from, if not the whole contribution. Isn't that the case? If so, how will potential interested contributors know what are key things missing from eg. a specific release? Jukka > -Original Message- > From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] > On Behalf Of ext Arjan van de Ven > Sent: 3. tammikuuta 2011 20:33 > To: Dave Neary > Cc: meego-dev@meego.com; Pienimaki Sami (Nokia-MS/Tampere); Lavonius > Ville (Nokia-MS/Helsinki) > Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? > > On 1/3/2011 10:10 AM, Dave Neary wrote: > > just as a side note... > since we're about two or so weeks away from feature freeze for 1.2 > it should be assumed that all feature requests that get filed are for > 1.3 ( in fact, that should have been the case from the day that 1.2 > development started, back in late October) > > ___ > MeeGo-dev mailing list > 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
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Hi, It's a fair question :) But I'm wondering what kind of information you are looking for, or actually what kind of format? As you know all the information is on featurezilla, for everybody to see. You can do queries like this: http://bugs.meego.com/report.cgi?x_axis_field=product&y_axis_field=component&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&classification=MeeGo+Features&product=MeeGo+Connected+TV+Features&product=MeeGo+Core+OS+Features&product=MeeGo+Handset+Features&product=MeeGo+IVI+Features&product=MeeGo+Netbook+Features&product=MeeGo+SDK+features&product=MeeGo+Tablet+Features&version=1.2&version=1.2&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&deadlinefrom=&deadlineto=&emailassigned_to1=1&emailtype1=substring&email1=&emailassigned_to2=1&emailreporter2=1&emailqa_contact2=1&emailcc2=1&emailtype2=substring&email2=&bugidtype=include&bug_id=&votes=&chfieldfrom=&chfieldto=Now&chfieldvalue=&format=table&action=wrap&field0-0-0=noop&type0-0-0=noop&value0-0-0= (all Accepted 1.2 features in products, grouped to components) BTW, for Handset there is some material already in http://wiki.meego.com/Roadmap, in the form of high-level presentation from MeeGo conference. Jukka > -Original Message- > From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] > On Behalf Of ext Carsten Munk > Sent: 2. tammikuuta 2011 0:29 > To: meego-dev; Hindman, Gavin; Pienimaki Sami (Nokia-MS/Tampere); > Rudolf Streif; Lavonius Ville (Nokia-MS/Helsinki) > Subject: [MeeGo-dev] MeeGo 1.2 Roadmap? > > Hi, > > So, we're in 2011, we have a release 1.2 in about 4-5 months - and I > wondered, what do we intend on delivering? > > I went to http://wiki.meego.com/Roadmap and looked, finding that we > have a release plan (always good..) and plans related to the build > infrastructure.. But no Core/Handset/IVI/SDK roadmaps. Nor on > meego.com anywhere. > > The question is - and I think it's a fairly reasonable one: Where is > our Core, Handset, Netbook, IVI and SDK roadmaps for 1.2? It's not on > meego.com anywhere - how does our future platform 'customers' know > what we plan to have coming for MeeGo 1.2? > > And second: What is the current status of them - where can I see the > work in progress? Is there some featurezilla searches? > > Gavin, Sami, Rudolf, Ville and the rest of you guys responsible for > MeeGo roadmaps - could I ask you to spend some few minutes elaborating > to the rest of the project what's going on in Program Office regarding > the roadmaps for 1.2 for your areas? It'll help people understand why > these roadmaps may be missing and set up expectations to when we'll > see them :) > > Thank you in advance, > > BR > Carsten Munk > MeeGo Nokia N900 hardware adaptation maintainer > ___ > MeeGo-dev mailing list > 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
