It’s rather unfortunate, but we’ve all seen those overly cluttered “development” threads that end up more full of low level questions and user support than actual development work. In order to best combat this, various members of the Recognized Contributor and Recognized Developer groups have worked together to come up with a better way of doing things. Rather than housing support requests and actual development talk in the same thread, it quickly became apparent that large projects need two separate areas for discussion: one for development questions such as bug reports and development-related topics, and the other for tech support questions such as whether a particular kernel works on a particular ROM or battery life.
In order to help developers and designated helpers best field the inevitable flood of user support questions, a dedicated Q&A/Troubleshooting thread should be created for ROMs, Kernels, and other projects. This initiative is the fruition of hard work by XDA Recognized Contributors Kuzibri, Robbie P, bigdaddy619, and Riro Zizo, as well as Forum Moderators TonyStark, soupmagnet, Stryke_the_Orc, and KidCarter93, and Forum Admin MikeChannon.
Not quite convinced? Listen to iSock for a few minutes:
OK, so we’ve already established that having a dedicated thread makes development more efficient by keeping the actual development thread clean. And since the thread is linked from the project’s DevDB entry, integration is seamless. But how do we partake in the new system? Thankfully there is an introduction thread that has a brief overview of the new system, guidelines, and a template and some example threads to follow.
To get the full scoop, head over to the instruction thread. From there, make sure to read the guidelines, follow the template, and view a few example threads. Help keep development smooth and steady by keeping the development threads clean._________
Want something on the XDA Portal? Send us a tip! -- Join us for xda:devcon 2014!