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 <[email protected]>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:* [email protected] [mailto:[email protected]] *On
> Behalf Of *Rudolf Streif
> *Sent:* Monday, January 03, 2011 9:35 AM
> *To:* Hindman, Gavin
> *Cc:* [email protected]; [email protected]; [email protected];
> [email protected]; [email protected]
>
> *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 <[email protected]>
> 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:* [email protected] [mailto:[email protected]] *On
> Behalf Of *Rudolf Streif
> *Sent:* Monday, January 03, 2011 8:56 AM
> *To:* [email protected]
> *Cc:* [email protected]; [email protected]; Hindman, Gavin;
> [email protected]; [email protected]
>
>
> *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, <[email protected]> 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
[email protected]
http://lists.meego.com/listinfo/meego-dev

Reply via email to