[ckan-dev] 'Awaiting review' tag on github issues

[Toby Dacre]

On 15 February 2013 10:18, Sean Hammond <sean.hammond at okfn.org> wrote:

> > I want to have a roadmap meeting where we're not just reactively fixing
> > things / reviewing bugs, but planning and moving stuff forward. For
> example
> > I'm putting together a spec for more coherent data explorer functionality
> > and ability for admins to 'invite' users - i.e. create user account and
> > assign them roles. Presumably just adding this as a github issue creates
> > noise
>
> Yeah, I think so. I think for new features generally, they shouldn't be
> added to github issues until someone starts working on them (and at that
> point, it could just become a standalone pull request once there's some
> code for it, doesn't actually need to be an issue as such).


we need the issue for the number in our commit messages/branch name do we
not?

And keep the
> issues more for reporting bugs.
>
> So roadmap trello board seems the right place to collect and prioritise
> these.
>
> Although if you're putting together a spec, I think the spec itself
> should go on the github wiki, we should keep all our specs there, rather
> than lose them in different trello cards and google docs. We can add a
> specs page to the wiki to collect them all together.
>
> _______________________________________________
> ckan-dev mailing list
> ckan-dev at lists.okfn.org
> http://lists.okfn.org/mailman/listinfo/ckan-dev
> Unsubscribe: http://lists.okfn.org/mailman/options/ckan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.okfn.org/pipermail/ckan-dev/attachments/20130215/3d26d45b/attachment-0001.html>