Just a reminder of some old rules that seem to be forgotten. We are not out to make the dev's lives harder or to be a pain in the neck. XDA has had issues in the past from kanging to malicious code in kernel's. They are based on the GPL and you are free to modify and distribute, however you must share your changes and cannot charge for your work. (my summary of the GPL). That's why when we distribute a kernel in a rom, we fall under the GPL guidelines and have to follow some simple rules to keep XDA and our members out of trouble. Thanks again to all the Dev's for your understanding and outstanding contributions.
Anyone providing a ROM with a Kernel include should mention and link what kernel is used.
This means either:
Stock kernel is used (OP has to say that)
OP uses a 3rd party kernel (from another user), then he has say that and link to the thread)
OP uses his own kernel in which case he has to upload sources as per GPL and XDA rules and link them. (Please note: sometimes only the ram disk of a stock kernel is modified, this does NOT fall under the GPL. Example: Making a stock kernel 'insecure')
Concerning GAPPS: CM and some other were asked by google to NOT include them. But only those parties. Everyone else can include them unless asked by the owner (ie Google) to remove them.
This also means in theory that everyone with a CM kang can include GAPPS, however most people don't (which is obviously fine too)
I don't think any OEM ROM was ever forced to remove GAPPS.
Noellenchris
XDA Forum MOD
Related
Welcome to the Original Development for the Evo
4g
Explanation
This section is for original works of art. It is meant to make developers strive for something better and to push the envelope. Our hopes are that developers will work even hard to get their work in here and even harder to keep it in here. All roms in here are actively being updated and maintained.
This section is for a number of things
1. Source build of original roms- Meaning a build that is made original built from source and maintained by creator
2. Maintainers- Roms that were created by an original developer but they have moved on and another developer has taken over as the maintainer (with permission from the originator)
3. Significant ports- Port of roms that are a huge significant development (one port only)
4. Kernels- Original kernels with open source made public on github and 100% gpl compliant. Source is up to date with current version
5. Mods- Original mods made. No ports at all
Make Sure
1. OP is clean and clear
2 Kernel source is gpl compliant and linked to either the orignators OP(where source link can be found) or to the github of their source
3. All build information is stated. (kernel, build type, credits(with links), changelog, whats broken, and screen shots)
What does not go in here?
1. Roms that are copy/paste, kitchen created, themed copy of other roms.
2. Ports not deemed significant or that have already been ported by someone else first
3. Guides
If you think your rom from development section deserves to be in here then PM a forum moderator and request that it be moved. The forum moderators in the evo section with make a group decision and move it if agreed upon. This makes it fair for all.
Things that must be in PM to get consideration
1. Link to the OP
2. What qualifies your rom
3. You are the owner of said thread
Please do not!
1. PM the moderators asking that your favorite rom be added
2. Try and have old threads that were once original be added (looking for active development only)
3. Get your feelings hurt if your turned down. No one is against you at all and your work is very much appreciated
4. Accuse the Mod team of playing favorites. We are all here to better our phones and put forward the best of the best and no one will be denied based on personal likes or dislikes of a person, team, or rom. It is all based on the criteria set above and thats it.
There are no exceptions of the above guidelines.
5. Post a thread in here without the Moderators approval. It will be deleted no questions asked. I'd hate to see a whole thread get deleted and you have to retype out the OP cause I know how time consuming it is.
The following are most likely “Original Development”:
Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them
Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.
Kernels which are built with beneficial changes that are not simply pulled from other kernels already available. Some element of original work is expected.
Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)
The following are most likely not “Original Development”, and should be posted in the “Android Development” subforum:
Your own “unofficial” stock build of your favourite original, source-built (or otherwise) ROM, particularly where an official or maintainer-endorsed thread exists already.
Minor derivatives of other ROMs with little or no changes, or ROMs consisting of “placebo” features as a main constituent or claim.
Renames or rebadges of others’ work – these don’t belong on XDA at all! Refer to rule 12 for more information.
Reposts of existing ROMs with small changes (i.e. kitchen work, such as adding a couple of apps). If you could realistically distribute your changes as an “addon pack” above and beyond a ROM, you should do so. In addition, your “ROM” would not be original development as it would be substantially identical to the original ROM.
A thread created with unrealistic goals that are clearly unachievable by those starting the thread. This is not intended to discourage high aspirations, rather to prevent threads porting Windows Phone 8 to the HTC Wallaby. This is pretty much common sense.
A ROM where a main or significant claim/feature is graphical changes to the user interface (ie. Themed ROM)
Click to expand...
Click to collapse
ALSO ALWAYS REMEMBER THE GPL LICENCE:
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
To put it short,
Rule No.1 - If you are about to post a new Kernel you need to be in compliance to GPL 2.0 since kernel does contain Linux code, this mean that if you have modified a kernel you MUST provide source code:
(choose what is 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 rules 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: (Ex: 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.
Click to expand...
Click to collapse
Reference taken from Micromax A110 forum
Here is what is likely to be posted here and whats not
The following are most likely “Original Development”:
Official releases of highly original and upstream custom ROMs (built from the ground up with significant original development within them
Official releases/development of such original ROMs, perhaps posted by the maintainer or their nominated person.
A significant “first” in development for a device. Significant is subjective, but it is likely something which took considerable time/effort, and is generally accepted by developers to be significant and non-trivial.
Kernels which are built with beneficial changes that are not simply pulled from other kernels already available. Some element of original work is expected.
Tools and utilities with a clear purpose, and which are well-made, and useful to users. They should have an element of originality, either in purpose or through significant improvement in the means of operation.
Significant port of a ROM from one device to another, giving enhanced features or functionality to users of the target device. The port should be beneficial (a port from two virtually identical devices isn’t original development, it’s winzipping, and nobody really benefits from this, as it’s not development)
The following are most likely not “Original Development”, and should be posted in the “Android Development” subforum:
Your own “unofficial” stock build of your favourite original, source-built (or otherwise) ROM, particularly where an official or maintainer-endorsed thread exists already.
Minor derivatives of other ROMs with little or no changes, or ROMs consisting of “placebo” features as a main constituent or claim.
Renames or rebadges of others’ work – these don’t belong on XDA at all! Refer to rule 12 for more information.
Reposts of existing ROMs with small changes (i.e. kitchen work, such as adding a couple of apps). If you could realistically distribute your changes as an “addon pack” above and beyond a ROM, you should do so. In addition, your “ROM” would not be original development as it would be substantially identical to the original ROM.
A thread created with unrealistic goals that are clearly unachievable by those starting the thread. This is not intended to discourage high aspirations, rather to prevent threads porting Windows Phone 8 to the HTC Wallaby. This is pretty much common sense.
A ROM where a main or significant claim/feature is graphical changes to the user interface (ie. Themed ROM)
ALSO ALWAYS REMEMBER THE GPL LICENCE:
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)
To put it short,
Rule No.1 - If you are about to post a new Kernel you need to be in compliance to GPL 2.0 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.
---------
Referenced from: My own thread
@justmpm Here's another thread I'd like stuck - If appropriate.
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
laufersteppenwolf said:
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:
@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:
If you need/want further information, you might want to take a look at THIS news article written by our Developer Admin pulser_g2
Click to expand...
Click to collapse