[About XDA developers] karandpr:
Recognized Developer Code of Conduct​

As an XDA Developers member with special standing as part of our developer program, we obviously have some expectations of your conduct. We try to be friendly here, and while we understand that not everyone is going to get along, we would ask that you try to avoid getting into big arguments in threads. If you have an issue with another forum member, take it up with them politely in a private message. It’s the mature way to deal with things.

As a titled member on XDA, you are a representative of XDA’s ethos – “by developers, for developers.” As such your activity offsite in other public venues should be in the same vein. Any negative, derogatory, abusive talk or actions may be taken into account as to your status as a titled member. This would include any behavior which violates our site rules. This does not change your responsibility to be subject to the requirements for acceptance into the Recognized Developer program, both in their current and future states.

While all users should follow the site rules, we would ask that you take a quick look at them again, as they are occasionally updated. If you have any questions, please don’t hesitate to get in touch with any moderator.

In addition to the rules, we would highlight the importance of acknowledging the work of others. It’s not nice to see your work get ripped off—whether it’s a ROM, part of a ROM, an app, a theme, images, guide text, etc. If you’re familiar with the regulations in academic institutions, you should know the score. Just seek permission and acknowledge those whose work you use, and generally be reasonable about things.

We would also ask that if you have a dispute, you first try to resolve it in a reasonable and private way, such as through private message. It is in no one’s interest to see your dirty laundry aired in public, and it looks much better for you to avoid conflicts on the site.

Senior Recognized Developers of XDA, in additional to the above, are expected to be active on XDA regularly. While we all go away for vacation, exams, and other everyday life events; we would ask that if a Senior Recognized Developer intends to take a significant break from development, he or she stand down temporarily. You’re more than welcome back if and when you return, and we’d love to have you back, if a space becomes available. The reason for requesting this level of activity is because as a Senior Recognized Developer, you will be able to vote on the appointment of other Senior Recognized Developers in the future. If many Senior Developers disappeared, it would be troublesome gathering a sensible turnout. In addition, from time to time we will invite discussions on matters pertaining to the site, and it’s only fair that we try to ensure that the people most familiar with development and XDA have a chance at helping out.

Recognized Developer Minimum Requirements​

To be able to provide some transparency on how the reviews for RD are rated we’ve set up these minimum requirements. Please understand that the RD program is not just a reward for people that try hard on XDA, it is more than that. Accordingly, not just any project meets the standard of development. We will use these minimum requirements with enough room to budge if the circumstances require this, but please use a somewhat critical view of your projects, and only apply if you have at least met these requirements.

Make sure you uphold the RD code of conduct and the regular XDA rules. Should you have infractions on your account, contact the Developer Committee if you want to know if you are eligible to apply. As a general rule of thumb, wait one month per infraction point before applying, and can’t accept members with more than 10 points to their account. Of course, exceptions may be made but contact us if you have a question about this.

All Projects

Members must be actively involved in the community

Team accounts can’t receive the RD title. It’s a program that rewards developers for their individual work and team accounts don’t fit that idea.

A minimum of two full-fledged, markedly different projects are needed to apply for RD, only very special projects are considered otherwise

Any project needs to have at least three months of active development before it will be taken into account for the application

No history of bans and/or serious infractions

Changelogs must be readily available inside the thread, with updated information for each version

Feature lists and changelogs need to be free of blurry expressions like “tweaked ext4 performance” and other meaningless terms. Instead, it should be explained what was done in detail and why it was done

ROM

They started from an official manufacturer or source base (stock ROM or AOSP-like source).

Threads show a clear overview of changes made, in a way that DC can clearly see what has been developed by the user

The ROM isn’t the product of an online kitchen or otherwise derivative development (i.e. themed stock ROM)

ROMs need to identify what kernel they are using

If 100% stock then they must state that

If custom they must provide a link to the kernel on XDA (if available) or a link to the kernel source. To accomplish this there are two options:

Option 1: They provide links to suggested kernels but do not include them in the ROM

Option 2: They include the kernel but must provide a full, buildable source with all GPLv2 requirements met

Apps

Very simple applications may be excluded (very basic UI or functioning)

A free version of the application is available on XDA (no trials)

The developers are either active on XDA or really helpful in their support thread

Kernels

Sources must be posted and downloadable with build comments, toolchain used, and must compile

Sources must be released via forking + commits rather than “lump releases”

Link to the source must include which branch is in use

Guidelines:

In order to make sure the DC is able to find the information we need to make sure your threads hold all the information necessary. Here’s a list of things we like to see.

Threads should include:

Clear introduction

An overview of what the project does (i.e. its purpose) and what is included

2-8 screenshots that are posted alongside each other

A clear changelog in a

or tag, that shows the non-trivial updates to the project

Installation instructions and links to download and github (or like services) for source code, as applicable

Credits with links to the projects that have been built upon, or have been included, in this project

Provide a checksum if you can (md5, sha1 etc.)

The DC set up a template thread that highlights the important parts of a project. Try to follow this template to have an organized and clean thread. You can find the template thread here.