> On 20 Sep 2016, at 19:34, Stefan van der Walt <stef...@berkeley.edu> wrote:
>> On Fri, Sep 16, 2016, at 01:35, François Boulogne wrote:
>> I think we need to determine how many boards we want (what github call
>> project, I don't like this word... anyway).
>> A big one with the progress or small ones, one per submodule? or one per
>> core dev?
> I think each board is associated with an outcome. So, e.g., we will
> decide on some projects such as "Improve Documentation", or "Add 3D
> capability", or "Catch up on review backlog". Each of those will then
> have a few standard columns that we have to decide on.
> An initial suggestion would be:
> Inbox (list all relevant PRs)
> In Progress (someone is working on it)
> Ready for Review (please review this work)
> Would that cover 80% of use cases, or do we need more columns?
This sounds good to me and we can add more columns as needed and as we gain
some experience with the workflow. Grouping comments into reviews and then
having a separate approval status is already a big step forward in my view.
> You received this message because you are subscribed to the Google Groups
> "scikit-image" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to scikit-image+unsubscr...@googlegroups.com.
> To post to this group, send an email to firstname.lastname@example.org.
> To view this discussion on the web, visit
> For more options, visit https://groups.google.com/d/optout.
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To post to this group, send an email to email@example.com.
To view this discussion on the web, visit
For more options, visit https://groups.google.com/d/optout.