Jan,
Yes its nice for organisation you have a BugTracker but i think problems what found a Team Member can you lock and solve directly .
Maybe not the right place, but I think there's still some value to this story - I had this manager, and it was me an my colleague working for him. He didn't believe much in tickets and keeping track on work, so we used to discuss issues as they came along, while I was working mainly on this area and all was perfectly fine, cause I used to create tickets for everything I done, even if he didn't. And at some point, he assigned me to something else, while he gave my old work to someone else. BUT, because he didn't search for existing tickets and why we made some of the changes we made, he was just telling this other developer to do this and that. To find out at a later stage discussing with this other developer (who also happened to be my friend) that a lot of the things I used to do were either undone or re-done, just because the manager forgot what we discussed at the time and why we made the decisions we made. I showed him the tickets and he was like, wtf, why he didn't tell me about this? Why, because he couldn't remember all the stuff. Point is, keeping track on work, issues and decisions through tickets saves you from a lot of people being busy for no particular reason, and wondering later, why the hell did we make a change.
Yes, it might look like unnecessary overhead, it might seem that a developer might just like the "paper work", but it's not about that - it's about documenting everything along the way, even with the littlest details that you can put into a ticket, it may be useful later.
... when the same on main xbmc is working with the paplayer and on xbmc4xbox not than it this a bug.
And I agree with you - find a scenario where it doesn't work, create a ticket, and fix it yourself or let someone else to fix it. It will get eventually found, referenced and someone might say, hey I've seen this being fixed in mainline, this is where. Keep the discussion between yourself and another person, and it will stay just that, a discussion. We all disconnect from this project and then come back when we have some time, this is exactly what the tickets are, they allow you to hook back in when you get some time to look at it.
@All
Although this thread developed into something else, it is an opportunity to grow
Let's all agree to meet in the middle - if most of us say lets get organized and create tickets, let's do that. If you think PAPlayer or some other player requires attention, let's create a ticket and focus on that. I can't get you all focused on what I'd like to see fixed (TakeScreenshot HTTP API wink wink nudge nudge
), but I create a ticket to which maybe some else might have an idea, or I might find a fix and close it later. Let's all play nice and can still drive this forward, maybe even learn something along the way.
the bugtracker is the right place for bugs. I try and find time to look at everything I can. You cannot mention something on the forum, and expect it to be remembered in xx months time by me, or even guarantee I will see it.