Looks like there was a format change from January to February in the incubator 
podling headers. 

January:

-------------------- Amaterasu
-------------------- Annotator
-------------------- BatchEE

February:

--------------------
Airflow
--------------------
Crail
--------------------
ECharts
Maybe we need to look closer at this. Why was this change made? What did it 
affect? Is there a change in the agenda or just the published minutes.

I'm copying whimsy dev.

Craig

> On Oct 4, 2018, at 8:44 AM, sebb <[email protected]> wrote:
> 
> On Thu, 4 Oct 2018 at 16:29, Craig Russell <[email protected]> wrote:
>> 
>> Hi Sebb,
>> 
>> I don't see anything wrong in 
>> https://www.apache.org/foundation/records/minutes/2018/board_minutes_2018_01_17.txt
>>  for Amaterasu or Freemarker.
>> 
>> Please elaborate.
>> 
> 
> The section starts:
> 
> == cut here ==
> -------------------- Amaterasu
> == cut here ==
> 
> However Whimsy expects
> 
> == cut here ==
> --------------------
> Amaterasu
> == cut here ==
> 
> c.f. the same podling in
> https://www.apache.org/foundation/records/minutes/2018/board_minutes_2018_07_18.txt
> 
> There should be an entry for Jan 2018 in Amaterasu, but there is not:
> https://whimsy.apache.org/board/minutes/Amaterasu.html
> 
>> Thanks,
>> 
>> Craig
>> 
>> On Oct 4, 2018, at 5:22 AM, sebb <[email protected]> wrote:
>> 
>> As noted in https://issues.apache.org/jira/browse/WHIMSY-209, some of
>> the podling reports have an unexpected syntax in the published
>> minutes.
>> 
>> Is it OK to fix such errors?
>> For example, remove trailing spaces after the hyphens, and replace the
>> space with new-line in lines of the following form:
>> 
>> -------------------- FreeMarker
>> 
>> (the above example is found in the Jan 2018 minutes)
>> 
>> Sebb
>> 
>> 
>> Craig L Russell
>> Secretary, Apache Software Foundation
>> [email protected] http://db.apache.org/jdo
>> 

Craig L Russell
Secretary, Apache Software Foundation
[email protected] <mailto:[email protected]> http://db.apache.org/jdo 
<http://db.apache.org/jdo>

Reply via email to