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)
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 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.
Click to expand...
Click to collapse
-----------
Referenced from:
Samsung Galaxy Ace Section
Related
☞[WARNING: READ ME 1st] If YOU DID NOT CREATE "it" THEN IT DOESN'T BELONG IN HERE
NOTICE: If You did not create the ROM, KERNEL, FIX, MOD, APP, HACK, GUIDE, or if it's not a SOURCE CODE then it should go to Nexus 4 General as it doesn't belong in Development.
If your thread can be phrased as a question, it DEFINITELY doesn't belong in Development either, post in in the Nexus Q & A sectionhttp://forum.xda-developers.com/forumdisplay.php?f=1909. If you post it in Development it will be moved/closed and you may get an infraction or a ban.
There is only 1 exception, stock ROMs are allowed, as long as the link does not require a registration to download the ROM.
You may start planning a [DEV] topic in the General or Q & A section and then have it moved to the Android Development section once the actual Development has started.
☞ Development is classified as original work and/or documented edits and changes made to others work (with their permission) that makes it your own.
Stock ROM dumps that are modified (deodexed, etc.) from the manufacturer's original intent and then repackaged together classifies as development.
Kernel's and Recovery obviously classify as development as they are modified and compiled from source
☞ Themes are graphical/visual changes made to a ROM which make's the ROM visually different from the original work, i.e. different battery icons, a blue-color scheme, etc. They may be packaged up together with a full ROM and deployed the same way. Simply running a script (not made by you) to deodex and then packaging other people's work/MOD's into one place does not constitute original development.
Follow the FORUM RULES and the XDA MANTRA and we'll all get along and enjoy this community!
Thank you for your cooperation & thanks to jerdog for writing this wonderful explanation.
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 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
☞[WARNING: READ ME 1st] If YOU DID NOT CREATE "it" THEN IT DOESN'T BELONG IN HERE
NOTICE: If You did not create the ROM, KERNEL, FIX, MOD, APP, HACK, GUIDE, or if it's not a SOURCE CODE then it should go to Galaxy Tab General as it doesn't belong in Development.
If your thread can be phrased as a question, it DEFINITELY doesn't belong in Development either, post in in the Nexus Q & A section. If you post it in Development it will be moved/closed and you may get an infraction or a ban.
There is only 1 exception, stock ROMs are allowed, as long as the link does not require a registration to download the ROM.
You may start planning a [DEV] topic in the General or Q & A section and then have it moved to the Android Development section once the actual Development has started.
☞ Development is classified as original work and/or documented edits and changes made to others work (with their permission) that makes it your own.
Stock ROM dumps that are modified (deodexed, etc.) from the manufacturer's original intent and then repackaged together classifies as development.
Kernel's and Recovery obviously classify as development as they are modified and compiled from source
☞ Themes are graphical/visual changes made to a ROM which make's the ROM visually different from the original work, i.e. different battery icons, a blue-color scheme, etc. They may be packaged up together with a full ROM and deployed the same way. Simply running a script (not made by you) to deodex and then packaging other people's work/MOD's into one place does not constitute original development.
Follow the FORUM RULES and the XDA MANTRA and we'll all get along and enjoy this community!
Thank you for your cooperation & thanks to jerdog for writing this wonderful explanation.