>"join someone else's project, don't start your own" That is true for a lone developer, but when you already have multiple development teams and communities, it's a slightly different argument.
MeeGo is pushing some radical new ideas about UI design that would be difficult to get pushed through an established project. I think MeeGo has every right to exist as its own project and there are plenty of good reasons to start with moblin instead of debian. I agree entirely that we should criticize any action to keep portions closed, but I don't think it's fair to criticize MeeGo's reasons for existing. Eli On Jul 8, 2010 4:20 AM, "Jeremiah Foster" <[email protected]> wrote: On Jul 7, 2010, at 18:51, Dirk Hohndel wrote: >> I'm not sure that will happen if I will use a com... This is why MeeGo should not exist and Intel should have contributed to Debian from the beginning, before Moblin. In the words of Dan Frye at IBM "Join someone else's project, don't start your own." Debian already builds on MIPS, ARM, IA, PPC, and many more platforms besides. Many companies donate machines to the Debian build system and Intel could have joined there focusing on their resources on their platform inside Debian. You still could have built on the OBS and kept your secret sauce secret, you just would have had cross architecture support (along with Debian's quality assurance and security services) out of the box. This doesn't mean MeeGo isn't "open", it is, its just that it is not as open / agnostic as other distros and the community sometimes finds that a hurdle, like when they want to port MeeGo. Jeremiah _______________________________________________ MeeGo-dev mailing list [email protected] http://li...
_______________________________________________ MeeGo-dev mailing list [email protected] http://lists.meego.com/listinfo/meego-dev
