Skip to Main Content
Apache Events The Apache Software Foundation
Apache 20th Anniversary Logo

This was extracted (@ 2024-03-20 21:10) from a list of minutes which have been approved by the Board.
Please Note The Board typically approves the minutes of the previous meeting at the beginning of every Board meeting; therefore, the list below does not normally contain details from the minutes of the most recent Board meeting.

WARNING: these pages may omit some original contents of the minutes.
This is due to changes in the layout of the source minutes over the years. Fixes are being worked on.

Meeting times vary, the exact schedule is available to ASF Members and Officers, search for "calendar" in the Foundation's private index page (svn:foundation/private-index.html).

Conferences and ConCom

15 Dec 2004

 It was reported that it was still too early to report on the
 full results of ApacheCon 2004, held last month, but that the
 event did appear to make a profit.  However, the $25,000 bounced
 check to the ASF did not alleviate the board's growing concern
 and unease with Security Travel.  There are also some reports
 of speakers not being paid and/or reimbursed.

 The board further discussed the difficulties we would face if
 Security Travel was not chosen as the organizer. Some of the
 issues would be: the time taken in searching for a new
 producer, trying to forge a new working relationship, and
 possibly trying out the new producer with a small conference or
 involving them with the ApacheCon Europe effort.

 ConCom is discussing internally the basic question "What Is, Or
 Should Be, ApacheCon." Some suggested considerations were the
 size of the conference, the pricing structure, and target
 audience(s) of the conference.

 The board spent some time in executive session discussing
 our contract details with Security Travel.

14 Nov 2004

 The board expressed its extreme displeasure with the work
 done by Security Travel regarding ApacheCon.  There was
 debate on whether the board should restrict ConCom from
 renewing any contract or agreement with ST.  The general
 consent was that this restriction was not going to be
 placed, but that the board withheld the right to do so.
 The ConCom was tasked with "determining the look, feel
 and direction of ApacheCon" and submitting that to the
 board.  The ConCom was further tasked with coming up
 with creative new ideas regarding what we want ApacheCon
 to be (ie: what is the major focus of ApacheCon? A
 revenue source? A community building effort? etc...)