[License-review] exploring tracking tool for license-review

[Josh berkus]

On 05/11/2016 10:46 AM, Allison Randal wrote:
> Hi all,
> 
> We're experimenting with Taiga.io[0] as an interface for tracking the
> license review process, and just put up a public project for it:
> 
> https://tree.taiga.io/project/osi-infra-osi-license-review/kanban
> 
> The status names are customizable, so before we start adding cards for
> the licenses currently in review, I thought we should do some
> brainstorming here on the list how to capture the license review
> workflow in a few simple statuses. My first thoughts for the workflow are:
> 
> SUBMITTED
> DRAFTING
> IN REVIEW
> READY FOR VOTE
> APPROVED
> REJECTED
> 
> Where a license starts in SUBMITTED, may circulate several times between
> DRAFTING and IN REVIEW, as changes are suggested and applied, moves to
> READY FOR VOTE when it's queued up for a board meeting vote, and then
> moves to APPROVED or REJECTED.
> 
> Does this list miss some stages? Do folks have suggestions on better names?

I'm concerned that "DRAFTING" doesn't make it clear that we're waiting
on the submitter.  "WAITING ON SUBMITTER" seems wordy, but it is the
actual state.  I'm worried that if we just call it "DRAFTING", the
submitter won't realize we're waiting for them.

Also, who decides when these statuses change?  In the past, we've had
some pretty strong disagreements about whether or not a license needed
to be revised.  We'll need some kind of ad-hoc procedure or it'll be
very confusing for sumbitters.