★ ★ ★ [Announcement] Read 1st! Original Android Development Section Rules ★ ★ ★
Hello everyone.
This message is directed to all ROM/kernel developers of Ace community.
There are some rules, which you have to follow before starting new thread.
Rule No.1 - If you are about to post a new Kernel you need to be in compliance to GPL2 since kernel does contain Linux code, this mean that if you have modified a kernel you MUST provide source code:
(choose what best for you)
- A github link
- packing your kernel and uploading
- a diff .patch files
- Credits to people in case of an already custom kernel
- Sources must be posted in first post of development.
Rule No.2 - If you are about to post a new Rom, you don't have to post source since they are covered by Apache, BUT you must be in compliance with XDA rule and with good sense. Remember that publishing sources is a very polite manner.
New Roms thread must contain:
- Exactly say which base rom do you used : Stock, custom from another developer, CyanogenMod.
- Permission to use said ROM as your base by the original developer(s).
- Credits given to original developer(s) in your first post: (eg: Credits and thanks for this Rom goes to XXXXX)
- Credits given, if possible, to the people from whom you grabbed scripts, themes and apps.
- Your ROM MUST BE free of paid apps, NO WAREZ ALLOWED.
- Your first post must contain as much info as you can provide, "this is my ROM" and a link is not tolerated (screens, installation procedure, CM version, kernel version etc.)
- Thread Title : " [ROM]xxxxxxxxxxx[date of release][kernel version/kernel required]
Rule No.3 - AdFly, or other ad-revenue related redirecting links, are NOT allowed. Thread will be closed and links be deleted.
In case of questions please drop me a PM.
Best regards
Tomek
Forum Moderator
Official XDA GPL statement:
pulser_g2 said:
The GPL is a software license agreement, under which parts of the Android operating system are licensed. The majority of Android is licensed under the Apache license, but the Linux Kernel (which is present in every running Android ROM in some shape or form) is licensed under the GPL (version 2).
Many of the amazing developers at XDA create custom kernels, which feature many improvements and changes over the “stock” kernels released by OEMs, including performance and stability tweaks. This is exactly what the GPL is designed to protect, by ensuring that anyone can get access to the original source code used to build the kernel. Given a suitably configured computer, it should be possible for anyone to reproduce a released kernel using the provided source code.
Recently it has come to our attention that a number of users have been neglecting to follow XDA’s GPL regulations, which amount to posting the sources for any kernel you build from source to share with others.
As a result, we would like to clarify our position on the GPL, and users’ obligations to this effect. By posting your work on XDA-Developers, you are agreeing that it complies with relevant licensing conditions. As such, by posting a kernel or other work containing GPL code, you are confirming to us that you have made this source code available publicly under the GPL, and should highlight this in your thread with a link. (Plenty of respected and trusted sites will host the code for you free of charge, such as GitHub and BitBucket.)
By posting open sourced work on XDA, you are also ensuring that your available sources are up-to-date with the work you have released. This means that if you update your kernel to add a new feature, for example, your sources should be updated to include this change. If they are not, this means you are not complying with the GPL.
There is no provision in the GPL to withhold access to sources based on time or other conditions, so please don’t attempt this, as it will only earn yourself a formal GPL request. If you do not provide the correct, accurate, and up-to-date sources (and keep them up-to-date), you will be non-compliant with the GPL.
In order to be fully GPL compliant, your sources must:
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)
The GPL is a legally enforceable license agreement, and while it offers users freedoms to copy and redistribute code, that permission is conditional upon all changes which are released being made publicly available. If you require further advice on this matter, we suggest you review the license itself or consult a lawyer.
Click to expand...
Click to collapse
Related
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
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)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
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)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
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)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
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)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator
GNU General Public License, version 2
Kernel Developers
In order to be fully GPL compliant, your sources must:
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)
Click to expand...
Click to collapse
ROM Developers
If your ROM uses custom boot.img the source must be provided.
If the kernel you are using was created by someone else, you must link to their source.
If your ROM contains a stock kernel, source must still be linked - ie; link to htc-dev kernel page.
Using a non GPL compliant kernel makes your ROM non compliant and subject to removal.
Click to expand...
Click to collapse
Here is an example of how your kernel sources should appear in your development thread's OP (original post):
My Awesome Kernel
Source: [LINK] - Linked directly to where your source is located, ie; github, bitbucket, htc-dev.
Compiler: Linaro GCC 4.8 [LINK] - Link not nessacery but is helpul.
Branch: Android 4.2.2
Kernel Version: 3.10
defconfig: vigor
Click to expand...
Click to collapse
Violating the GNU General Public License, version 2 is breaking the law. We will not go lightly on violators.
Want to learn more about XDA and the GPLv2 License? Check out the news article by our very own, pulser_g2:
XDA-Developers and the GPL
Thank you for your attention.
wildstang83
Forum Moderator