Hi, Patrick Ohly wrote: > On Tue, 2010-08-31 at 17:19 +0100, Luiz Augusto von Dentz wrote: >> Well, I can implement it, Im not sure why you guys are pointing to >> meego bugs when meego is suppose to use what is upstream, > > *If* an upstream project is used, *then* the policy is to work upstream. > But there's no policy that all code in MeeGo has to be released and > maintained as a separate upstream project. Many core components were > specifically developed for Harmattan and MeeGo.
Certainly the impression I got during the MeeGo sessions at the Linux Foundation Collaboration Summit last year was that Nokia and Intel projects *would* become upstreams for MeeGo. The intention was to have the MeeGo specific projects be upstreams for MeeGo the distribution - each project would have a maintainer, web pages, bug tracking, etc. which would be used by the development team, and then MeeGo the project would pull releases off them. There was a specific question about how project governance would be handled when MeeGo was both upstream and downstream, but (at the time) the question was not addressed in detail. > At the moment, Buteo is getting developed inside Nokia: all the > developers are from Nokia, code gets committed to Nokia-internal repos, > the change log contains only references to a closed issue tracker that > (presumably) covers the next Nokia product. What would be needed to open up Buteo for collaborative development? Cheers, Dave. -- maemo.org docsmaster Email: [email protected] Jabber: [email protected] _______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
