I was wondering what happens to tracker issues that have been assignet to 'moodle.com', rather than a specific person.
For example, I have found a javascript typo that would take about 30 seconds for someone with CVS access to fix ( http://tracker.moodle.org/browse/MDL-22535 ), but I'm not sure how to bring this to the attention of someone who has that access.
Should I just leave the issue and hope that it gets assigned to the right person at some point in the future, or should I look through CVS and assign it to the person who last updated the section of code that has the mistake in it?
I'm working through the backlog 
But looking though CVS to find the right person is not a bad idea either!
Thanks for that - I realise now, that I don't seem to be able to change who bugs are assigned to anyway (at least not when they are assigned to 'moodle.com' automatically).
Hi Davo
I've previously been told by a developer (and by Martin!) to add them as a watcher to the tracker item (click 'Watching' on the Operations menu) then comment on the issue - this sends an email to all watchers, including the developer you just assigned as a watcher!
Of course, we need to make sure we're not spamming people so as Martin advises above look through CVS to find the appropriate developer to assign! the Developer page is also very helpful I've found!
Cheers
teresa
I've previously been told by a developer (and by Martin!) to add them as a watcher to the tracker item (click 'Watching' on the Operations menu) then comment on the issue - this sends an email to all watchers, including the developer you just assigned as a watcher!
Of course, we need to make sure we're not spamming people so as Martin advises above look through CVS to find the appropriate developer to assign! the Developer page is also very helpful I've found!
Cheers
teresa
Really, be very careful doing that.
Most core Moodle developers already have hundreds of bugs assigned to them, and the last thing they want is more. (We do, also, quite like being able to mark bugs resolved fixed.)
Bringing a bug to the attention of a developer in a way that just pisses them off is probably not productive. (Although other developers may not be as cantankerous as me.)
So, useful help with bug triage == a good thing, and sorely needed. Causing unnecessary bug spam == very bad thing.
Most core Moodle developers already have hundreds of bugs assigned to them, and the last thing they want is more. (We do, also, quite like being able to mark bugs resolved fixed.)
Bringing a bug to the attention of a developer in a way that just pisses them off is probably not productive. (Although other developers may not be as cantankerous as me.)
So, useful help with bug triage == a good thing, and sorely needed. Causing unnecessary bug spam == very bad thing.
Tim, is there a way that you would recommend going about drawing the right person's attention to a bug?
For example, I had a simple DB error that I found a week or so ago, I followed Teresa's advice and (after carefully checking CVS), added Petr to the tracker report watch list, who then fixed it within about 10 min of looking at it (and seemed quite happy that I had done so).
Obviously I only added him as his name was against the line of code that was causing the error (and the lines of code that generated the sql being passed on to that line).
I would have dropped Petr a message via moodle messaging, but he only accepts messages from contacts, so I wasn't sure of a better way to assign it in his direction.
For example, I had a simple DB error that I found a week or so ago, I followed Teresa's advice and (after carefully checking CVS), added Petr to the tracker report watch list, who then fixed it within about 10 min of looking at it (and seemed quite happy that I had done so).
Obviously I only added him as his name was against the line of code that was causing the error (and the lines of code that generated the sql being passed on to that line).
I would have dropped Petr a message via moodle messaging, but he only accepts messages from contacts, so I wasn't sure of a better way to assign it in his direction.
Exactly, when you get it right it is really helpful.
And, if it is worth sending a message, it is better to do it via the tracker than any other way.
The thing that really winds me up if people who just go to the tracker to whinge and moan; and people who create blatant duplicate bugs. If you are trying to be helpful, then you should not have to worry.
And, if it is worth sending a message, it is better to do it via the tracker than any other way.
The thing that really winds me up if people who just go to the tracker to whinge and moan; and people who create blatant duplicate bugs. If you are trying to be helpful, then you should not have to worry.
Thanks for the clarification - I'll make sure I do that with any further bugs I find.
Tim,
I really appreciate your position but I'm concerned that what you say here might actually put people off adding things to the tracker.
I have spoken to users on numerous occasions who have found problems (often minor) in Moodle and my reaction is "well, have you added it to the tracker". Of course, they never have. I encourage people to use it all the time.
If they have to trawl through CVS and consider whose day they might be upsetting then they're definitely not going to do it. Actually, *I* would stop doing it. Much better that they go in the 'assigned to moodle.com' black hole than that, surely?
Also, I create duplicate posts all the time. I don't mean to - I do look and I do know how to work the search facilities and I *still* miss duplicates. Again, I would be happier that they are reported twice than not at all. However, as you say, I do not - for the most part - have to fix them. Maybe there are now too few developers fixing bugs or something.
I really appreciate your position but I'm concerned that what you say here might actually put people off adding things to the tracker.
I have spoken to users on numerous occasions who have found problems (often minor) in Moodle and my reaction is "well, have you added it to the tracker". Of course, they never have. I encourage people to use it all the time.
If they have to trawl through CVS and consider whose day they might be upsetting then they're definitely not going to do it. Actually, *I* would stop doing it. Much better that they go in the 'assigned to moodle.com' black hole than that, surely?
Also, I create duplicate posts all the time. I don't mean to - I do look and I do know how to work the search facilities and I *still* miss duplicates. Again, I would be happier that they are reported twice than not at all. However, as you say, I do not - for the most part - have to fix them. Maybe there are now too few developers fixing bugs or something.
Thanks for these thoughts Tim... I have only done this a couple of times, the first time (on a quiz issue) was to add you, on your advice, while at the 2008 Aussie moot!!
I think it's fine to add someone as a watcher if you are pretty sure they need to see it and you think an important issue is being forgotten. If I didn't think so then you wouldn't have access to do so.
Please don't let Tim's reaction stop you adding other people as watchers. However, if you abuse this then I'm sure the person involved will let you know.
Generally though, it should NOT be necessary to manually add anyone. There's a lot of default processes in place within the tracker to make sure things automatically get to the right person as long as your issue is categorised correctly, and it's best to just let that happen. Just remember we all have big backlogs.
(All I need is 20 more developers I can trust. )
Please don't let Tim's reaction stop you adding other people as watchers.
Generally though, it should NOT be necessary to manually add anyone. There's a lot of default processes in place within the tracker to make sure things automatically get to the right person as long as your issue is categorised correctly, and it's best to just let that happen. Just remember we all have big backlogs.
(All I need is 20 more developers I can trust.
Well, Martin, at least our supervisor at eSchool has encouraged us to really contribute to the 2.0 development process as a way not only to get the release out as soon as possible, but to give back to the project & community that has benefited us so much all these years.
Yeah, it's not the same as having X number of trusted core developers, but at least there are some us that are trying to make the jobs of those developers easier by reporting and even trying to fix bugs as we find them. I know my experience so far reporting bugs for 2.0 so far is that the developers jump right on them and get them fixed, even if they were knee deep in something else, just because someone reported it. That's awesome!
Yeah, it's not the same as having X number of trusted core developers, but at least there are some us that are trying to make the jobs of those developers easier by reporting and even trying to fix bugs as we find them. I know my experience so far reporting bugs for 2.0 so far is that the developers jump right on them and get them fixed, even if they were knee deep in something else, just because someone reported it. That's awesome!
Cheers, Basil. Thanks lots for getting involved, we really appreciate it.