dneary said: What can we do to ensure continuity after MeeGo? What do you mean with this sentence? The scope of http://bugs.maemo.org is and will be the Maemo platform.
When it comes to the platform and apps developed by Nokia, the continuity will be defined by the Maemo 5 maintenance releases. We will need to find a way to move forward to MeeGo the relevant reports not addressed in Maemo. There are several categories of reports based on the components they relate to: - OSS components also maintained in MeeGo: should they find their way to http://bugs.meego.com ? And additional factor to consider is that even if the components are the same, in the Harmattan timeframe they will differ in packaging and perhaps this have further implications. This needs to be discussed in the MeeGo context as well. - OSS components not maintained in MeeGo: either they move forward as MeeGo community projects or they will get out of scope somehow. - Proprietary components common in Maemo 5 and MeeGo releases from Nokia. As I see it, the MeeGo Devices team at Nokia and the community really need to find a common agreement on these. They are the most problematic when it comes to address Bug 630 Increased Bugzilla transparency - get the developers involved!. Maybe we should remove them from any Bugzilla and place them in a different context for gathering user feedback and testing. Nokia Pilots comes to mind. I need to check with the owners of these components. If you have opinions please waive them out here.