search

folklabs / communitydata

Promoting the use of open data by the community.
GNU General Public License v2.0
3 stars 1 forks source link

Issues getting created but not assigned #130

Closed djwesto closed 10 years ago

djwesto commented 10 years ago

I've noticed that the following Issues have been created without anyone getting assigned to them:

129, #124, #121, #119, #69, #55, #52 , #40, #38, #36, #8, #1

It's important that an issue gets an assigned individual, even if it's the wrong person.

@GilesGibson I can assign someone to these but in future, when you're creating issues, please can you make sure you assign them?

GilesGibson commented 10 years ago

I think that general issues that didn't have a known home were left unassigned. It was how things were earlier on in the debug project. Maybe a few more got left in limbo land later on as well as the precise recipient was unsure. I will go through and assign.

djwesto commented 10 years ago

Cool. Cheers!

pmackay commented 10 years ago

I would actually suggest the important thing is that a milestone is set. Issues in backlog can be left, they dont have to have someone assigned. Issues in v1.0 should be assigned if there is an obvious owner.

djwesto commented 10 years ago

OK. Issues in backlog can be left and only assigned once they're moved to have a milestone attached. That seems like a sensible rule.