Develop Bugs

"Dev" UserGroup

Why not just create a "Developer" forum usergroup for all the Android/Winmo developers who create ROMs/Mods/Themes and use that rank to filter out who is allowed to create new threads in the respective "Dev" forums of each phone? It's maddening to see so many [Q]'s among all the ROM titles and would REALLY clean things up, not to mention push all the other Q/A and help traffic into the forum sections they actually belong in, resulting in greater topic exposure, and by extension, potentially expedited help in dealing with problems.
Have a simple process of a message appearing when a non-dev clicks on the new thread button in the Dev section, and have it say "Sorry, you are not a recognized developer. Android/WinMo developers are the only ones allowed to post here, all questions and other discussion belong in the Q/A forum of this phone (Link here). To apply, simply PM (some moderator), tell that moderator you are a Dev, and you will be able to post.
You're not going to have to ask for proof from Devs who want to post, because since the majority of help threads created in the Dev sections are made by people who simply don't know better, are new, or don't understand the difference between forum sections. There won't really be censorship, because no user who needs help with xyz gps issue is going to go through the trouble of trying to fill out a Dev rank request forum when they suddenly realize they are posting in the wrong forum, and will move to the correct one.
It won't even be difficult to implement, just look through the dev forums and start granting people who are already android/WinMo developers the Developer usergroup. It's not even like they need extra permissions, the only extra permission they'd have is being able to post in their Development and Hacking forum.
Love XDA, Cheers!

+1 to this idea.
It won't be hard to implement, but it will be a constantly time consuming job for the Administrators to monitor the boards to appoint certain users to such a 'Rank'.
Along with this idea... why not a 'Community Assistance' rank for those who don't necessarily develop, but rather help users with issues they may have: answering questions, providing tutorials for help, sharing resources, etc..

[Project] Dev Blogs

Dev Blogs
It's my new webpage project. So far, a link to developer project blog.
Mod Edit: Link Removed
So generally speaking about the project,
it will be a page on which the developers
will be able to create your pages, post news, upload files, etc.
In general, the entire page will be dedicated
to developers of all sorts, not only Android
Want to know more? Write below.
If you would like to join the team welcome Mod Edit: Link Removed
Join to team it's free and earnings later!
PS - In general, we need 200$ to buy server and domain for 1 year.
​

My team wasn't enough?

@up
heh

Thread Closed
Sorry, not allowed per Rule 11.
Thread closed,
mikef
XDA Senior Moderator

[Q] Posting a port

If I post a port on this primoc forum do i have to have permission from the original rom dev? even if the rom may be discontinued and the dev no longer active? Could I still post it and give them credit instead?

Zakman72 said:
If I post a port on this primoc forum do i have to have permission from the original rom dev? even if the rom may be discontinued and the dev no longer active? Could I still post it and give them credit instead?
Click to expand...
Click to collapse
No you HAVE to ask. Unless they have stated otherwise, even if they have stated otherwise you MUST give credit.

In regards to shubham's cm9 kang bang rom. I would send a permissions request and give him fair time to reply. And then if no reply confer with the community about adding it with proper credits to shub for the original rom. I say this due to him no longer being online with the htc one v. If not online at all. I never could get in touch with shub after trying to contact via several methods. I do not think shub would mind as long as you gave him proper credit for his original work. To me its about continuing the community. A number of the older roms would still be very useful if bug problems were finally eliminated. Roms like Kang Bang have a lot of potential..they just need some bugs eliminated. In regard to what is best for the community,I say keeping the community active and viable to draw new development should come before certain permissions if the developer is no longer active in the community,not online at all any where and as long as they are credited for their work. Most developers would not mind seeing their work continue and fixed if possible as long as they are properly credited. Zakman I suggest private messaging the senior members of the htc development community like Simon,Llior and the current major rom developers and see how they feel about it. You might find they as a whole would be ok with it in the absence of shub as long as you did credit shub.

Well said, sir
Sent from my phone running a rom

Curtis1973 said:
In regards to shubham's cm9 kang bang rom. I would send a permissions request and give him fair time to reply. And then if no reply confer with the community about adding it with proper credits to shub for the original rom. I say this due to him no longer being online with the htc one v. If not online at all. I never could get in touch with shub after trying to contact via several methods. I do not think shub would mind as long as you gave him proper credit for his original work. To me its about continuing the community. A number of the older roms would still be very useful if bug problems were finally eliminated. Roms like Kang Bang have a lot of potential..they just need some bugs eliminated. In regard to what is best for the community,I say keeping the community active and viable to draw new development should come before certain permissions if the developer is no longer active in the community,not online at all any where and as long as they are credited for their work. Most developers would not mind seeing their work continue and fixed if possible as long as they are properly credited. Zakman I suggest private messaging the senior members of the htc development community like Simon,Llior and the current major rom developers and see how they feel about it. You might find they as a whole would be ok with it in the absence of shub as long as you did credit shub.
Click to expand...
Click to collapse
Big Thank you sir. Will do.

[INDEX]Betaapps - beta testing community (google+)

Dear XDA members and developers, in case all of your apps need to be tested, and tested correctly, I would like to introduce my google+ beta community here:
Betaapps
As many of you know, Google implemented beta testing options to the Google Play Market and this option based on google+ communities, where you can invite your testers.
These way have a huge advantage:
1) Users can install your beta application directly from Play Market (they can trust your app more, and they don't need to move *.apk files on the device).
2) You will have a simple bugtracker with crash reports, it should increase quality of received feedbacks.
My community should help developers to share their beta programs and invite testers to their communities. If you have a post on XDA forums with your application beta promo, you also can just share the link to our community to the "Request feedback" section with no worry that it will be removed (even if you don't have any community). There are not so much places where you can find a list of beta testing programs, like in our "apps" section, and I also would like to invite all XDA members who want to be notified about new android apps in beta to join our Betaapps community as a tester.
For now, Betaapps community is growing and it will be very helpful if you will share this community with your google+ circles and other social networks. This forum section could be more effective for developers if they will know how to get more testers.
Actually I have a big plans in beta testing field and my community and I hope that XDA members will enjoy my activities and our work will be help testers and developers meet each other. Welcome for your comments.
* for moderators: It would be great to pin this post in this forum section. I also
can place a link to this post in our community description to help people visit XDA. Thanks!

Hey if tester positions are still opened please consider me.. As I'm a real QA Analyst so can easily find and report the bugs n I'll prefer Quality all the way...
Thanks
Sent from my GT-I9070 using XDA Free mobile app

Welcome - Betaapps community is a part of crowd testing. It's mean that everyone can become a tester and of course you can be invited privately for more interesting projects, if your testing skills are good.
There are a lot of free testing programs there and you can join any of them, by the way I will share some information about other beta platforms where you can find paid projects in "crowd" section. Stay tuned and you will become a part of a big crowd testing project with paid opportunities and other awesome features.
You can also introduce yourselves there, and share that community with your friends. We are looking for active QA professionals there :highfive:
Fill free to ask anything you want to know about Betaapps!
sunil.avvas said:
Hey if tester positions are still opened please consider me.. As I'm a real QA Analyst so can easily find and report the bugs n I'll prefer Quality all the way...
Thanks
Sent from my GT-I9070 using XDA Free mobile app
Click to expand...
Click to collapse

Vindceo said:
Welcome - Betaapps community is a part of crowd testing. It's mean that everyone can become a tester and of course you can be invited privately for more interesting projects, if your testing skills are good.
There are a lot of free testing programs there and you can join any of them, by the way I will share some information about other beta platforms where you can find paid projects in "crowd" section. Stay tuned and you will become a part of a big crowd testing project with paid opportunities and other awesome features.
You can also introduce yourselves there, and share that community with your friends. We are looking for active QA professionals there :highfive:
Fill free to ask anything you want to know about Betaapps!
Click to expand...
Click to collapse
I'm In and thanks for the info I've juts Joined & followed the Beta apps from G+

Recognized Developer Code of Conduct & Minimum Requirements.

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
Code:
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.