Related
[Mods: I felt that this thread is most appropriate in this section as it pertains specifically to Android development. If you feel this is not the case and should be moved, please do so.]
As many of us know, Eugene and TeamWhiskey both released completely working Froyo ROMs today, and they were able to do so with leaked code that both were asked not to divulge. There's been some infighting between developers, and the use of the leaked code is the major point of contention.
What interests me is how developers have been respecting the GPL. As a major free/open source supporter, the fact that how this license permits developers and users alike to use any source code has not been respected scares me. I certainly don't want to see development of our phones fall by the wayside because some developers have access to code that others don't, when that code [or at least, the source code of developed ROMs that use leaked code] is legally required to be released to the public. (source, and examples of the GPL's standing in an American court of law)
Based on the current events and major milestones in Android development, I'm interested to see if anyone else agrees with me. (Or perhaps I'm wrong entirely - but there's a sticky on the top of this forum reminding developers about abiding by the GPL, so I assume that any ROM or kernel we've seen is GPL-derived.) I realize that some aspects of the Samsung version of Android in particular is under a proprietary license (TouchWiz, RFS), and this little point gets touchy. But Android itself and kernels for Android are GPL - so shouldn't any source code used by any Android project be released?
honestly? I'm concerned about the GPL implications too but I'm 100% sure that I don't have enough information to try to form an opinion about what's right or wrong in this scenario. I'm sure there is a lot going on in the background the average user such as myself doesn't know of what's going on here. edit: trying to speculate here is just too hard to guess, and would invoke both drama and the answers are not backed by anyone.
If you're not sure, ask the FSF.
Eugene and Sombionix need to take up their issues privately (and have since), and that was their only mistake. The rest of the scenario is simply not appropriate to come up publicly.
Although, I agree with the fact that the GPL has to be followed, the GPL only applies to source code. From what I gather, neither of these parties have any source code. They are both in the possession of a leak ROM. The word source here is used to mean the ROM from which the files came from.
When it comes to leaks, files in leaks CAN be traced back to the leak in some cases which is why many times, leaks cannot and will not be shared.
On the other hand, if they have the source code and it has been modified, then they must abide by the GPL.
One thing to consider here is that to the best of my knowledge, nobody other than Samsung at this point has the source to the SGS FroYo builds. What I mean by that is; everything that went on regarding the leak, is based off of binary files taken from a working phone. No source code involved. Google has released the code to 2.2, which satisfies the GPL licensing; with which Samsung has added proprietary software on top of for use with their phones, but because what they have added is NOT GPL'd, are not obligated to provide the source for.
I might be mistaken here, but assuming Samsung didn't change any of the existing AOSP code, and only added their proprietary software on top, then the 'must provide source code' clause is in fact being satisfied by Google. All Samsung needs to do to cover their behinds is provide a link to Google's Android development pages.
if it was GPLv3 we wouldn't have this problem, but a lot of companies are unwilling to jump to GPLv3 instead of GPLv2.
To clarify the position XDA takes on GPL code (having worked on the GPL policy you see at the top of every forum), it is required to release kernel sources if you have access to them.
It seems likely that no source code was available here, and the use of leaks in ROMs has been standard practice for a long time on XDA, and on other sites. There's no issue with this, and it is a signal of trust from the leaker to the developer that the source file will not be made available. Thus you are unlikely to get access to such leaks as a user, though you can enjoy the fruits of them after established developers with contacts have got access to them.
If it were insisted that sources be provided for EVERYTHING, then releases like this would be in breach of the XDA GPL code, and thus would stifle development. Samsung has not provided them with the sources (as I understand), so they have no obligations as far as I can identify, beyond passing on any standard notices placed in the ROM by Samsung, offering source code.
If a custom kernel was compiled to use the ROM, then its sources would be required under the GPL. The actual ROM itself is not GPL'd as such, and treating it as such would be detrimental to users on XDA.
If GPL sources have been used, then they must be posted per the GPL. Otherwise, there are no further obligations per the XDA rules. This does not appear to be the case here.
Just to back up this point, I worked on and released some ROMs, and never touched a line of source code personally. It's possible to do a surprising amount to ROMs without actually editing sources (often they're not available either when working on HTC devices...). It's only within the last month or two that I've actually looked at source code properly with intent on making changes.
Finally, I'll move this into general with a redirect for just now, as it's not directly related to a ROM, though is "on topic".
Ah - so the leaked code used to finish both Eugene's and Team Whiskey's was not code, but binaries (i.e., a leaked ROM?) This makes a lot more sense to me. Thanks for clarification.
I suppose this point becomes moot when froyo finally drops officially, but it's still important.
Sent from my SGH-T959 using XDA App
Well said Pulser_g2
Pulser.......Well said. The important thing people need to remember is not to "create" drama where it is not. The Dev's do work in concert and do produce amazing results contrary to the public chatter.
It is a blessing that there are so many good developers working on the Vibrant vs, say ...(you insert phone of choice). ......now off to flash............
As I mentioned in one of the Froyo threads, I feel like the GPL doesn't really apply in the case of leaked ROMs, since 1) nobody has the source anyway and 2) they're chock full of closed source Samsung bits. The leaked ROMS, and any ROM derived from it in some way, is already questionable to redistribute since Samsung hasn't granted permission to do so.
On the other hand, I do wish people would release source to any modifications of the Linux kernel and any other GPL software that's acquired through legitimate channels. I can understand that the source might be released slightly later than the binary, but most kernels at this point haven't had any source accompany them, ever. This really isn't in the spirit of the GPL, and as a long time Linux user it came as a surprise to me that this is the way things seem to work here.
The bottom line is that, like it or not, people actually don't have the *right* to not release source eventually. I hope they start doing so sooner rather than later.
Looks like a lot of people don't understand the GPL, even senior moderators.
We ARE talking about the GPL, not LGPL, right?
Samsung hasn't made any of the stuff they have posted official... Why would samsung release anything for something that is not yet official...
How would the devs of xda be able to give you the source they don't have?
If you want to fight a losing battle email htc about the mytouch slide..
Sent from my SGH-T959 using XDA App
First, I'm not trying to start a web battle here, just stating the facts.
1. The files that I received from our source gave me consent via email to build a rom and release it. Unfortunately, after the fact the rom was built and released, the source has been claiming that he did not want the files released, which was not at all what was discussed originally. Had he clearly stated that he did not want them released, I would not have done so. He specifically asked me to build a rom, but that he did not want his identity released, which I did not do.
2. You information regarding GPL is very wrong. We were not working from souce because source for the Vibrant 2.2 has not yet been released. The only Galaxy S device that has had source officially released has been the I9000. Had we been working from source, we would have gladly posted our edited source code with accordance with GPL law.
sombionix said:
2. You information regarding GPL is very wrong. We were not working from souce because source for the Vibrant 2.2 has not yet been released. The only Galaxy S device that has had source officially released has been the I9000. Had we been working from source, we would have gladly posted our edited source code with accordance with GPL law.
Click to expand...
Click to collapse
Yeah, this was my mistake. I was under the impression that you were working from source, not just a ROM, as was previously pointed out. So I guess it's a moot point.
Moto mde a stament http://sourceforge.net/motorola/atrix/discussion/general_comments/thread/9f80b745/
gb source by 7/29
So with the official 4.5.91 finally being populated to everyone through regular channels (not our awesome quicker than the maker methods ). We gain the right to demand from motorola to release the source, as according to GPL, if someone ask for the source they must release it.
Thanks joe for finding all the info on the specific lincese
Android Open Source Project license
http://source.android.com/source/licenses.html
GPL http://www.gnu.org/copyleft/gpl.html
GPL V2 http://www.gnu.org/licenses/gpl-2.0.html
LGPL http://www.gnu.org/copyleft/lesser.html
Apache License V2 http://www.apache.org/licenses/LICENSE-2.0
ubuntu licensing http://www.ubuntu.com/project/about-ubuntu/licensing
Q: Why should I care if moto releases the source or not?
A: Do you want AOSP rom, and CM7, maybe MIUI. all of this are dependent on the source. otherwise is super mega complicated to create them. And available source guarantees more devs.
So what is the plan?
Simple, the plan is to demand the source, a lot, A LOT! So they dont pull the same stunt they did with 4.1.83 update. The source for that became available last week!
So we are going to do this 2 ways! The official way, and the troll way.
The official method to request source is by writing a letter to motorola mobile to the following address.
Motorola Mobility, INC.
OSS Management
600 North US hwy 45
Libertyville, IL
60048, USA
The letter of course:
I ___________ write to request the release of the source code for the following software:
The 4.5.91 firmware update for motorola Atric 4g, the webtop included in the update, and any particular software included in this update that follows GPL licensing.
The second method, the troll way. Is simply to flood the motorola forums and requested there!
Tell everyone about this effort, we need source code right away!
on twitter use this hashtag #tsib #gpl
I love these ****ing topic names lmao
Sent from my MB860 using XDA App
neer2005 said:
I love these ****ing topic names lmao
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Me to haha i dont even have the atrix but saw this as soon as i opened the xda app haha but HTC is pulling the same **** with the evo. We got this damn ota like a month and a half ago and we still dont have the ****ing source
Sent from my PC36100 using XDA App
samcripp said:
So with the official 4.5.91 finally being populated to everyone through regular channels (not our awesome quicker than the maker methods ). We gain the right to demand from motorola to release the source, as according to GPL, if someone ask for the source they must release it.
Q: Why should I care if moto releases the source or not?
A: Do you want AOSP rom, and CM7, maybe MIUI. all of this are dependent on the source. otherwise is super mega complicated to create them. And available source guarantees more devs.
So what is the plan?
Simple, the plan is to demand the source, a lot, A LOT! So they dont pull the same stunt they did with 4.1.83 update. The source for that became available last week!
So we are going to do this 2 ways! The official way, and the troll way.
The official method to request source is by writing a letter to motorola mobile to the following address.
Motorola Mobility, INC.
OSS Management
600 North US hwy 45
Libertyville, IL
60048, USA
The letter of course:
I ___________ write to request the release of the source code for the following software:
The 4.5.91 firmware update for motorola Atric 4g, the webtop included in the update, and any particular software included in this update that follows GPL licensing.
The second method, the troll way. Is simply to flood the motorola forums and requested there!
Tell everyone about this effort, we need source code right away!
on twitter use this hashtag #tsib #gpl
Click to expand...
Click to collapse
Do we flood the Motorola support tread? Or their Dev tread? I'm on board.
Gr8Danes said:
Do we flood the Motorola support tread? Or their Dev tread? I'm on board.
Click to expand...
Click to collapse
the dev thread!
Link to the dev tread anyone?
Sam,
Are you taking initiative to write a letter to Motorola? If you do, I'm sure the XDA community would be obliged to take care of the flooding.
mpalatsi said:
Sam,
Are you taking initiative to write a letter to Motorola? If you do, I'm sure the XDA community would be obliged to take care of the flooding.
Click to expand...
Click to collapse
well considering i took the initiative to spread the word of finding the unlock, and then my handle got submited to a few international gadget sites as responsible for finding the unlock from the test servers. maybe writing to moto myself could be a bad idea. i def dont want to face any legal problems. but i will encourage anyone who wants to write them to do so, ill even write the letter and paste it for you guys, a stamp is only 45 cents!
Please some direction to help, @ or#
Swyped from 'mount' Olympus
Going on dev forum now, commence troll method.
Sent from my MB860 using XDA Premium App
https://supportforums.motorola.com/thread/54476 in the support tread too.
Lemme first be a little polite.
Dear Motorola,
You have already done your best to turn the Atrix into a dead bird. The GS2 and G2X have better fan following because you locked the bootloader, now we request you to release the source of the GB update ASAP so we can get to work with the code and bring some CM magic to the Atrix
Click to expand...
Click to collapse
Where in the Dev forums do you post? Can someone link?
Edit: here is the link for those that would like to add
https://sourceforge.net/motorola/atrix/discussion/
is it possible to build AOSP on a beta source? ... cuz befor 2 days they release 2.3 to beta testers
I've also started trolling their Developers facebook page. You guys should help me.
http://www.facebook.com/motodev?sk=wall
this does not apply to only folks on att, international users need to help to get source as well. we can compile cm for everyone globaly if we get this source. so please lets make an effort everybody!
T-t-t-t-trollin' everywhere I can
Joe did a bit of research and found every license moto has to comply with!
Android Open Source Project license
http://source.android.com/source/licenses.html
GPL http://www.gnu.org/copyleft/gpl.html
GPL V2 http://www.gnu.org/licenses/gpl-2.0.html
LGPL http://www.gnu.org/copyleft/lesser.html
Apache License V2 http://www.apache.org/licenses/LICENSE-2.0
ubuntu licensing http://www.ubuntu.com/project/about-ubuntu/licensing
Sounds uneducated and stupid.
Rikuumi said:
Sounds uneducated and stupid.
Click to expand...
Click to collapse
What does?
Have anyone found kernel source for this model?
i have seen discussion on roms without gpl, and is this model released with kernel source available?
I believe Google has not released source for Honeycomb yet. That is the answer I got when I asked the same question over at thriveforums.org.
mknewman said:
I believe Google has not released source for Honeycomb yet. That is the answer I got when I asked the same question over at thriveforums.org.
Click to expand...
Click to collapse
indeed google have, and kernel source needs to be posted, or roms on this forum seems to be illegal.. xda don't allow roms with a gpl kernel without source code linked, if its posted..
so thats pretty sad for toshiba.
even android 3.2 source is available, so toshiba thrive has to release their source now.. but 3.1 will do fine to begin with.
This is how it works. Various parts of the software are licensed by different entities. So the Android source includes Google's code and anything Toshiba does is affected. Android is under and open source license, but it is built on top of GNU/Linux. The Linux kernel is under the Greater Public License which requires the source to be distributed or accessible by request online when the binary is distributed. Typically as companies go though their code making sure they only release source they are supposed to and don't accidentally release proprietary code it may take them a while to post it. Regardless it must be posted or things get a little hot when advocates press for it.
exactly, xda rules says no uploads on information roms including gpl kernels without source included..
so its kinda funny if toshiba continue not to post it. maybe i should request it from toshiba somewhere..
The Kernal has been requested multiple times over on the Toshiba run forum. Users have even started to pull out the legal aspect of it citing the 30 day requirement and expamples of HTC getting into hot water when they passed that deadline.
I think Toshiba is just now realizing they HAVE to post it.
I started a thread over on Toshiba's forum and indeed did explain that they have 30 days to release. "Jim" said he would look into it but then came back and made it sound like "contact our legal team".
Precedent has been set - GPL breaking software is not allowed on XDA, specifically in the a500 forum. This primarily refers to kernels. Software that breaks GPL is considered "warez" - aka illegally distributed software.
Recently there has been an unofficial leak of an early version of Android 4.0 for the a500 tablet. This software contained a Linux kernel. The source code for this kernel has not been released, even though Linux kernels are required to have the sources posted to be GPL compliant. This makes the a500 ICS leak "warez" which are not allowed on XDA. There are also custom ROMs containing the leaked kernel, posted in the development forum. Since this kernel may differ from the final version, there is a possibility the source for it may never be released, setting it status as "illegal" software in stone.
According to XDA policies, and set precedent, the creators of the offending software (the custom ROMs) must provide the kernel source code, or have their offemding work, as well as their user accounts, banned from XDA. All other re-postings of the offending software (all sources of the ICS leak) must also be removed, per XDA policy and set precedent.
Just to clarify, Acer did NOT leak this ROM, it was leaked completely unofficially. Acer will release their kernel source code once they officially release the ROM.
Very good point. However, that emphasize my point even further - since this is an unofficial early leak, source code for this kernel may change before the final version is released, meaning there is a possibility that we will NEVER get the source code for this specific kernel. According to XDA rules and precedent, that makes it guarenteed "warez"
mtmerrick said:
Precedent has been set - GPL breaking software is not allowed on XDA, specifically in the a500 forum. This primarily refers to kernels. Software that breaks GPL is considered "warez" - aka illegally distributed software.
Recently Acer has leaked an early version of Android 4.0 for the a500 tablet. This software contained a Linux kernel. The source code for this kernel has not been released, even though Linux kernels are required to have the sources posted to be GPL compliant. This makes the a500 ICS leak "warez" which are not allowed on XDA. There are also custom ROMs containing the leaked kernel, posted in the development forum.
According to XDA policies, and set precedent, the creators of the offending software (the custom ROMs) must provide the kernel source code, or have their offemding work, as well as their user accounts, banned from XDA. All other re-postings of the offending software (all sources of the ICS leak) must also be removed, per XDA policy and set precedent.
Click to expand...
Click to collapse
this shows how bureaucracy kills. this is hilarious.
updated OP with clarification. Thanks to floating fat man
yes the hypocrisy is rampant, the irony, tasty as ics
Sent from my A500 using Tapatalk
Lol.
How can you hold acer responsible for violating GPL when they didn't release the ROM?
That's like someone winning a PS3 the day before it was released and then suing the guys that held the contest for breaking street date.
Good luck with that.
teflontactics said:
Lol.
How can you hold acer responsible for violating GPL when they didn't release the ROM?
That's like someone winning a PS3 the day before it was released and then suing the guys that held the contest for breaking street date.
Good luck with that.
Click to expand...
Click to collapse
no one's blaming Acer. the posting of the leak violates the rules of this forum, just as the posting of Thor's roms, even links to his site, are a violation of the forum rules.
Sent from my A500 using Tapatalk
Somairotevoli said:
no one's blaming Acer. the posting of the leak violates the rules of this forum, just as the posting of Thor's roms, even links to his site, are a violation of the forum rules.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
Correct! And the makers of ROMs that include this kernel are even more in trouble. That is, if the mods follow their own rules, which they seem to take very seriously.....
mtmerrick said:
Correct! And the makers of ROMs that include this kernel are even more in trouble. That is, if the mods follow their own rules, which they seem to take very seriously.....
Click to expand...
Click to collapse
I think having the source and not releasing it (Thor) is different than not having the source and not releasing it (leak based rom devs).
There were plenty of gingerbread roms running around the inspire 4g forum that were up BEFORE HTC actually released the source code for the kernel. So were the devs of the roms running the kernel in violation of the GPL or was it HTC since it was their kernel and therefore was their source code to release?
The problem is that Acer is not required to release the source for that kernel, since it is a leak and wasn't supposed to be publicly released.
Also, you seem way too excited about potentially killing the recent spark in development that has taken place around here recently. If the mods need to remove them, they will and they will handle it how they see fit.
This thread = garbage.
just playing devils advocate here. so if one was to share their private kernel with a few friends and one of those friends chose to "leak" it here, it would be acceptable?
Sent from my A500 using Tapatalk
wolverine423 said:
I think having the source and not releasing it (Thor) is different than not having the source and not releasing it (leak based rom devs).
There were plenty of gingerbread roms running around the inspire 4g forum that were up BEFORE HTC actually released the source code for the kernel. So were the devs of the roms running the kernel in violation of the GPL or was it HTC since it was their kernel and therefore was their source code to release?
The problem is that Acer is not required to release the source for that kernel, since it is a leak and wasn't supposed to be publicly released.
Also, you seem way too excited about potentially killing the recent spark in development that has taken place around here recently. If the mods need to remove them, they will and they will handle it how they see fit.
This thread = garbage.
Click to expand...
Click to collapse
Actually, not only were they at fault for using illegal software in their ROM, every android user who has a non-GPL compliant kernel is breaking the law - they are in possession of illegally distributed software.
Kinda shows how stupid the XDA rule is, doesn't it? That's what I'm trying to do, which most everyone else in the thread has understood; showing how rediculous using GPL compliance as a forum weapon is
mtmerrick said:
Kinda shows how stupid the XDA rule is, doesn't it? That's what I'm trying to do, which most everyone else in the thread has understood; showing how rediculous using GPL compliance as a forum weapon is
Click to expand...
Click to collapse
On this, there can be little argument.
mtmerrick said:
Actually, not only were they at fault for using illegal software in their ROM, every android user who has a non-GPL compliant kernel is breaking the law - they are in possession of illegally distributed software.
Kinda shows how stupid the XDA rule is, doesn't it? That's what I'm trying to do, which most everyone else in the thread has understood; showing how rediculous using GPL compliance as a forum weapon is
Click to expand...
Click to collapse
Actually no, using examples of how the GPL applies to users in no way shows me how stupid the xda rule is.
NOTE: I have not stated whether or not I agree or disagree with the rule.
This is taking it out of hand. Wonder how many phones here have custom stock roms with out the manufacturers source.....
Sent from my Nexus S 4G using Tapatalk
nevermind. The post in dev is for the A200 kernel.
Just for fun:
GPLv2 3.c) said:
Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
Click to expand...
Click to collapse
I'm no lawyer, but vache doesn't have the sourcecode, so... I'll let everyone come to their own conclusions, as this is a rather technical problem.
In the end, only Acer can fix this problem -- and they probably will once they release the final version of the ROM.
Other than that, the Acer ROM was never supposed to be public, so I doubt Acer can be held accountable for the leak. If anything, vache's source has made himself liable under copyright law.
the self righteous gpl nazis sure are quiet.
Well Vache is not the author of the code. Perhaps you should switch your sites at Acer and ask why there is no kernel source....
Even if Thor was operating in the gpl his website requires a sign in to get his work. Again against XDA rules.
The OP is a complete moron....if he wants to further cripple this community go ahead, seeing as Vache is selling his A500, which will most likely leave us with one less Dev. I suggest we all do since this community is head strong about ruining it for everyone, while trolling other users
Sent from my Nexus S 4G using Tapatalk
This thread brings up an interesting point.
I'm not entirely convinced that the kernel source being unreleased qualifies the Acer ICS ROM as "warez" (I'm fairly confident we'll eventually get the source for the kernel from Acer).
What could potentially be construed as warez are the Acer-specific applications, assuming they're licensed/paid for by Acer for inclusion in their ROM.
Back in the day, Motorola send out C&Ds to sites hosting a leaked 2.2 ROM for DX because it included Swype (IIRC).
In any case, it's a good point to consider.
HTC has been releasing new kernel bases and have not bothered to release source. According to the GPL this is unacceptable. This is not only important to developers but to we the users as well. I know a lot of you love to use custom kernels and they have improved all of our phones. Let's band together send them an e-mail and remind them that the source should be released with new kernels. Letting them get away with this will only reward this type of behaviour.
http://www.htc.com/www/contact/email/ here is the link to the e-mail even if only a little bit of people send it it still says something thank you and lets make it happen!
Sent from my HTC One using xda premium
Sent from my Black HTC ONE
Response -
Sent from my Black HTC ONE
Technically, 4.2.2 is a leak, so until it's officially released, then they don't have to do anything, am I right?
Sent from my HTC One using xda premium
cdordon said:
Technically, 4.2.2 is a leak, so until it's officially released, then they don't have to do anything, am I right?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Correct but there has been like two base updates and still no kernel source so a little push wont hurt
Sent from my HTC One using xda premium
cdordon said:
Technically, 4.2.2 is a leak, so until it's officially released, then they don't have to do anything, am I right?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
Absolutely.
That response email just shows how ignorant of GPL HTC is. They have to supply source to anyone who submits a request in writing if I'm not mistaken.
Where did u see that rule?
Op is just a busybody who doesnt even know what to do with the source but screams for it lol.
This is what happens, when u fed too much they become too dependent on u. A tad bit late and they will start screaming.
Kinda reminds me of the horde.
Remember when the one first came out, then the source follows in a week? Thats called feeding too much.
When the horde realized that the source for 2.17 is slow, they start screaming.
Sent from my HTC One X using Tapatalk 2
I think the sources will be released when 4.2.2 is official carried out. The 4.1 sources were avaiable really quickly so I'm looking forward
HTC has gotten better than they used to be. If the op is looking for 2.17 source then lol.
---------- Post added at 07:11 AM ---------- Previous post was at 07:09 AM ----------
gunnyman said:
That response email just shows how ignorant of GPL HTC is. They have to supply source to anyone who submits a request in writing if I'm not mistaken.
Click to expand...
Click to collapse
I just spent a little while reading the gpl and I'm wrong. Htcdev is complying properly.
As already stated, they haven't "released" 4.2.2 yet, so they are not required to release the source.
We see this every time they release an update. People start crying for the source. Give them time...it WILL appear, just not always straight away.
There's no such thing as propriety in the the current HTC One's linux kernel. All the codes in there are GPL licensed.
The camera fix + the back button sensitivity fix are all in a GPL licensed driver. And I quote.
The GPL states that anyone who modifies GPL licenced code is required to make available the sources used to compile it. This is to further improve and encourage collaborative work, as well as to ensure that the best code possible is produced, and to encourage peer-review of all work. This benefits both developers and end users in numerous ways, including:
Allowing anyone to verify the code they are trusting with their data, and its authenticity
Encouraging community collaboration to produce faster fixes and updates, and better code
Helping bring new developments from other devices and fields to your own, letting you benefit from new code that wouldn’t have been available without this sharing.
The GPL imparts great freedom for GPL end users. It ensures innovation is never stifled and no project is dependent upon any single developer.
Click to expand...
Click to collapse
alphamale99 said:
Response -
Sent from my Black HTC ONE
Click to expand...
Click to collapse
cdordon said:
Technically, 4.2.2 is a leak, so until it's officially released, then they don't have to do anything, am I right?
Sent from my HTC One using xda premium
Click to expand...
Click to collapse
4.2.2 is leaked but 1.29.***.12, 1.29.***.13, 1.29.***.16, 1.29.***.16R are official releases with new kernel revisions and they should be obligued to release what they have modified on those revisions.
shiningarmor said:
Where did u see that rule?
Op is just a busybody who doesnt even know what to do with the source but screams for it lol.
This is what happens, when u fed too much they become too dependent on u. A tad bit late and they will start screaming.
Kinda reminds me of the horde.
Remember when the one first came out, then the source follows in a week? Thats called feeding too much.
When the horde realized that the source for 2.17 is slow, they start screaming.
Sent from my HTC One X using Tapatalk 2
Click to expand...
Click to collapse
Read GPL for the rules. The OP might not have direct benefit over this but we developers have and end users in return benefit from us.
Is there a specific time limit mentioned in the GPL? I don't think they are obliged to provide it on the spot as soon as someone requests it.
the_scotsman said:
Is there a specific time limit mentioned in the GPL? I don't think they are obliged to provide it on the spot as soon as someone requests it.
Click to expand...
Click to collapse
@the_scotsman
There is no specific time limit in the GPL license as you are suppose to be obligued to release the source code as soon as the binary is distributed to the public.
Link is here. http://www.gnu.org/licenses/gpl-2.0.html
Refer to #3
3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,
c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you received the program in object code or executable form with such an offer, in accord with Subsection b above.)
Click to expand...
Click to collapse
Letter A should be the one applicable to HTC's kernel license. As
B - If you're selling the software
C - If the licensor limits the license.
Thanks for that. My next point is then, if HTC are violating GPL so badly as people seem to ALWAYS be claiming, why haven't they been contacted about it? The fact they haven't is good enough for me not to stress over it.
the_scotsman said:
Thanks for that. My next point is then, if HTC are violating GPL so badly as people seem to ALWAYS be claiming, why haven't they been contacted about it? The fact they haven't is good enough for me not to stress over it.
Click to expand...
Click to collapse
@the_scotsman
They already have been contacted for numerous times. But once they receive a valid complaint they then comply to it and release the source code so the claimant then decides to discontinue the case.
Although if we really enforce this strictly when one company violates GPL he then get's blacklisted and is not allowed anymore to use any GPL licensed source code unless the company makes an appeal and no GPL licensor would oppose to the appeal.
Here's a good example
http://lists.gpl-violations.org/pipermail/legal/2011-February/002645.html
even an official from google took action in there.
There's no time limit specified... I guess the spirit is at the same time as the binaries. I doubt this has been tested in court. Usually it's settled, or they're forced to release after the fact. The timing is unlikely to have been tested, but I'd love to be informed otherwise.
Done.
Sent from my HTC One using xda app-developers app