Dear kernel and ROM developers.
According to GPL v2 license, under which kernels are released, kernels must be released with source code provided.
To be fully compliant, the thread must contain in the OP:
@ kernel devs
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released
Example.
Kick-ass kernel
Built with android-toolchain 4.8 4.8-2013.05 (linking isn't a bad idea)
Branch used to compile (can be a direct link to git)
Name of the defconfig used in build
A short instruction about how to build it (not necessary, but useful)
Click to expand...
Click to collapse
@ ROM devs
If ROM uses custom boot.img, the source must be uploaded by you.
If it uses kernel by someone else, the kernel thread (and source link provided in main thread) must be linked in the OP.
If the ROM contains stock kernel, it must be mentioned. Source isn't required.
If you can not do any of the above, release your rom without a boot.img in the flashable zip.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal
Violation of GPL is in fact a breaking of the law, so I don't have to explain what could be a final of this.
More information can be found in the news written by pulser_g2.
Thank you for your attention.
Tom
XDA Senior Moderator
With recent site wide concerns about GPL Compliance, or lack thereof, I've copied this here to help remind everyone about the importance of posting the matching source code for your kernels.
I'll leave this open for awhile in case anyone has questions about it.
thanks for a update
will help the developers as well as end-users
Related
Dear kernel and ROM developers.
According to GPL v2 license, under which kernels are released, kernels must be released with source code provided.
To be fully compliant, the thread must contain.
@ kernel devs
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released
Example.
Kick-ass kernel
Built with android-toolchain 4.8 4.8-2013.05 (linking isn't a bad idea)
Branch used to compile (can be a direct link to git)
Name of the defconfig used in build
A short instruction about how to build it (not necessary, but useful)
Click to expand...
Click to collapse
@ ROM devs
if ROM uses custom boot.img, the source must be provided. If it uses kernel by someone else, the kernel thread must be linked in the OP
if the ROM contains stock kernel, source must be linked (official site can be used)
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal
Violation of GPL is in fact a breaking of the law, so I don't have to explain what could be a final of this.
More information can be found in the news written by pulser_g2.
Thank you for your attention.
Tom
XDA Senior Moderator
Dear kernel and ROM developers.
According to GPL v2 license, under which kernels are released, kernels must be released with source code provided.
To be fully compliant, the thread must contain in the OP:
@ kernel devs
Successfully build and produce a valid output file, which is the same format as provided in the binary
Contain all source code, interface definition files, scripts used to control compilation and installation of the executable (it is not required to include the actual compiler/toolchain, but sufficient information should be made available to obtain the SAME configuration, including compiler flags, as used to build the binary version as released
Example.
Kick-ass kernel
Built with android-toolchain 4.8 4.8-2013.05 (linking isn't a bad idea)
Branch used to compile (can be a direct link to git)
Name of the defconfig used in build
A short instruction about how to build it (not necessary, but useful)
Click to expand...
Click to collapse
@ ROM devs
If ROM uses custom boot.img, the source must be uploaded by you.
If it uses kernel by someone else, the kernel thread (and source link provided in main thread) must be linked in the OP.
If the ROM contains stock kernel, it must be mentioned. Source isn't required.
If you can not do any of the above, release your rom without a boot.img in the flashable zip.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal
Violation of GPL is in fact a breaking of the law, so I don't have to explain what could be a final of this.
More information can be found in the news written by pulser_g2.
Thank you for your attention.
Moderator Team - Samsung International
This dev sub-forum is scheduled for GPL cleanup on 8th July, I.e. 7 days from the date of sticky.
I believe that is enough time for everyone to comply with this.
Threads which aren't GPL compliant will be closed down with their download links removed.
Do we need to post the whole code of the kernel?
◄Rahul4Ace► said:
Do we need to post the whole code of the kernel?
Click to expand...
Click to collapse
The whole code which is required to compile a complete, up-to-date kernel in similar build environments.
So, yeah. Whole code, not just modified chunks.
a.cid said:
The whole code which is required to compile a complete, up-to-date kernel in similar build environments.
So, yeah. Whole code, not just modified chunks.
Click to expand...
Click to collapse
Thank You For The Info, Hope The XDAians follow this.
Dear Developers
I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).
You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.
Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:
The used toolchain including its version (linking to your toolchain source is always a good idea)
The used defconfig
The link to your sourcecode (including the used branch, tags,...)
If used, also upload your scripts used for the compilation
If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...
Example:
GPL:
- Used sources (cm-10.1 branch)
- Used defconfig
- Used toolchain
- Used scripts
Click to expand...
Click to collapse
@ROM devs, using a precompiled kernel
As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.
Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.
Example:
GPL:
The kernel included in this ROM is located HERE. I have not altered anything.
Click to expand...
Click to collapse
If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
Dear Developers
I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).
You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.
Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:
The used toolchain including its version (linking to your toolchain source is always a good idea)
The used defconfig
The link to your sourcecode (including the used branch, tags,...)
If used, also upload your scripts used for the compilation
If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...
Example:
GPL:
- Used sources (cm-10.1 branch)
- Used defconfig
- Used toolchain
- Used scripts
Click to expand...
Click to collapse
@ROM devs, using a precompiled kernel
As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.
Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.
Example:
GPL:
The kernel included in this ROM is located HERE. I have not altered anything.
Click to expand...
Click to collapse
If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
Dear Developers
I'm sure you already heard about the GPL around the forums. In case you did not, the GPL ("GNU General Public License") is the most common license that affects many projects, like the Linux Kernel (the Linux Kernel is licensed under the GPLv2). This affects us, XDA and its members, as we are often working with the Linux Kernel (every Android platform runs on top of the Linux Kernel).
You may ask yourself now "Well, that's nice, but how does this affect me and what does the GPL do?" The answer is pretty simple actually: The GPL guarantees users to examine, modify and share their and others code by enforcing open-sourceness. This means you are free to use any GPL'ed sourcecode for your project, but you must make your used code publically available again.
Now, as many advantages this has, it also means quite some work for us developers. All used sources must be completely public by the time the compiled binary (like a Kernel) goes online. Another requirement is, that the OP must include all information to compile the exact same binary as uploaded by the developer. This means you need to specify:
The used toolchain including its version (linking to your toolchain source is always a good idea)
The used defconfig
The link to your sourcecode (including the used branch, tags,...)
If used, also upload your scripts used for the compilation
If you upload a kernel, publish the source, but the source is not compilable, it means you are breaking the GPL as you did not release the used source. Breaking the GPL actually means breaking the law, which means the sanctions on XDA could possibly be the least of your problems...
Example:
GPL:
- Used sources (cm-10.1 branch)
- Used defconfig
- Used toolchain
- Used scripts
Click to expand...
Click to collapse
@ROM devs, using a precompiled kernel
As you are not compiling the kernel yourself, you do not have to give the above information. However, you have to link to the source of your kernel binary (for example: link to the OP of the used kernel). If you use the stock kernel, you must state this. Linking to the stock sources is not a requirement, but it is not the worst idea.
Keep in mind; if the kernel used is not GPL compliant, your ROM is not GPL compliant either. This may cause your thread to be closed and/or further action on your account may be taken.
Example:
GPL:
The kernel included in this ROM is located HERE. I have not altered anything.
Click to expand...
Click to collapse
If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2