Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Hi gang, This list is kinda of lonely... So I thought I'd bring this thread back up. The wiki (http://wiki.meego.com/In-vehicle/Roadmap) has a number of features listed but not when they are target for. The bug site has these two items listed (using Meego Features-IVI Features -(meego release)1.2): 8704 ACCEPTED [FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI 11456 INDEFINITION [FEA] [MASTER] Provide OKI IVI IOH drivers for Stephenville platforms So the question is, are the two above the extent of the features expected for 1.2? Thanks, Nasa - jukka eklund jukka.ekl...@nokia.com wrote: 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 ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
On Friday, January 21, 2011, Nasa wrote: Hi gang, This list is kinda of lonely... So I thought I'd bring this thread back up. The wiki (http://wiki.meego.com/In-vehicle/Roadmap) has a number of features listed but not when they are target for. The bug site has these two items listed (using Meego Features-IVI Features -(meego release)1.2): So the question is, are the two above the extent of the features expected for 1.2? Thanks, Nasa I added the MeeGo IVI 1.2 planned features to the bottom of the In-vehicle/Roadmap page you referenced. Thanks for the reminder. Remember this is IVI specific and does not cover the other devices. regards Joel Clark MeeGo IVI program manager ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
- Joel Clark joel.cl...@intel.com wrote: On Friday, January 21, 2011, Nasa wrote: Hi gang, This list is kinda of lonely... So I thought I'd bring this thread back up. The wiki (http://wiki.meego.com/In-vehicle/Roadmap) has a number of features listed but not when they are target for. The bug site has these two items listed (using Meego Features-IVI Features -(meego release)1.2): So the question is, are the two above the extent of the features expected for 1.2? Thanks, Nasa I added the MeeGo IVI 1.2 planned features to the bottom of the In-vehicle/Roadmap page you referenced. Thanks for the reminder. Remember this is IVI specific and does not cover the other devices. regards Joel Clark MeeGo IVI program manager Joel, Good Stuff... Thanks Nasa ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Hi Jukka, jukka.ekl...@nokia.com wrote: 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. A good roadmap provides a number of things: * A vision for what the end goal is * A list of steps required to attain the goal * Clear labelling of ownership for each step, so that I know who is working on something, and which steps are not currently being done * Regular updates on progress towards the goal, as tasks are completed You can do queries like this: http://bugs.meego.com/report.cgi?x_axis_field=producty_axis_field=componentz_axis_field=query_format=report-tableshort_desc_type=allwordssubstrshort_desc=classification=MeeGo+Featuresproduct=MeeGo+Connected+TV+Featuresproduct=MeeGo+Core+OS+Featuresproduct=MeeGo+Handset+Featuresproduct=MeeGo+IVI+Featuresproduct=MeeGo+Netbook+Featuresproduct=MeeGo+SDK+featuresproduct=MeeGo+Tablet+Featuresversion=1.2version=1.2longdesc_type=allwordssubstrlongdesc=bug_file_loc_type=allwordssubstrbug_file_loc=deadlinefrom=deadlineto=emailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailqa_contact2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=votes=chfieldfrom=chfieldto=Nowchfieldvalue=format=tableaction=wrapfield0-0-0=nooptype0-0-0=noopvalue0-0-0= (all Accepted 1.2 features in products, grouped to components) This is a list of tasks (and problems to be addressed), but it falls down in other ways. There is no over-arching goal - when time pressure comes, how will tasks be prioritised to decide which ones to drop, and which ones to finish? And there is no clear opportunity to contribute - these tasks are, as you say, accepted features. How about the unaccepted features, those that we'd like to have, but that there are no resources to work on? It would be nice to use the roadmap as an opportunity to contribute. BTW, for Handset there is some material already in http://wiki.meego.com/Roadmap, in the form of high-level presentation from MeeGo conference. Thanks for the link! For some idea of what I hope to see in a roadmap, here's one of the best community roadmaps I'm aware of, Inkscape's: http://wiki.inkscape.org/wiki/index.php/Roadmap - the roadmap breaks down like this: 0.48 (next version): Starts with a goal for the release, then a detailed list of tasks that must be finished before we release a new version (includes features and bugs). 0.49 (n+1 version): Goal for the release, and some high level features to be done (these get broken down into smaller task lists as people take them on, after the 0.48 release) Following releases: The most important features goals we want to see accomplished, but that have not been included in the next milestone. Forms a basis for discussion after each release when discussing the high-level goals for n+2 release. The old roadmap for the project is here, showing how the project's roadmap developed over the years: http://wiki.inkscape.org/wiki/index.php/OldRoadmap Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Hi there, Carsten wrote: 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? See, comment, vote: Bug 9908 - Open roadmapping process defined but no implemented http://bugs.meego.com/show_bug.cgi?id=9908 I also think this is an important topic and I also expected more information or at least feedback from the roadmap owners at this point. 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 :) -- Quim ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Unfortunately, the MeeGo Bugzilla does not offer a field to distinguish between a bug and a feature. That's something that should be considered adding. For MeeGo IVI I have searched the database and compiled a list: Bugzilla ID Title 7668 [FEA] Multi Screen Support 7669 [FEA] Tethered Device Indexing 7670 [FEA] Multi Zone Audio 7671 [FEA] Distributed Audio Management 7672 [FEA] Network Gateway 7674 [FEA] Phonebook Sync with CE Device 7675 [FEA] Media Sync with home PC 7677 [FEA] Multi-User Support 7678 [FEA] IVI Fastboot 7679 [FEA] Persistency Management 7680 [FEA] Power Management 7681 [FEA] System Health Monitor 7682 [FEA] Inertia based Application control 8704 [FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI 8813 [FEA] Terminal Mode VNC Client 8814 [FEA] Remote Framebuffer Protocol 8815 [FEA] Integrate EMGD 1.0 Update user mode driver components 8816 [FEA] RFB Encodings 8817 [FEA] Terminal Mode 1.0 RFB extension messages 8818 [FEA] Terminal Mode UpnP Control Point 8819 [FEA] IVI document viewer 8821 [FEA] TmServerDevice:1 Device 8822 [FEA] IVI Nobody 8823 [FEA] Terminal Mode Audio 8824 [FEA] IVI Proximity 8827 [FEA] IVI Persistancy Control Manager 8828 [FEA] RTP Client supporting Terminal Mode payload 8829 [FEA] Terminal Mode Client Controller 9169 [FEA] Contacts should have routing integration 9171 [FEA] Weather app 9174 [FEA] Media player: FM/AM radio 9175 [fEA] MCP pluggable mass storage controls 9209 [FEA] btrfs compression during installation 9210 [FEA] Remove physical keyboard requirement 9211 [FEA] Enhance meego-handset-songs to a classed audio sources 9212 [FEA] Sample Sirius radio integration 9213 [FEA] Rebase Russellville tsc2007 touchscreen to evdev 10295 [FEA] Request for Bluetooth DUN support for both server and client role 10355 [FEA] UI should include a day/night mode 11256 [FEA] Over-the-Air (OTA) Updates [FEA-IVI-UX] Align IVI Home Screen with MeeGo Touch direction [FEA-IVI-UX] Unified Media Player [FEA-IVI-UX] Unified Dialler [FEA-IVI-UX] Navigation [FEA-IVI-UX] Document Viewer [FEA-IVI-UX] Picture Viewer [FEA-IVI-UX] Speech recognition The MeeGo IVI Working Group has identified the following high-level areas for the near-term roadmap: • App Store Demonstration • Automotive Networking • Audio management • Device connectivity • Navigation • Auto UX • BSP/ARM-support We are currently in process of fleshing them out. I will put this framework up on the IVI roadmap page on meego.com. :rjs On Mon, Jan 3, 2011 at 2:47 AM, quim@nokia.com wrote: Hi there, Carsten wrote: 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? See, comment, vote: Bug 9908 - Open roadmapping process defined but no implemented http://bugs.meego.com/show_bug.cgi?id=9908 I also think this is an important topic and I also expected more information or at least feedback from the roadmap owners at this point. 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 :) -- Quim ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
On 1/3/2011 2:47 AM, quim@nokia.com wrote: Hi there, Carsten wrote: 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? See, comment, vote: Bug 9908 - Open roadmapping process defined but no implemented http://bugs.meego.com/show_bug.cgi?id=9908 I also think this is an important topic and I also expected more information or at least feedback from the roadmap owners at this point. actually, given that we are where we are, I would like to see the program office come to the TSG meeting with a, say, 20 minute status update of where 1.2 is that way it's public, official and also it makes the TSG even more about the general good of the project ;) ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Bugs and features are filed under separate classifications - MeeGo Platform vs MeeGo Features - there are no bugs in MeeGo Features. __ Gavin Hindman SSG\OTC MeeGo Core Product Manager From: rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.com] On Behalf Of Rudolf Streif Sent: Monday, January 03, 2011 8:56 AM To: quim@nokia.com Cc: cars...@maemo.org; meego-dev@meego.com; Hindman, Gavin; sami.pienim...@nokia.com; ville.lavon...@nokia.com Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? Unfortunately, the MeeGo Bugzilla does not offer a field to distinguish between a bug and a feature. That's something that should be considered adding. For MeeGo IVI I have searched the database and compiled a list: Bugzilla ID Title 7668[FEA] Multi Screen Support 7669[FEA] Tethered Device Indexing 7670[FEA] Multi Zone Audio 7671[FEA] Distributed Audio Management 7672[FEA] Network Gateway 7674[FEA] Phonebook Sync with CE Device 7675[FEA] Media Sync with home PC 7677[FEA] Multi-User Support 7678[FEA] IVI Fastboot 7679[FEA] Persistency Management 7680[FEA] Power Management 7681[FEA] System Health Monitor 7682[FEA] Inertia based Application control 8704[FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI 8813[FEA] Terminal Mode VNC Client 8814[FEA] Remote Framebuffer Protocol 8815[FEA] Integrate EMGD 1.0 Update user mode driver components 8816[FEA] RFB Encodings 8817[FEA] Terminal Mode 1.0 RFB extension messages 8818[FEA] Terminal Mode UpnP Control Point 8819[FEA] IVI document viewer 8821[FEA] TmServerDevice:1 Device 8822[FEA] IVI Nobody 8823[FEA] Terminal Mode Audio 8824[FEA] IVI Proximity 8827[FEA] IVI Persistancy Control Manager 8828[FEA] RTP Client supporting Terminal Mode payload 8829[FEA] Terminal Mode Client Controller 9169[FEA] Contacts should have routing integration 9171[FEA] Weather app 9174[FEA] Media player: FM/AM radio 9175[fEA] MCP pluggable mass storage controls 9209[FEA] btrfs compression during installation 9210[FEA] Remove physical keyboard requirement 9211[FEA] Enhance meego-handset-songs to a classed audio sources 9212[FEA] Sample Sirius radio integration 9213[FEA] Rebase Russellville tsc2007 touchscreen to evdev 10295 [FEA] Request for Bluetooth DUN support for both server and client role 10355 [FEA] UI should include a day/night mode 11256 [FEA] Over-the-Air (OTA) Updates [FEA-IVI-UX] Align IVI Home Screen with MeeGo Touch direction [FEA-IVI-UX] Unified Media Player [FEA-IVI-UX] Unified Dialler [FEA-IVI-UX] Navigation [FEA-IVI-UX] Document Viewer [FEA-IVI-UX] Picture Viewer [FEA-IVI-UX] Speech recognition The MeeGo IVI Working Group has identified the following high-level areas for the near-term roadmap: * App Store Demonstration * Automotive Networking * Audio management * Device connectivity * Navigation * Auto UX * BSP/ARM-support We are currently in process of fleshing them out. I will put this framework up on the IVI roadmap page on meego.comhttp://meego.com. :rjs On Mon, Jan 3, 2011 at 2:47 AM, quim@nokia.commailto:quim@nokia.com wrote: Hi there, Carsten wrote: 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? See, comment, vote: Bug 9908 - Open roadmapping process defined but no implemented http://bugs.meego.com/show_bug.cgi?id=9908 I also think this is an important topic and I also expected more information or at least feedback from the roadmap owners at this point. 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.comhttp://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.comhttp://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 :) -- Quim ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Hindman, Gavin wrote: there are no bugs in MeeGo Features. Until they're written, presumably... ;) Cheers, Dave. -- maemo.org docsmaster Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Does not seem to work too well. Most folks won't see the feature link on the bottom of the New page and at least for me searching for features using the advanced search function also returns all bugs even though I explicitly selected Features only. :rjs On Mon, Jan 3, 2011 at 9:12 AM, Hindman, Gavin gavin.hind...@intel.comwrote: Bugs and features are filed under separate classifications – MeeGo Platform vs MeeGo Features - there are no bugs in MeeGo Features. __ Gavin Hindman SSG\OTC MeeGo Core Product Manager *From:* rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.com] *On Behalf Of *Rudolf Streif *Sent:* Monday, January 03, 2011 8:56 AM *To:* quim@nokia.com *Cc:* cars...@maemo.org; meego-dev@meego.com; Hindman, Gavin; sami.pienim...@nokia.com; ville.lavon...@nokia.com *Subject:* Re: [MeeGo-dev] MeeGo 1.2 Roadmap? Unfortunately, the MeeGo Bugzilla does not offer a field to distinguish between a bug and a feature. That's something that should be considered adding. For MeeGo IVI I have searched the database and compiled a list: Bugzilla ID Title 7668[FEA] Multi Screen Support 7669[FEA] Tethered Device Indexing 7670[FEA] Multi Zone Audio 7671[FEA] Distributed Audio Management 7672[FEA] Network Gateway 7674[FEA] Phonebook Sync with CE Device 7675[FEA] Media Sync with home PC 7677[FEA] Multi-User Support 7678[FEA] IVI Fastboot 7679[FEA] Persistency Management 7680[FEA] Power Management 7681[FEA] System Health Monitor 7682[FEA] Inertia based Application control 8704[FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI 8813[FEA] Terminal Mode VNC Client 8814[FEA] Remote Framebuffer Protocol 8815[FEA] Integrate EMGD 1.0 Update user mode driver components 8816[FEA] RFB Encodings 8817[FEA] Terminal Mode 1.0 RFB extension messages 8818[FEA] Terminal Mode UpnP Control Point 8819[FEA] IVI document viewer 8821[FEA] TmServerDevice:1 Device 8822[FEA] IVI Nobody 8823[FEA] Terminal Mode Audio 8824[FEA] IVI Proximity 8827[FEA] IVI Persistancy Control Manager 8828[FEA] RTP Client supporting Terminal Mode payload 8829[FEA] Terminal Mode Client Controller 9169[FEA] Contacts should have routing integration 9171[FEA] Weather app 9174[FEA] Media player: FM/AM radio 9175[fEA] MCP pluggable mass storage controls 9209[FEA] btrfs compression during installation 9210[FEA] Remove physical keyboard requirement 9211[FEA] Enhance meego-handset-songs to a classed audio sources 9212[FEA] Sample Sirius radio integration 9213[FEA] Rebase Russellville tsc2007 touchscreen to evdev 10295 [FEA] Request for Bluetooth DUN support for both server and client role 10355 [FEA] UI should include a day/night mode 11256 [FEA] Over-the-Air (OTA) Updates [FEA-IVI-UX] Align IVI Home Screen with MeeGo Touch direction [FEA-IVI-UX] Unified Media Player [FEA-IVI-UX] Unified Dialler [FEA-IVI-UX] Navigation [FEA-IVI-UX] Document Viewer [FEA-IVI-UX] Picture Viewer [FEA-IVI-UX] Speech recognition The MeeGo IVI Working Group has identified the following high-level areas for the near-term roadmap: • App Store Demonstration • Automotive Networking • Audio management • Device connectivity • Navigation • Auto UX • BSP/ARM-support We are currently in process of fleshing them out. I will put this framework up on the IVI roadmap page on meego.com. :rjs On Mon, Jan 3, 2011 at 2:47 AM, quim@nokia.com wrote: Hi there, Carsten wrote: 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? See, comment, vote: Bug 9908 - Open roadmapping process defined but no implemented http://bugs.meego.com/show_bug.cgi?id=9908 I also think this is an important topic and I also expected more information or at least feedback from the roadmap owners at this point. 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
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
I can't log in as anyone but myself, for obvious reasons, so I'm not sure what you mean by your first comment - are you saying that users with the lowest level of access cannot file feature requests? If so, that's a bug in the tool and should be submitted as such. As for the search, if you're selecting a Classification of MeeGo Features in the Advanced Search, you'll only get features returned - I do this every day. Additionally, all features have the string [FEA] in the Summary, so that can be included in the Quick Find search box if you only want to get features. __ Gavin Hindman SSG\OTC MeeGo Core Product Manager From: rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.com] On Behalf Of Rudolf Streif Sent: Monday, January 03, 2011 9:35 AM To: Hindman, Gavin Cc: quim@nokia.com; cars...@maemo.org; meego-dev@meego.com; sami.pienim...@nokia.com; ville.lavon...@nokia.com Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? Does not seem to work too well. Most folks won't see the feature link on the bottom of the New page and at least for me searching for features using the advanced search function also returns all bugs even though I explicitly selected Features only. :rjs On Mon, Jan 3, 2011 at 9:12 AM, Hindman, Gavin gavin.hind...@intel.commailto:gavin.hind...@intel.com wrote: Bugs and features are filed under separate classifications - MeeGo Platform vs MeeGo Features - there are no bugs in MeeGo Features. __ Gavin Hindman SSG\OTC MeeGo Core Product Manager From: rudolf.str...@gmail.commailto:rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.commailto:rudolf.str...@gmail.com] On Behalf Of Rudolf Streif Sent: Monday, January 03, 2011 8:56 AM To: quim@nokia.commailto:quim@nokia.com Cc: cars...@maemo.orgmailto:cars...@maemo.org; meego-dev@meego.commailto:meego-dev@meego.com; Hindman, Gavin; sami.pienim...@nokia.commailto:sami.pienim...@nokia.com; ville.lavon...@nokia.commailto:ville.lavon...@nokia.com Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? Unfortunately, the MeeGo Bugzilla does not offer a field to distinguish between a bug and a feature. That's something that should be considered adding. For MeeGo IVI I have searched the database and compiled a list: Bugzilla ID Title 7668[FEA] Multi Screen Support 7669[FEA] Tethered Device Indexing 7670[FEA] Multi Zone Audio 7671[FEA] Distributed Audio Management 7672[FEA] Network Gateway 7674[FEA] Phonebook Sync with CE Device 7675[FEA] Media Sync with home PC 7677[FEA] Multi-User Support 7678[FEA] IVI Fastboot 7679[FEA] Persistency Management 7680[FEA] Power Management 7681[FEA] System Health Monitor 7682[FEA] Inertia based Application control 8704[FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI 8813[FEA] Terminal Mode VNC Client 8814[FEA] Remote Framebuffer Protocol 8815[FEA] Integrate EMGD 1.0 Update user mode driver components 8816[FEA] RFB Encodings 8817[FEA] Terminal Mode 1.0 RFB extension messages 8818[FEA] Terminal Mode UpnP Control Point 8819[FEA] IVI document viewer 8821[FEA] TmServerDevice:1 Device 8822[FEA] IVI Nobody 8823[FEA] Terminal Mode Audio 8824[FEA] IVI Proximity 8827[FEA] IVI Persistancy Control Manager 8828[FEA] RTP Client supporting Terminal Mode payload 8829[FEA] Terminal Mode Client Controller 9169[FEA] Contacts should have routing integration 9171[FEA] Weather app 9174[FEA] Media player: FM/AM radio 9175[fEA] MCP pluggable mass storage controls 9209[FEA] btrfs compression during installation 9210[FEA] Remove physical keyboard requirement 9211[FEA] Enhance meego-handset-songs to a classed audio sources 9212[FEA] Sample Sirius radio integration 9213[FEA] Rebase Russellville tsc2007 touchscreen to evdev 10295 [FEA] Request for Bluetooth DUN support for both server and client role 10355 [FEA] UI should include a day/night mode 11256 [FEA] Over-the-Air (OTA) Updates [FEA-IVI-UX] Align IVI Home Screen with MeeGo Touch direction [FEA-IVI-UX] Unified Media Player [FEA-IVI-UX] Unified Dialler [FEA-IVI-UX] Navigation [FEA-IVI-UX] Document Viewer [FEA-IVI-UX] Picture Viewer [FEA-IVI-UX] Speech recognition The MeeGo IVI Working Group has identified the following high-level areas for the near-term roadmap: * App Store Demonstration * Automotive Networking * Audio management * Device connectivity * Navigation * Auto UX * BSP/ARM-support We are currently in process of fleshing them out. I will put this framework up on the IVI roadmap page on meego.comhttp://meego.com. :rjs On Mon, Jan 3, 2011 at 2:47 AM, quim@nokia.commailto:quim@nokia.com wrote: Hi there, Carsten wrote: 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? See, comment, vote
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Use Classification to distinguish Features from Bugs. Status does not filter for feature vs bugs, clicking on feature near the Status selector only changes the list of available Status filters, but since many of these Status filters are common (intentionally so) to bugs and features, it does not distinguish them. regards Joel From: meego-dev-boun...@meego.com [mailto:meego-dev-boun...@meego.com] On Behalf Of Rudolf Streif Sent: Monday, January 03, 2011 9:56 AM To: Hindman, Gavin Cc: meego-dev@meego.com; sami.pienim...@nokia.com; ville.lavon...@nokia.com Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? No, anyone can probably request features but the link to do so is tucked away at the end of the page where it may not be found by everybody. However, I am only making this assumption based on finding features classified as bugs. Yes, that works that way. I selected Status = Feature and that does not seem to work. No problem. Thanks, :rjs On Mon, Jan 3, 2011 at 9:40 AM, Hindman, Gavin gavin.hind...@intel.commailto:gavin.hind...@intel.com wrote: I can't log in as anyone but myself, for obvious reasons, so I'm not sure what you mean by your first comment - are you saying that users with the lowest level of access cannot file feature requests? If so, that's a bug in the tool and should be submitted as such. As for the search, if you're selecting a Classification of MeeGo Features in the Advanced Search, you'll only get features returned - I do this every day. Additionally, all features have the string [FEA] in the Summary, so that can be included in the Quick Find search box if you only want to get features. __ Gavin Hindman SSG\OTC MeeGo Core Product Manager From: rudolf.str...@gmail.commailto:rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.commailto:rudolf.str...@gmail.com] On Behalf Of Rudolf Streif Sent: Monday, January 03, 2011 9:35 AM To: Hindman, Gavin Cc: quim@nokia.commailto:quim@nokia.com; cars...@maemo.orgmailto:cars...@maemo.org; meego-dev@meego.commailto:meego-dev@meego.com; sami.pienim...@nokia.commailto:sami.pienim...@nokia.com; ville.lavon...@nokia.commailto:ville.lavon...@nokia.com Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? Does not seem to work too well. Most folks won't see the feature link on the bottom of the New page and at least for me searching for features using the advanced search function also returns all bugs even though I explicitly selected Features only. :rjs On Mon, Jan 3, 2011 at 9:12 AM, Hindman, Gavin gavin.hind...@intel.commailto:gavin.hind...@intel.com wrote: Bugs and features are filed under separate classifications - MeeGo Platform vs MeeGo Features - there are no bugs in MeeGo Features. __ Gavin Hindman SSG\OTC MeeGo Core Product Manager From: rudolf.str...@gmail.commailto:rudolf.str...@gmail.com [mailto:rudolf.str...@gmail.commailto:rudolf.str...@gmail.com] On Behalf Of Rudolf Streif Sent: Monday, January 03, 2011 8:56 AM To: quim@nokia.commailto:quim@nokia.com Cc: cars...@maemo.orgmailto:cars...@maemo.org; meego-dev@meego.commailto:meego-dev@meego.com; Hindman, Gavin; sami.pienim...@nokia.commailto:sami.pienim...@nokia.com; ville.lavon...@nokia.commailto:ville.lavon...@nokia.com Subject: Re: [MeeGo-dev] MeeGo 1.2 Roadmap? Unfortunately, the MeeGo Bugzilla does not offer a field to distinguish between a bug and a feature. That's something that should be considered adding. For MeeGo IVI I have searched the database and compiled a list: Bugzilla ID Title 7668[FEA] Multi Screen Support 7669[FEA] Tethered Device Indexing 7670[FEA] Multi Zone Audio 7671[FEA] Distributed Audio Management 7672[FEA] Network Gateway 7674[FEA] Phonebook Sync with CE Device 7675[FEA] Media Sync with home PC 7677[FEA] Multi-User Support 7678[FEA] IVI Fastboot 7679[FEA] Persistency Management 7680[FEA] Power Management 7681[FEA] System Health Monitor 7682[FEA] Inertia based Application control 8704[FEA] Smartphone Connectivity using Terminal Mode for MeeGo IVI 8813[FEA] Terminal Mode VNC Client 8814[FEA] Remote Framebuffer Protocol 8815[FEA] Integrate EMGD 1.0 Update user mode driver components 8816[FEA] RFB Encodings 8817[FEA] Terminal Mode 1.0 RFB extension messages 8818[FEA] Terminal Mode UpnP Control Point 8819[FEA] IVI document viewer 8821[FEA] TmServerDevice:1 Device 8822[FEA] IVI Nobody 8823[FEA] Terminal Mode Audio 8824[FEA] IVI Proximity 8827[FEA] IVI Persistancy Control Manager 8828[FEA] RTP Client supporting Terminal Mode payload 8829[FEA] Terminal Mode Client Controller 9169[FEA] Contacts should have routing integration 9171[FEA] Weather app 9174[FEA] Media player: FM/AM radio 9175[fEA] MCP pluggable mass storage controls 9209[FEA] btrfs compression during installation 9210[FEA] Remove physical keyboard requirement 9211[FEA
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
Hi, Hindman, Gavin wrote: I can’t log in as anyone but myself, for obvious reasons, so I’m not sure what you mean by your first comment – are you saying that users with the lowest level of access cannot file feature requests? If so, that’s a bug in the tool and should be submitted as such. When I click New to create a new bug/feature request, I can set the priority to enhancement, but I don't see any link marked Feature. I see now that there's a MeeGo Feature section at the bottom of http://bugs.meego.com/enter_bug.cgi but the thought didn't occur to me that I would have to click there - I think of feature requests being reported against products rather than separately. So for an IVI feature, for example, I clicked directly on Automotive user experience under the MeeGo Platform classification. As for the search, if you’re selecting a Classification of MeeGo Features in the Advanced Search, you’ll only get features returned – I do this every day. Additionally, all features have the string [FEA] in the Summary, so that can be included in the Quick Find search box if you only want to get features. I think the problem, as it is, comes from the filing of all features under a separate MeeGo features classification. While this may be useful for a subset of bugzilla users, it isn't exactly intuitive for those who aren't aware of how the project teams are using the classifications. Cheers, Dave. -- Email: dne...@maemo.org Jabber: bo...@jabber.org ___ MeeGo-dev mailing list MeeGo-dev@meego.com http://lists.meego.com/listinfo/meego-dev
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
That is the case, yes. Any new high priority feature requests for 1.2 have to go through some level of CCB, and pretty much have to be drop-ins, at this point. __ Gavin Hindman SSG\OTC MeeGo Core Product Manager -Original Message- From: Arjan van de Ven [mailto:ar...@linux.intel.com] Sent: Monday, January 03, 2011 10:33 AM To: Dave Neary Cc: Hindman, Gavin; meego-dev@meego.com; sami.pienim...@nokia.com; ville.lavon...@nokia.com 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
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=producty_axis_field=componentz_axis_field=query_format=report-tableshort_desc_type=allwordssubstrshort_desc=classification=MeeGo+Featuresproduct=MeeGo+Connected+TV+Featuresproduct=MeeGo+Core+OS+Featuresproduct=MeeGo+Handset+Featuresproduct=MeeGo+IVI+Featuresproduct=MeeGo+Netbook+Featuresproduct=MeeGo+SDK+featuresproduct=MeeGo+Tablet+Featuresversion=1.2version=1.2longdesc_type=allwordssubstrlongdesc=bug_file_loc_type=allwordssubstrbug_file_loc=deadlinefrom=deadlineto=emailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailqa_contact2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=votes=chfieldfrom=chfieldto=Nowchfieldvalue=format=tableaction=wrapfield0-0-0=nooptype0-0-0=noopvalue0-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
Re: [MeeGo-dev] MeeGo 1.2 Roadmap?
2011/1/3 jukka.ekl...@nokia.com: 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=producty_axis_field=componentz_axis_field=query_format=report-tableshort_desc_type=allwordssubstrshort_desc=classification=MeeGo+Featuresproduct=MeeGo+Connected+TV+Featuresproduct=MeeGo+Core+OS+Featuresproduct=MeeGo+Handset+Featuresproduct=MeeGo+IVI+Featuresproduct=MeeGo+Netbook+Featuresproduct=MeeGo+SDK+featuresproduct=MeeGo+Tablet+Featuresversion=1.2version=1.2longdesc_type=allwordssubstrlongdesc=bug_file_loc_type=allwordssubstrbug_file_loc=deadlinefrom=deadlineto=emailassigned_to1=1emailtype1=substringemail1=emailassigned_to2=1emailreporter2=1emailqa_contact2=1emailcc2=1emailtype2=substringemail2=bugidtype=includebug_id=votes=chfieldfrom=chfieldto=Nowchfieldvalue=format=tableaction=wrapfield0-0-0=nooptype0-0-0=noopvalue0-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. Hi, Thanks for pointing this out :) I guess some customized featurezilla queries added to the roadmap wiki pages to help list those would go a long way, so we have something to point people to. What I'm looking for is basically a listing of the features accepted on the roadmap for 1.2 for various areas. For people/companies interested in contributing, 'NEW' listings could be useful for seeing what they can propose to be responsible for, in order to get it implemented. The current links point to features with indefinition and new, which doesn't help to clear up the picture of what's going to be delivered/planned. In addition to the featurezilla stuff, some information about deadlines for 'ACCEPTED' for 1.2 and when 1.3 planning starts, would be useful - some insight in your processes, if any exist :) Best regards, Carsten Munk -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
