Good to see that this discussion is not only about quick fixes. This answer goes to wikidata-bugs but it is also applicable to Nobody. On 12/07/2012 03:17 AM, Lydia Pintscher wrote: I just did: https://bugzilla.wikimedia.org/show_bug.cgi?id=42817 There is more at http://bit.ly/WO5wBk (my new saved search) Let's see what happens. :) Going through a sample of bugs ASSIGNED to Nobody and Wikidata it seems that each developer goes to their newly assigned bug reports and sets them to ASSIGNED (and CCing themselves). Is that the case or is there someone acting as proxy for the developers? If they are the ones doing the work, how hard is to click "take"? This is now easier than CCing you. If someone is doing the proxy work for the developers (as it happend too frequently when I worked at Nokia, and I have seen other corporations doing the same with public bug trackers) then the main risk is to have a disconnect between the reporter and the bug discussion and the actual work that someone else is doing inside an organization, because that developer is not even getting the feedback that bug might raise. Adding the actual developer to the CC field helps fixing this problem but, once you are there, assigning the bug to the actual developer is just the same amount of work. Conclusion: assigning bugs to the people that got them assigned is quite simple, a good open source software development practice and one factor helping getting more and better contributions. My work consists in helping bringing more and better contributions to Wikimedia software projects, and this is why I care. I understand modifying processes is always an annoyance for busy teams but at least I hope you get what we all get (you included) for the price of a click. Thank you for reading. :) -- Quim Gil Technical Contributor Coordinator Wikimedia Foundation