Slashdot Mirror
All Cyanogen Services Are Shutting Down (cyngn.com)
Long-time Slashdot reader Nemosoft Unv. writes: A very brief post on
Cyanogen's blog says it all really: "As part of the ongoing consolidation of Cyanogen, all services and Cyanogen-supported nightly builds will be discontinued no later than 12/31/16. The open source project and source code will remain available for anyone who wants to build CyanogenMod personally." Of course, with no focused team behind the CyanogenMod project it's effectively dead. Building an Android OS from scratch is no mean feat and most users won't be able to pull this off, let alone make fixes and updates. So what will happen next?
Cyanogen had already laid off 20% of its workforce in July, and in November announced they had "separated ties" with Cyanogen founder and primary contributor Steve Kondik. One Android site quoted Kondik as saying "what I was trying to do, is over" in a private Google+ community, and the same day Kondik posted on Twitter, "Time for the next adventure." He hasn't posted since, so it's not clear what he's up to now. But the more important question is whether anyone will continue developing CyanogenMod.
UPDATE: Android Police reports that the CyanogenMod team "has posted an update of their own, confirming the shutdown of the CM infrastructure and outlining a plan to continue the open-source initiative as Lineage." The team posts on their blog that "we the community of developers, designers, device maintainers and translators have taken the steps necessary to produce a fork of the CM source code and pending patches."
UPDATE: Android Police reports that the CyanogenMod team "has posted an update of their own, confirming the shutdown of the CM infrastructure and outlining a plan to continue the open-source initiative as Lineage." The team posts on their blog that "we the community of developers, designers, device maintainers and translators have taken the steps necessary to produce a fork of the CM source code and pending patches."
Of course, the problem here is that development of huge massive codebases involve needing people to work on the boring stuff.
If this doesn't happen, then no, the code doesn't immediately break.
But over time, it gets harder and harder for the average developer to build.
And at some point, you have a couple of die-hards working on it, at which point it may as well be dead.
I
Except it has had zero effect on Google which is the only realistic target for MS doing an embrace, extend extinguish.
And, during that time period, windowsphone was extinguished.
No, this was just mismanagement by the CM guys.
Once MS got involved, it was going to be game over, man.
I'm hoping Sailfish continues to evolve....
More FOSS amateur shit crashes to the ground and burns. Never trust basement dwelling coders, if they were any good they would have been hired by reputable corporations and became professional programmers. Mediocrity and lack of social skills doom them to slave away on half-assed projects with no future at all. Stay away from this crap.