What should the License Result Communication Process be?

[Zak Greant]

Hi Justin, Greetings All,

Sorry for the late response here.

I've been playing about with doing something like this (and so has
Steve Mallett, though I haven't seen what he has done.)

I'm just using a customized version of Trac - you can see the rough
work at https://osi.osuosl.org/

I've held off sharing because I still have more work to do (and the
admins for the site are somewhat engaged with other projects.)
However, most of us have used issue trackers and should get the
general idea.

I've been triaging some messages from the past of license-discuss as
sample data. Keep in mind that the sample data won't (yet) reflect the
actual state of things.

>    + Something on website listing licenses "in queue" (plus date)

https://osi.osuosl.org/report/9

>    + Something on website giving visual process flow (flowchart?)

Trac has a gantt plugin that should provide the functionality needed

>    + Something on website listing licenses accepted, rejected, and
> perhaps "needing further work for re-submission".

Custom reports can easily show this.

I've embedded one on the front page to demonstrate.

>      Pretty much mandatory to have a paragraph summarising caveats,
>      why something has been rejected, needs resubmission, etc

I had planned on tracking this in the ticket, but we should summarize
this in a convenient place as well.

>    + List of places the results or updated status must get to, and
>      in which order.
>
>      i.e. after decision:
>
>          a) email to submitter
>          b) license-discuss mailing list
>          c) update website as above

Sounds sensible - and like something that should be added to the
license approval process.

> Do these bits sound practical so far?

Quite - would you like a Trac account? :)

> (perhaps we'll need to have effort estimates added after we get this
> fleshed out a bit?)

-- 
Cheers!
--zak