Josh, thanks so much for adding to the report wiki page.  I submitted the
report as represented at:
https://cwiki.apache.org/confluence/display/VCL/2016-03-16+Apache+VCL+Board+Report

Regarding the report's content, I added a secondary link to the thread
since it's now cross posted on our user and dev lists.  The original link
only included the user list content.  I also added a sentence asking board
and ASF members to review the thread and participate if they wish.

Thanks,
Andy

On Wed, Mar 9, 2016 at 1:28 PM, Andy Kurth <[email protected]> wrote:

> I have created a stub for this month's board report at:
>
> https://cwiki.apache.org/confluence/display/VCL/2016-03-16+Apache+VCL+Board+Report
>
> This one snuck up on me -- it's due today.  I'll send it later tonight
> (EST).  We need to populate these sections:
>
> *Activity*
> Is anyone working on anything?  If so what is the status?  Where are we at
> regarding a release?
>
> *Health report - Please use this paragraph to elaborate on why the current
> project activity (mails, commits, bugs etc) is at its current level.*
> We should reference the "State of Apache VCL" thread here.  I think we can
> hold off on adding anything under "issues requiring board attention" for
> now since there has been some good discussion.
>
> *Mailing list activity - Please explain what the following statistics mean
> for the project. If there is nothing significant in the figures, omit this
> section.*
> Activity has continued to be low prior to the past week.  This was
> specifically mentioned in the previous board report:
>
> - User list traffic has been surprisingly low since July. Our last release
>> was in April and we saw an expected increase in traffic the following from
>> April to June as users upgrade. I would have expected traffic to taper off
>> more gradually.
>> - Dev list traffic has been about normal considering we haven't had a
>> flurry
>> of activity preceding a release.
>
>
> Does anyone have anything to add?
>
> Thank you for your help in preparing this report,
> Andy
>

Reply via email to