Guides and Rules for Posting in Original Development - LG V10 Original Android Development

Just wanted to clarify what the differences are between android and original development. Here are some KEY points by our very own pulser_g2.
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.
*ROMs where the developer has made a custom kernel for it.
*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 favorite 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)
You can find all the info for it here. Threads will be moved if they do not meet the "Original" development requirements. Thank you guys and have fun!
NOTE: IF YOU ARE UNSURE WHETHER OR NOT YOUR WORK QUALIFIES FOR OD THEN POST IN ANDROID DEVELOPMENT AND CONTACT A MODERATOR TO REVIEW IT. THANKS!

Related

***OFFICIAL*** Samsung Galaxy S Group - Join NOW!!!

http://forum.xda-developers.com/group.php?groupid=287
http://forum.ppcgeeks.com/group.php?groupid=71
Join now if your are currently a user of any of the Samsung Galaxy S devices!!!
Moved this thread from the Samsung Tab forum where it did not belong.
What is the use of these groups?
This is a dupe of http://forum.xda-developers.com/showthread.php?t=774092&page=1
And I'll reiterate my thoughts from the other thread:
1)This thread is misleading. It ISN'T an official group. It's possibly even less official than this forum, and there is no reason to believe Samsung is in the group.
2) I STRONGLY feel it actually is a step backwards, because you must be part of the the group to even read threads. To me this seems to suggest it has a greater interest in boosting numbers than encouraging cooperation, and sharing of information.
3) The assumption being made that you can easily blend all the development streams of the Galaxy S variants together is a wrong assumption. Whilst the phones are similar, until developers get together to merge all the drivers into a single rom (to create a universal rom), each phone does need it's own development board.
In that case consider it Closed
Been away a while, but indeed this can be seen as a violation, the thread adds nothing to the information on XDA and is spammy in it's nature.

Thunderbolt Rules - New Users Guide - GPL - Read Before Posting!

NEW USERS READ BEFORE POSTING!​
Please read this amazing guide below made by ScoobarSTI specifically for new users, it will tell you all you need to know!
New to the thunderbolt? Look here before posting
--------------------------------------------------------------------------------------------------------------------------------
Thinking of posting a new thread?
Search the whole forum using the search button for a relative topic before posting or starting a new thread, Chances are you can find your answer with a simple search. Use the search button on the top bar.
If your thread is merged/deleted/moved or closed its because this is the development section not General/Q&A
Non-Dev related threads will be closed without notice and then moved to the appropriate sub-forum or trash. Repeat offenders will have their post deleted and will receive an infraction and possible ban.
--------------------------------------------------------------------------------------------------------------------------------
This thread is for all the important links and info new and old users may need to get started. I will try and fill this thing with as much info as possible so please read before posting.
_____________________________________________________________________
ATTENTION - PLEASE READ​
Forum Rules ​
HTC Thunderbolt Wiki
Moderator List
ATTN - ALL ANDROID DEVS] General Public License by 12aon​
Official Stance from Swype Inc. Regarding Swype Distribution​
REF | GUIDES
Prerequisite to Rooting - Android SDK Installer - v3.0 for Windows​
WARNING - Do not downgrade to 1.0xxxxx after root​
ROOT - Unlock Bootloader + Permroot​
SCRIPT - Windows One Click Root Method​
Easyroot + S-Off​Getting root on the HTC Thunderbolt from absolute start to finish - Mac OS X
Return to stock properly and safely​
ATTN - ALL ANDROID DEVS General Public License
Originally posted by 12aon
http://forum.xda-developers.com/member.php?u=900967
A little introduction
Recently in several Android fora on XDA-Developers, it has come to the attention of the moderator team that there have been issues regarding developers’ compliance with the GPL. This post aims to clarify the position of XDA on the use of GPL sources, particularly in the development of Android kernels.
Without the GPL, the Android operating system would likely never have come about. Through the work of Linus Torvalds, the Linux kernel was made open source for all to use, share and modify. As Android runs on the Linux kernel, and features numerous modifications to these sources, it would not exist in its present state without the Open Source community.
As a result, it is in the interests of everyone who owns an Android phone, who wishes to see further development on the platform, to ensure that they play their part in upholding both the letter and spirit of the GPL.
The GNU General Public Licence (also known as the GPL) is available to read in full at www.gnu.org
To make it easy for everyone to spot a release that complies with the GPL mark the title of your release thread with [GPL]. If you find a ROM which does not comply with the GPL, or the developer does not issue sources, you can report the post as usual, using the report post button next to the post number. Alternatively you may PM your forum specific moderator.
The Rules as they apply on XDA
As XDA has no legal power to uphold the GPL (and frankly we want to stay as far away from doing so as possible), we can’t force any of our users to abide by the GPL. However it is in XDA’s interests as well as the interests of our developer-base to ensure all GPL-derived materials hosted or linked on XDA comply fully with the GPL.
GPL-derived materials that do not come with the complete sources used to compile the GPL components are considered warez, and will be treated as such under forum rule 6 and 9.
If you use GPL components, but do not make any modifications to them whatsoever, you should provide a link to the original source of your GPL code.
Sources accompanying a release should be complete, and contain all the necessary source code for any modules, scripts or definition files. Complete sources will be defined as those which compile correctly and completely against the platform for which the software is distributed, and which contain any and all modifications made to the released General Public Licenced code. The source code supplied should be the exact version for which the source code is being requested, complete with all modifications.
EXAMPLE: Here’s a bit of code that could be used as a template to post your releases
<Kernel Or Author Name> <Kernel Nr>:
<Source>|<ReadMe>|<Credits>|<Other>​The Very Quick Summary of General Public License (GPL)
The text of the GPL Licence itself will be used to reach any final conclusion regarding any disputes over GPL Licenced materials. The above is a summary of what XDA expects of members using GPL code, and the complete text can be read at the GNU website.
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.
It is in everyone’s interest for the GPL to be adhered to, as it gives us all better ROMs, better transparency, and a better atmosphere for developers to work together to make great code.

[Q] original development vs development

Can someone explain what the difference between the two development sections are?
I believe it means what it says. Original meaning by developer/development team and only them. The other forum is for different variations of existing roms/kernels etc. Like taking a piece of this and that and giving credit to original developers. Something along these lines.

[Request] Dedicated section for Umeox x201 (AW-414/420, TrueSmart, etc...)

Really didn't want to do this but EVERYBODY that posted here, post in the Official *** New Device Forum Requests *** thread.
This may be the only way we are going to make this happen.​
Would like to publicly request a dedicated section for the Umeox x201. This covers such devices like the the AW-414, AW-420, Vapirius AX-3, Omate TrueSmart ans at least three other devices based on the x201 platform.
Current issues with not having a dedicated forum are;
Informational master thread keeps getting buried
Cannot add development releases to the Dev DB
Development projects are not being posted due to lack of a development section
The current Omate TrueSmart main thread is now over 100 pages long and includes development, Q&A, general discussions and is near unmanageable
There is a lot of cross posting of the same information on the AW414 and TrueSmart threads because, except for case and name, they are the same device.
wondermike8 said:
A section for this class of smartwatch would greatly help things. It would make it easier to find information because we could have single-topic threads. It would be easier to contribute because catching up with a thread would be quicker. It would allow the community to grow and operate.
But of course it would be useful to US. Every obscure device community could ask for a section and argue that it would help them. We need to argue that our device is so popular that a section is required. Here are some points to consider:
* Within the "Other Smartwatches" section, the "Omate Truesmart" thread has about 40% of the posts of the "MotoActv" thread. However, the MotoActiv has been around since 2011 and the Truesmart has been around since - well, for all intents and purposes, it isn't even out yet and there's still a thriving community
* There are more posts in the "Omate Truesmart" thread than in the entire "Pebble Smartwatch" section. Don't get me wrong, there's a huge and dedicated Pebble community out there. Here on the XDA forums, however, the Umeox x201 community is larger, more active, and in need of a good home
* A dedicated section will improve the quality of the site. Having monster threads like the "Omate Truesmart" thread make the site disorganized and difficult to use. If the information is easy to find, the users are better informed. Well-informed users make a better community. Better communities bring in more advertisment dollars.
* The time to act is NOW. The early devices are beginning to ship, and the there are only a few developers churning away. Over the next month or two, the number of devlopers will explode. Implementing a new section now will allow time for proper organization. Allowing a thread to balloon to 10,000 posts and we'll need to hire more mods to help sort the information into proper threads.
Does it make sense? Is it worth it? My professional experience in forum management (of which I have none) says yes!
Click to expand...
Click to collapse
Note to Admins:
We currently have info, fixes, development environment guides and so on spread out across multiple G+ communities and posts, two forums and personal pages and are already running into issues where even searching doesn't even find some it. If you decide to not create a section for the x201 please let us know as we will need to find some sort of solution.
agreed
You have my support. Now let's flood the official request thread
Tapatalked from my HTC Droid DNA
Lokifish Marz said:
Would like to publicly request a dedicated section for the Umeox x201. This covers such devices like the the AW-414, AW-420, Vapirius AX-3, Omate TrueSmart ans at least three other devices based on the x201 platform.
Current issues with not having a dedicated forum are;
Informational master thread keeps getting buried
Cannot add development releases to the Dev DB
Development projects are not being posted due to lack of a development section
The current Omate TrueSmart main thread is now over 100 pages long and includes development, Q&A, general discussions and is near unmanageable
There is a lot of cross posting of the same information on the AW414 and TrueSmart threads because, except for case and name, they are the same device.
Click to expand...
Click to collapse
Agreed.
i support this too.
attapKia said:
i support this too.
Click to expand...
Click to collapse
Couldn't agree more.
Would be grateful for a dedicated section as well.
I agree. We need a section for the best SmartWatches so far.
Aye, Loki, you have my axe!
(in other words, I support a dedicated forum)
Support!
One more here to agree !!
Omate might kill me for this since I'm one of their forum moderators and an admin, but I think a development forum on XDA is a much better thing then a "special development forum"...
Reason 1:
There are too much wise noses on the TS forums who think they know it all, but over here at XDA I mostly see professionals or at least people working together more professionally...
Reason 2:
There has never been an Asus Padfone series forum over here at XDA (even though a lot of people requested it), and there has been a lot of development for this device over at my Padfone community, but I know there would be a lot more development if the Padfone would've gotten it's own forum over here a XDA... So to make the TS (or any other Umeox watch since they're pretty much all the same, except for the exterior) a great success, proper development is required!
So +1
Agree
And as an avid reader of this forum and member since 2007 (when xda-dev was for xda's only), I support this request.
support this.....
I support this.
Agree.
+1
Sent from my Nexus 5 using xda app-developers app
Yes, please. :good:
+1

How to Apply to become Recognized Contributor /Themer on XDA

Just stop around & have a look to this thread. A thread for the devs & themers who contribute a lot to the forum, & can become a Recognized Contributor/ Themer because they are worth the title, as they work so hard to bring the users with something new to xperience & that too free of cost.
Special Thanks to the XDA Member @Zatta for his thread to explain the process to become a Recognized Contributor/ Themer as stated below.
So over on the Recognized Contributors forum, it has become clear that most members of XDA don't know that you can apply for the title of Recognized Contributor (RC). I have also included the same for Recognized themer, as I am assuming that it's not well known that you can apply.
What is a Recognized Contributor?
Recognized Contributor is a role intended for members who produce some of the best original and helpful guides for users, as well as helping other users who have problems, in a friendly manner. Recognized Contributors will get a custom user title and the faster ad-free XDA template, as well as access to developer tools currently being created. Any Senior Moderator on XDA can add Recognized Contributors, should you feel deserving of this title.​What is a Recognized Themer?
Recognized Themers are those users who work (often tirelessly) on designing new theme graphics and user interface overhauls for ROMs. Users who aspire to be Recognized Themers should be creating original graphics work for their themes being released, demonstrate a commitment to crediting other users’ work when applicable, and seek the relevant permission in advance from the original creator. Recognized Themers will receive a custom user title and the faster ad-free XDA template, as well as access to developer tools currently being created. Any Senior Moderator on XDA can add Recognized Themers, should you feel deserving of this title.​Pre-requisites
1. Been a member for at least 1 year (willingly following the XDA rules) with consistent and acceptable activity in the last 3 months.
2. Posted good original threads:
a. Threads that are guides/ index / collective information.
b. OP of ROM threads and have a good support within the ROM thread or via a separate thread in the Q&A section, and some activity in Q&A section or other threads besides their own.
c. Place holder threads (discussions of home screens/ wall papers / Off Topic, etc) are NOT accepted.
Exception: A proper place holder for a new phone with details and other important information and further maintaining the Q&A on the device.
3. In case of no independent threads, the following may be accepted:
a. An FAQ (or support post) within a ROM thread.
b. Generally moving around from thread to thread to help members – the "Post Count Vs Thanks" could be used as a means to measure to this.
4. Good quality general know-how around XDA forums (not necessarily developer standard)
5. Thanks count broadly expected given the forums they are in.
6. Posted regularly enough (complementing point 1) to provide continuous support or less frequently but good high value support
7. Contribute to a good over-all general atmosphere.
8.You have read, understood and already adhere to the Recognized Contributor Code of Conduct.
How can I apply?
You can apply by sending your application via PM to:
A member of the RC-RT Committee:
ApriliaM3, KennyG123, Mr. Clown, PG101, Judge Joseph Dredd, Woody.
Any other Senior Moderator
Any FSM.
Any existing RC, who will pass on your application forward.
Choose whichever route you are more comfortable with, the end result is the same. All list of moderators can be found here.
Best way in which to apply through your PM
When you are writing your application, you will need to include:
A polite hello
Your username with a link to your username, they will want to check your history.
Why you think you would make a good RC/RT, including a little about your time on XDA.
Links to your work including Guides, Ref, Roms, Projects, Apps(Themes for RT) etc
Do not forget to include 7/10 links of threads/posts which would be helpful in assessing your application.
A thank you for their time and good bye (Manners are free)
Please note only apply once to one committee members, do not send 3 applications to 3 different committee members. Also be patient, the committee members are very busy people and have other work on XDA and in personal life. I would recommend a waiting time of upto a week; and if you receive no response within a week, then a reminder PM.
Please do not bombard the committee with PM's.
If you are having a problem with your application or you would like to appeal a decision made on your application, then you can contact the RC-RT Committee through PM.
If you do get accepted as a RC/RT then please come and visit the RC's forum and help contribute to our work and cause to make XDA a better place
If you have any questions then please ask, myself or the other RC's/RT's will help in anyway we can.
WHAT THIS THREAD IS NOT: A PLACE FOR PRE-ASSESSMENTS.
Press Thanks :thumbup: If I Helped

Categories

Resources