I would think there is some lessons to be learned by those who run this site.
It took what amounted to less than a dozen people to basically bring this place to its knees. Ultimately, these very few people got EXACTLY what they were looking at getting.
Basically, the message being sent is: If you want to change something here, go get your band of thug computer geeks, a proxy server, and in a few hours it's game over.
These supposed development leaders acted like a bunch of punk highschool kids.
Pitty.
KOS
By the way, the Android development community is a lot larger than this forum. This sent shock waves throughout it. While you may have seen 12 or so vocal individuals, it was spreading like wildfire across the internet, and making serious waves. Even devs for apps most rooters here use, such as SetCPU showed their support for cyanogen and their disapproval for UD and how it was (not) being handled.
I wonder if you would have felt it was no big deal what BD did if the dev for SetCPU suddenly decided to remove Droid support because of all of this?
This was not a small matter, by any means. Whether it was right to close BD's forum or not, I don't know. I know if I was in BD's shoes, I would have take a piece of humble pie, given credit where due, and moved on.
Richard Stallman - Wikipedia, the free encyclopedia
This is where credit is due. I am a fan of open source. By the wiki even Linux had to take some humble pie.
Richard Stallman - Wikipedia, the free encyclopedia
By the way, the Android development community is a lot larger than this forum. This sent shock waves throughout it. While you may have seen 12 or so vocal individuals, it was spreading like wildfire across the internet, and making serious waves. Even devs for apps most rooters here use, such as SetCPU showed their support for cyanogen and their disapproval for UD and how it was (not) being handled.
I wonder if you would have felt it was no big deal what BD did if the dev for SetCPU suddenly decided to remove Droid support because of all of this?
This was not a small matter, by any means. Whether it was right to close BD's forum or not, I don't know. I know if I was in BD's shoes, I would have take a piece of humble pie, given credit where due, and moved on.
Richard Stallman - Wikipedia, the free encyclopedia
This is where credit is due. I am a fan of open source. By the wiki even Linux had to take some humble pie.
Richard Stallman - Wikipedia, the free encyclopedia
Yeah, I know, Linux is just the kernel, the rest is GNU, and the correct naming terminology is GNU/Linux OS.
I'm in complete agreement about that, by the way.
Which ROM version had SetCPU in it?
Richard Stallman - Wikipedia, the free encyclopedia
This is where credit is due. I am a fan of open source. By the wiki even Linux had to take some humble pie.
Richard Stallman - Wikipedia, the free encyclopedia
Yeah, I know, Linux is just the kernel, the rest is GNU, and the correct naming terminology is GNU/Linux OS.
I'm in complete agreement about that, by the way.
I didnt see the credit.
http://en.wikipedia.org/wiki/Richard_Stallman
By the way, the Android development community is a lot larger than this forum. This sent shock waves throughout it. While you may have seen 12 or so vocal individuals, it was spreading like wildfire across the internet, and making serious waves. Even devs for apps most rooters here use, such as SetCPU showed their support for cyanogen and their disapproval for UD and how it was (not) being handled.
I wonder if you would have felt it was no big deal what BD did if the dev for SetCPU suddenly decided to remove Droid support because of all of this?
This was not a small matter, by any means. Whether it was right to close BD's forum or not, I don't know. I know if I was in BD's shoes, I would have take a piece of humble pie, given credit where due, and moved on.
Which ROM version had SetCPU in it?
Shockwaves throughout the entire Android Dev Community... That is a bit of an exaggeration. The lions share of the Android Dev Community don't give a rip about UD and very likely CyanogenMOD.
There is defiantly lessons to be learned all around the table.
When it comes right down to it, what happened here was VERY minor.
I've seen commercial entities brand GPL code and shamelessly pass it off as proprietary solutions. Even in these situations, I've never seen a blowup like happened here.
Like I said, these android devs are like a bunch of kids. I've never seen anything like it.
KOS