What should the License Result Communication Process be?

[Lawrence Rosen]

Ernie Prabhakar wrote:
> We'd love to do stuff like this, the difficulty is finding someone to
> commit to doing it.  Any volunteer Drupal programmers willing to help?

Certainly the obstacle isn't Drupal programming? Keeping a list of submitted
and approved licenses, and publishing minutes of board meetings, is
something that we used to do in OSI with minimal effort using a word
processor and email. (I know, because I used to do it myself.) Why is it so
difficult now? Nobody on the board can accept this responsibility? Perhaps
you need at least one other board member?

/Larry 


> -----Original Message-----
> From: Ernest Prabhakar [mailto:ernest.prabhakar at gmail.com]
> Sent: Tuesday, November 13, 2007 1:21 PM
> To: Justin Clift
> Cc: OSI License Discuss
> Subject: Re: What should the License Result Communication Process be?
> 
> Hi Justin,
> 
> On Nov 13, 2007, at 3:40 AM, Justin Clift wrote:
> > 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".
> 
> We'd love to do stuff like this, the difficulty is finding someone to
> commit to doing it.  Any volunteer Drupal programmers willing to help?
> 
> -- Ernie P.