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:
On Thu, Dec 6, 2012 at 10:17 PM, Quim Gil <[email protected]> wrote:
On 12/06/2012 10:56 AM, Lydia Pintscher wrote:
For Wikidata at least we do set bugs to ASSIGNED most of the time. But
we do leave the assignee set to the mailing list. If there is a strong
preference to also change the assignee I can bring it up in the team.
Bitte bitte biiiitte! :)
Hey Quim,
I brought this up today in our daily meeting. It seems people do not
think changing this is doable. The way we work in the team is that at
the beginning of the sprint we set the tasks we'll be working on to
assigned and add them to the task board in the office here. Then
people pick things from the board as they go along during the sprint
by putting a pin with their face on it on the task. Duplicating this
information once again seems like it'll not get done... I think for
people outside the team setting the status to assigned is enough. And
if they want to know who exactly is working on it they can ask in the
bug.
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
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
