4 ms·
Android master HEAD is always proprietary and always has been. Android master HEAD also fails Andy Rubin's own definition of open: https://twitter.com/Arubin/st
by nailer 14y ago
Android master HEAD is always proprietary and always has been. Android master HEAD also fails Andy Rubin's own definition of open: https://twitter.com/Arubin/status/27808662429 https://twitter.com/Arubin/status/27808662429, since that website is out of date.
Only a few people inside Google are allowed to see it. Their colleagues aren't allowed to sit in the same cafeteria as the Android developers, much less see the source code, until it's already done.
If it was actually Open Source, XDA developers would actually have real, original development, and features like lock screen widgets, officially added in JB 4.2 in 2012, would have been completed by the community in 2009.
Only old, already released versions of Android are Open Source. This makes it useless for real developers - who would want to fix something that might already be a non-issue as of six months ago?
As a result, the only 'community development' in Android is people who know how to tweak settings files and make ROMs with particular apps and settings built in.
- ajross 14y agoAll of this is true. But it's not the choice between two extremes. Google doesn't have to wall off community development in order to develop new features in secret. There's no reason they couldn't curate an AOSP project where submissions like this one (although obviously not this particular one!) could be made in a way that was truly useful to the community. It would cost money and time, and maybe they don't have that. But it's something that other FOSS players do, so it's not an impossibility.
- eloisant 14y agoWell, if they work on version n+1 internally and secretly it's highly unlikely a patch for version n will have any value. In order for patches to be relevant, they should be on the HEAD of the project where most developers are working, not the old, released, finished, version.
- ibrahima 14y ago> If it was actually Open Source, XDA developers would actuall have real, original development, and features like lock screen widgets, officially added in JB 4.2 this year, would have been completed by the community in 2009. I agree in general that if AOSP was an actual open source project things would be better but I don't think XDA would be any different. It's been full of end users for years now and most of them are easily fooled by stuff like this. CyanogenMod is developed in the open and they do have quite a few contributors, but it's not terribly ground breaking (although some of their features do get reimplemented in AOSP eventually). The fact is that the Android project is really a gigantic codebase and it takes a lot of time to get started (and even on a really fast machine, 20-40 minutes to build), and a lot of the work CyanogenMod developers do is porting to hardware that's unsupported by AOSP, not feature development.
- VikingCoder 14y agoAndroid is open soure - it's just not developed in an open, community manner. The existence of Cyanogenmod and Amazon Kindle Fire prove that you are over-stating the case.
- nailer 14y agoCyanogenmod doesn't have access to the current android source. The current test release, 10.1 is based on Android 4.2, there is no version based on the actual current android source code as that is not available to anyone who isn't a Google employee on the Android team. The kindle fire is a fork of Android 2.x.
- gbog 14y agoAnd? I mean, ok, we get it, the most recently committed code is not open yet, probably because Google would prefer its flagship phones not be spoiled. So what? My phone runs an OS whose code is on github, and I install new versions when I choose to do so, from nightly builds.
- nailer 14y agoAnd all the drawbacks I cited in the original post, ie, nobody outside the Android team bothers contributing anything, and the project has less developers and less features than it would if it were truly open. Why would new phones be 'spoiled' if their source code was released?
- gbog 14y ago> nobody outside the Android team bothers contributing anything Do you have any figures to back this claim? Somewhere above or below a guy said he did send a patch. > less developers and less features than it would if it were truly open Very unlikely. Were it fully open (say, the Linux-way), it would not be pushed forward so steadily by Google, it would not have so many high-end apps (many written by Google), it would not have such a big piece of the market, it would not be the solution of choice for manufacturers, etc. I also wish Android to be more open, and I hope we will see soon emerge a "Landroid" that will be to Android what Linux is to Unix, and probably Cyanogenmod is paving its path, but this is no reason to spit in the soup: Android is a giant step forward and without it we would be all sandwiched in a MS-Apple cross-fight. > Why would new phones be 'spoiled' if their source code was released? Suppose the most recent feature developed by Google on Android reveals that their next phone will have two-faced screens, wouldn't you think Google might prefer to decide when and how this new phone will be announced? As a result, we have a slightly lagging opening of the source code. It is sad, but better than nothing.
- lwf 14y ago> Their colleagues aren't allowed to sit in the same cafeteria as the Android developers Well, the Android cafe isn't advertised to Googlers, but any Googler can dine there.
- nailer 14y agoPerhaps things have changed since 2010 then.