Related
With so many roms and software being developed and so many questions being asked over and over again, it occured to me that there is not (correct me if i am wrong) a public bug tracker for XDA.
Ideally integration with the user database and even possibly the threads (more than just a url link) would be great.
If we had a way of tracking and submitting bugs then i think each dev or cook could better manage the bugs in thier software and i think it will help reduce the duplicate requests and bug reports going on in each thread.
The bug tracker could split between software types, platform, then also have device sections with each rom under that, much like XDA is structured at the moment, in fact probably identical to reduce the confusion and help with the linking and integration.
What bug trackers could possibly be used that would integrate with XDA? Bugzilla?
I am more than willing to setup an instance for testing etc, who would be keen to see and help with this? Integration will be the biggest task.
Interesting Idea, I guess that would have to involve developer consent that they want their work to be tracked. Having people discuss in threads isnt bad as that is what the forum is for but a tracker type online utility may be good for huge projects which would cut down on posts saying "Hey whats the status of Bug X and Y?"
Good idea
I used my own tracker for a while, but for xda we would have the issue of how to assign users to what role.
Every time I made a rom, I would need to request a new category and get ten pepper added as project authors ...
Trouble with the tracker that I found was that it just got messed up like the forums. Trust me that nobody searched it.
I reverted to a dedicated subforum, eventually, as it was less work in managing. I had appointed a second bug system admin, yet still got heaps of stuff to do...
A tracker is a great idea, but would be misused, and there stupid "why is camera no work kthxbai" posts would continue by those not checking the tracker.
Integrating a attacker is pretty easy on a username perspective, but harder on a people perspective
Still, I like the idea, but can envisage huge amounts of work for svetius, making new categories every time a new rom appears etc ...
pulser_g2 said:
I used my own tracker for a while, but for xda we would have the issue of how to assign users to what role.
Every time I made a rom, I would need to request a new category and get ten pepper added as project authors ...
Trouble with the tracker that I found was that it just got messed up like the forums. Trust me that nobody searched it.
I reverted to a dedicated subforum, eventually, as it was less work in managing. I had appointed a second bug system admin, yet still got heaps of stuff to do...
A tracker is a great idea, but would be misused, and there stupid "why is camera no work kthxbai" posts would continue by those not checking the tracker.
Integrating a attacker is pretty easy on a username perspective, but harder on a people perspective
Still, I like the idea, but can envisage huge amounts of work for svetius, making new categories every time a new rom appears etc ...
Click to expand...
Click to collapse
yeah i agree with all of your points, i guess i was thinking that if it were somehow integrated into the forums then it'd be used more. as far as roles, a simple request to establish a project that would then be assigned to the dev in question. they could then choose to add extra people.
i just have no idea what tracker could and how fully integrated it would be with the forums.
it seems to me that if some of the noob "why is x not working" could be at least reduced by a bug tracker, hell we could even weed out the noobs by saying that unless you check and submit bugs no questions will be answered in the forum.
anyway, thought it was worth mentioning and getting the ball rolling. We could do some basic pilots of different trackers based on any known integration benefits.
I would like to know how to develop WP7 apps the fastest and essayist possible?
Check here[/urll]. This thread - especially post #1 - provides several ressources and links which include how-tos and guidelines on how to start developing for WP7. It also tells you what you need and where to get it.
> Abstract: I have been consolidating a complete, monolithic, and community editable guide for all mobile devices, to reform how XDA Developers works. Take a look, and edit or give suggestions... (Perhaps merge this with XDA University?)
## Rationale
XDA Developers is one of the largest and most important sites to mobile device development. We know all that; we've been here for years. And after staying here for a long time, it's hard to imagine anything different from the status quo; nor why the "new guy" is so frustrated and confused.
Unfortunately, owing to our messy evolution, the guides for most devices on XDA are, (quite honestly, no offense), outdated and disorganized, divided among tons of threads and maintained by OPs who may or may not be active. The XDA Wiki was built on the premise of consolidating the info from the forum, but the tendency to link to forum posts rather than bring in the full methods has made it utterly redundant, and therefore rarely edited or trafficked.
The reality is, forums are great for development and asking questions, but they are the wrong place for constantly fluctuating guides that demand united community support. The result is the status quo on XDA; a ceberus of information difficult to organize or sift through, resulting in newbies constantly asking supposedly "obvious" questions about methods and issues long since solved.
The question is, is it the noob's fault for not trusting or reading such disorganization, or could it be that we aren't making it clear how to proceed safely?
## Design Specifications
To rectify this situation, I have been compiling the Android Development Codex, a complete, monolithic, and community editable guide to the any device I could get my hands on, taking users all the way from unlocking to customization.
The codex will also give readers a few tips and tricks for troubleshooting common problems (so they don't have to wade through 900 posts to find the answer), and general guides to cool mods that can be made on the phone. Perhaps we could even teach people to create modifications to keep the community going.
The Android Development Codex is based on eight principles:
* Everything must be in the guide. We need customized "beginning to end" guides that give the user everything it takes to mod a device and deal with problems afterwards. As stated above, the XDA Wiki failed because it only linked to the forum, making it no more useful than a forum sticky.
* Mark or fix outdated information ASAP. Outdated information is the biggest issue with the status quo on XDA; at best, it won't work, and the new guy will come crying to the forums. At worst, devices will be bricked, leading to intense mobs of angry noobs. With a monolithic guide, as soon as new developments occur, we can post it in the Codex as a warning to all, and change the method if needed.
* No redundant information. There could be thousands of devices by the time we get to a finished state, and much of that info is exactly the same. This leads to duplication of work, and eventually outdated info. Examples are things like ClockworkMod instructions, Glossaries, and general OS mods. The Codex should consolidate as many mods as possible into general guides, and for things like glossaries and recovery instructions, Mediawiki-style templates should be used to pull them in.
* One customized guide for every device family. Every device is special in some way. The XDA Developers Book is great, but even the most general of rooting guides cannot tackle the thousands of unique circumstances that exist in every device. Rooting, Unlocking, Downgrading, and other unique things are under this umbrella.
* Always provide a manual method. Automatic "one-click" roots are great, but manufacturers are always out to patch the latest method. If we don't know how to do it by hand, we can't really find much of a solution.
* Ensure that all required files are accessible and stay accessible. Eventually, all good things must come to an end, and when people are no longer around to sweep the grounds, link rot sets in. This is very, very bad; one of the archives could contain a vital rooting program, and there would be no way to recover it. Just remember the fall of Megaupload. Always have multiple mirrors for every file, and perhaps archive everything into the Internet Archive when the community is gone.
* Give all sources for methods included. Credit must be given where credit is due, not only in deference to the original authors, but also to give the methods credibility.
* The ultimate goal is to transform a layman into a developer. For most people nowadays, modding mobile phones is their gateway into the workings of the computers that control our lives today, just like home computers were in the 80s. The Codex needs to clearly show how anyone can become an XDA-Developer and participate as enlightened individuals, rather than as mere participants.
## The Monolithic Guide
The Android Development Codex is here.
Currently, only the HTC HD2 and the HTC Droid Incredible have functionally complete guides at the moment.
The entire thing is stored on Github Wiki, so you can edit it if you have a github account. Hopefully, developers will all be able to come together once and for all, and work on one big guide, rather than tons of small, redundant, and outdated ones.
## The Android Development Codex is unfinished! Why are you releasing it now?
Originally, I was going to keep the Android Development Codex as a surprise until all the guides for the devices I owned were complete. However, a new project called "XDA University" is being started with similar goals, so am prematurely releasing my work to the community and awaiting further developments.
If anyone here has a hand in creating the XDA University, please contact me, because I have some great ideas on how to make it work, not to mention tons of data for us to start with.
You have a PM
This area is currently experimental and was set up by the XDA Administrators for development discussion. The idea in this section is for developers (not only recognized developers, but all developers) to have a place for discussion threads to "talk shop." What kind of talk? Some topics (that I'm making up as I type this) might include (and are certainly not limited to):
Overriding the power widget in the notification dropdown
Considerations of using gcc versions other than 4.4.3 for compiling the kernel
Tegra3: discussion on working around the SOC wake from sleep delay
This isn't a Q&A forum. However, developers might kick off discussions with a question. The difference? This belongs in Q&A: "My phone wakes up slow, will it go faster if I take my sdcard out?" On the other hand, the following might belong in this new section: "Has anyone tried adjusting the mmc detection timeouts to see if there's an impact on the SOC wakeup delays?" The assumption here is that the person asking the latter question actually knows what a mmc detection timeout is, how they'd change it, and has started to play around with it before posting the question.
As well, this section is not for posting finished products or "advertising" of kernels, apps, etc. This section is to discuss the process, not for the end result.
The hope (at least my own hope) is that developers can discuss things here instead of resorting the various other methods of communication we've used. At the same time, newer developers and even non-developers can LEARN from the conversations and eventually participate.
Depending on the reception (and difficulty moderating, probably) this experiment will either be expanded for other device types, completely shut down as a failure, or adjusted. Obviously, if we developers don't use it, it might be considered a waste of time and dissolved.
This section will be very closely moderated by moderators who are also developers and non-development discussion will be harshly dealt with.
Let's do development.
So normal users arent to post here?
For example, could this be used for devs to talk about S-off etc?
yes it can be. ANY user can post here as long as it's dev related.
Great Thought
Wilks3y said:
So normal users arent to post here?
For example, could this be used for devs to talk about S-off etc?
Click to expand...
Click to collapse
newer developers and even non-developers can LEARN from the conversations and eventually participate
Click to expand...
Click to collapse
just don't fill this thread with rubbish i'm not referring to you :good:
Recognized Developer Code of ConductAs 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 RequirementsTo 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.