Validity criteria for bugtrackers and bugtrackers links
 

Hi,

since some developers aren't taking seriously the QA rules and there's a lot of room for different interpretations in some cases, like the validity of the bugtracker fields, the Testing Squad decided to write some additional rules to clarify dubious situations: http://wiki.maemo.org/Bugtracker

These rules aren't final and need to be approved by the community as usual, this is just a call for further discussion.

Discussion at -Community ML: http://n2.nabble.com/Validity-criter....html#a4695909

Re: Validity criteria for bugtrackers and bugtrackers links
 

With that URL I am a bit afraid that newbies might think that it is the URL for the maemo.org Bugtracker instead. It's not clear that this refers to packages.

Re: Validity criteria for bugtrackers and bugtrackers links
 

I'm ok with that. It acknowledges specific alternatives to a formal bug tracking app, which is IMO important.

Re: Validity criteria for bugtrackers and bugtrackers links
 

Yeah i agree, having the types listed is a good idea.

I'd like to see a way of linking some of the great tutorials to the pages like bugtracking etc... so the process can be followed through from beginning to end. Its the little snags like the bugtracker link that have added a week onto my first attempt. But does also prove that if we tighten things up a bit, new coders can almost have an app in extras in under a month... (Not sure if that is good, but feels good to me!)

good point Andre :D - i probably would have!

Re: Validity criteria for bugtrackers and bugtrackers links
 

I do have a slightly different opinion. as much as i agree with bug tracking etc... for small projects it isn't allways needed. And after battling through QT and Python, the last thing i wanted was to have to learn Bugtracker, get another login, remember to visit it etc... (OK it's not that bad, as it emails you) - but doesnt portray a nice image to first timers.

I think working alongside the rest of the good single-sign-on work for meego forums and making sure that users can do bugtracking on the forum sign-on would also be a good idea. (As well as all the other options).

Re: Validity criteria for bugtrackers and bugtrackers links
 

We are also working in a checklist for developers with all the links, in order to smooth the testing process: http://wiki.maemo.org/Prepare_your_a...on_for_testing

Re: Validity criteria for bugtrackers and bugtrackers links
 

Are you reading my mind? :D :D good work.

Re: Validity criteria for bugtrackers and bugtrackers links
 

I'm not sure if making it easy for developers is the point here. Maemo.org has a repository where new developers can play and learn and needn't care at all about good packaging practices.

The whole point of having -devel, -testing and then Extras is that Extras should be a high quality repo that makes it easy for users (and power users who report bugs), not primarily for developers. (It's not all that difficult for developers, though.)

I expect developers who go all the way from -testing to Extras to be serious enough about their projects and their involvement with the community that registering an account @bugzilla and learning how to use the system isn't too much for them.

I'm just very sad how many developers (good developers of useful application) just seem to insist on not following the rules. When I find a project I would love to see in Extras, I cannot vote it up because it's just not "ready". I don't know why devs do something like that, even if you tell them how to correct the problem easily.

Re: Validity criteria for bugtrackers and bugtrackers links
 

Rob1n launched a side discussion regarding the value of encouraging/requiring applications to register their data files for backup. That topic also seems quite worthy of discussion, so I've moved those posts their own thread where that topic will (hopefully) be easier to find and won't side-track this thread.

Re: Validity criteria for bugtrackers and bugtrackers links
 

remember not all are tecnically dev's though... There is alot to pickup - so getting it all right first time is a challenge... I had to read hundreds of threads, lots of wiki posts, register at a garage, bugs, get answers on irc and maemo.org, buy 3 books... etc...

So sometimes its just making sure that when they look for help its a pleasure and not a chore ;)

(Allthough you are right ... experienced dev's probably have no excuse) - i'm hoping in my second app, i'm aware of the impending bugtracker doom, and plan sooner :D