Hi Sam,

Foundation/board is ambiguous. Sorry.

Look at https://svn.apache.org/repos/private/foundation/board

You will find board agendas for April, May, June, and July and minutes for 
April, May, several for June (including f2f which I'm not concerned with right 
now).

When processing the board/calendar.html, the minutes should have been deleted 
and the agendas moved to archived agendas.

Craig

> On Jul 12, 2017, at 6:33 PM, Sam Ruby <[email protected]> wrote:
> 
> On Wed, Jul 12, 2017 at 8:21 PM, Craig Russell <[email protected]> wrote:
>> Hi,
>> 
>> The agenda tool has been working so well I have not looked at the end result 
>> for a while.
>> 
>> It seems that the "publish minutes" part of the tool is not working.
>> 
>> If you look at foundation/board you will see that the minutes from April and 
>> May 2017 are on the web site but the corresponding text files are not 
>> organized.
>> 
>> I can process these files manually but thought that we should see what went 
>> wrong.
> 
> I'm confused.  What are you seeing, and what do you expect to see?
> 
> I see April and May here: 
> https://www.apache.org/foundation/board/calendar.html
> 
> Furthermore, they appear to have been committed in June:
> 
> $ svn log -l 1 calendar.mdtext
> ------------------------------------------------------------------------
> r1799500 | clr | 2017-06-21 15:34:26 -0400 (Wed, 21 Jun 2017) | 1 line
> 
> Publish 17 May 2017 minutes
> ------------------------------------------------------------------------
> 
> $ svn log -l 1 board_minutes_2017_05_17.txt
> ------------------------------------------------------------------------
> r1799499 | clr | 2017-06-21 15:34:23 -0400 (Wed, 21 Jun 2017) | 1 line
> 
> Publish 17 May 2017 minutes
> ------------------------------------------------------------------------
> 
>> Thanks,
>> 
>> Craig
>> 
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> [email protected] http://db.apache.org/jdo
> 
> - Sam Ruby

Craig L Russell
Architect
[email protected]
P.S. A good JDO? O, Gasp!





Reply via email to