> 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.
OK with that. > An initial suggestion would be: > > Inbox (list all relevant PRs) > In Progress (someone is working on it) > Ready for Review (please review this work) > Done > > Would that cover 80% of use cases, or do we need more columns? Maybe we should had Needs Decision. Often, we have tickets stuck on a decision to take, either on new features (names, API...) or on refactoring (change API, dependencies, add new functions, reorganize a code...). These choices are often not straightforward and we need different opinions. -- François Boulogne. http://www.sciunto.org GPG: 32D5F22F -- 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 scikit-image@googlegroups.com. To view this discussion on the web, visit https://groups.google.com/d/msgid/scikit-image/5edc406e-b7b9-c795-78b0-df1119557c60%40sciunto.org. For more options, visit https://groups.google.com/d/optout.
