What should the License Result Communication Process be?

[Justin Clift]

Hi all,

It's been a while now, so we should probably start putting together the 
(could be better named) "License Result Communication Process", to be 
followed to publish the results of submitted licenses.

Seem like an ok idea?

If so, some rough on-the-spot thoughts of things to include (not in order):

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

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

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

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

   + 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

Do these bits sound practical so far?

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

Regards and best wishes,

Justin Clift

-- 
The Flame Project - Open Source GUI for animated SVG & Flash
http://www.flameproject.org