Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Markdown
Goals
==============================================================================

* Organise the selection, promote and celebrate incredible content for our target audience

* Select tracks and track leads and help organise their work.
  - Rotating track leads / co-leads?
  - Fair / blind / inclusive reviews, constructive feedback to authors.
  - Good balance of talks, always something to go see.
  - Work with the track chairs to publicize CFPs and selected talks

* Work with the communications committee for announcements.
  - Social media, announce@apachecon.com, planners@apachecon.com, announce@apache.org(?), blog, website
  - CFP reminder emails to registered attendees
  - Program announcements

* Work with the tech committee (including website)
  - Publishing the schedule and reference materials
  - Making slides and videos available after the conference?


Questions
------------------------------------------------------------------------------

* What other than talks? Lightning talks? 
  - Who finds and approaches keynote speakers?
  - Poster sessions!
  - Birds of a feather
  - Key signing party (during a break)
* How many submissions can we expect to deal with?
* What percentage of **accepted** should we expect to actually show?
  - Waitlist percentage?
  - Backup talks to fill in?

Telling a story
------------------------------------------------------------------------------

A conference should be a rewarding experience for everyone: the audience (of course), but also speakers, sponsors, as well as generating content for future viewers.

* Beginner track chairs pick talks.
* Intermediate track chairs pick the whole track as a coherent story.
* Advanced track chairs coordinate across tracks. Like "after this talk you may want to skip over to this other track for this talk"

Structure and schedule
==============================================================================

ACNA 2022 Structure
------------------------------------------------------------------------------

* 9 rooms, 7 keynotes, 160 talks (normally 5-7 talks simultaneously)
* Lightning talks had the exclusive last slot on the second last day.
* Last day: 1 keynote and later start.

| Start | Duration | Note       |
|-------|----------|------------|
| 09h00 | 15m +5   | Welcome    |
| 09h20 | 30m +5   | All 1      |
| 09h55 | 30m      | All 2      |
| 10h25 | 55m      | **Coffee** |
| 11h20 | 40m +10  | Talk 1     |
| 12h10 | 40m      | Talk 2     |
| 12h50 | 90m      | **Lunch**  |
| 14h20 | 40m +10  | Talk 3     |
| 15h10 | 40m +10  | Talk 4     |
| 15h40 | 30m      | **Coffee** |
| 16h10 | 40m +10  | Talk 5     |
| 17h00 | 40m +10  | Talk 6     |
| 17h50 | 40m      | Talk 7     |

CoC EU 2023 [Suggested structure][CoCEU24Tracker] Radisson Blu Carleton
------------------------------------------------------------------------------

* Harmony Hall (380), breaks out into:
  - Melody (80)
  - Symphony (80)
  - Rhapsody (80)
* Carleton Hall (80) (with obstructing pillars?)
* Community lounge (??)
* 8 talks per day in 4 rooms ==> 96 talks
* **Two types of talks: 30min and 40min ??**

| Start | Duration | Note          |
|-------|----------|---------------|
| 08h15 | 15m      | Welcome       |
| 08h30 | 30m      | All 1         |
| 09h00 | 30m      | All 2         |
| 09h30 | 30m      | All 3         |
| 10h00 | 30m      | **Break**     |
| 10h30 | 40m      | Talk 1        |
| 11h15 | 40m      | Talk 2        |
| 12h00 | 40m      | Talk 3        |
| 12h40 | 60m      | **Lunch**     |
| 13h40 | 30m      | Talk 4        |
| 14h10 | 30m      | Talk 5        |
| 14h40 | 20m      | **Break**     |
| 15h00 | 40m      | Talk 6        |
| 15h45 | 40m      | Talk 7        |
| 16h30 | 40m      | Talk 8        |
| 17h10 | 90m      | **Reception** |

[CoCEU24Tracker]: https://docs.google.com/spreadsheets/d/1VM3FPsZviPm5Ln9BRzzQYR52EA5TrNHhQCcuR7MAd0E/edit#gid=354354676 "Community Over Code 24 Tracker"

Timeline
==============================================================================

Estimation
------------------------------------------------------------------------------

(Estimated dates are based on ACNA 2022)

|       | What                          | ACNA 22    | CoC EU 24      | Notes                                                  |
|-------|-------------------------------|------------|----------------|--------------------------------------------------------|
| T-216 | Call for Tracks               | 2022/03/01 | **2023/10/31** | Earlier: Keep in mind track lead fatigue fromCoC NA 23 |
| T-202 | Call for Tracks closes        | 2022/03/15 | **2023/11/14** |                                                        |
| T-195 | Announce tracks               | 2022/03/22 | **2023/11/21** |                                                        |
| T-192 | Call for Reviewers            | 2022/03/25 | **2023/11/24** |                                                        |
| T-187 | Call for Presentations        | 2022/03/30 | **2023/11/29** |                                                        |
| T-158 | Call for keynote suggestions  | 2022/04/28 | **2023/12/28** |                                                        |
| T-133 | Call for Presentations closes | 2022/05/23 | **2024/01/22** |                                                        |
| T-124 | Track allotments finalized    | 2022/06/01 | **2024/01/31** |                                                        |
| T-115 | Track schedules due           | 2022/06/10 | **2024/02/09** |                                                        |
| T-102 | Speaker notifications sent    | 2022/06/23 | **2024/02/22** |                                                        |
| T     | First day of the conference   | 2022/10/03 | **2024/06/03** |                                                        |

Communication examples
------------------------------------------------------------------------------

| What                          | ACNA 21                  | ACNA 22                                       | CoC NA 23                                                                                                  | CoC Asia 23 |
|-------------------------------|--------------------------|-----------------------------------------------|------------------------------------------------------------------------------------------------------------|-------------|
| Call for Tracks               | [2022/03/01][ACNA21-CFT] | [2022/03/01][ACNA22-CFT]                      | [2023/02/08][CoCNA23-CFT]                                                                                  |             |
| Call for Tracks closes        |                          | 2022/03/15                                    | 2023/03/01                                                                                                 |             |
| Announce tracks               |                          | [2022/03/22][ACNA22-TrackAnnounce]            |                                                                                                            |             |
| Call for Reviewers            |                          | [2022/03/25][ACNA22-CFR]                      |                                                                                                            |             |
| Call for Presentations        |                          | [2022/03/30][ACNA22-CFP]                      | [2023/03/08][CoCNA23-CFP] [News][CoCNA23-CFP-News] [Site][CoCNA23-CFP-Site] [Twitter][CoCNA23-CFP-Twitter] | 2023/05/30  |
| Call for keynote suggestions  |                          | [2022/04/28][ACNA22-CFKN]                     |                                                                                                            |             |
| Call for Presentations closes |                          | 2022/05/23                                    | 2023/07/13                                                                                                 | 2023/06/06  |
| Track allotments finalized    |                          | [2022/06/01][ACNA22-TrackNum]                 |                                                                                                            |             |
| Track schedules due           |                          | 2022/06/10 [2022/05/31][ACNA22-TrackReminder] |                                                                                                            |             |
| Speaker notifications sent    |                          | [2022/06/23][ACNA22-CFPAccepted]              |                                                                                                            |             |
| First day of the conference   |                          | 2022/10/03                                    | 2023/10/07                                                                                                 | 2023/08/18  |

[ACNA21-CFT]: https://lists.apache.org/thread/xxk630donrwqjgno5l1y78v3wml50lod "Call for Tracks ACNA 2021 (Email)"
[ACNA22-CFKN]: https://lists.apache.org/thread/t1c6hoys4jq6ky4n6jrkbgt21tn2r92l "Call for Keynote suggestions (Email)"
[ACNA22-CFP]: https://lists.apache.org/thread/ho1h6lf8g8hxmfylddstmffbr9b0942l "Call for Presentations ACNA 2022 (Email)"
[ACNA22-CFPAccepted]: https://lists.apache.org/thread/hkt9cx3j79ctp5dbwpo29qn078pk2ljr "Speaker notifications sent (Email)"
[ACNA22-CFR]: https://lists.apache.org/thread/dmjwh1yocz04rdwhs2fs1r0mfbh4mjzv "Call for Reviwers ACNA 2022 (Email)"
[ACNA22-CFT]: https://lists.apache.org/thread/xxk630donrwqjgno5l1y78v3wml50lod "Call for Tracks ACNA 2022 (Email)"
[ACNA22-TrackAnnounce]: https://lists.apache.org/thread/9mzy173wfs93pwm3fxfmohsd8y43r7x4 "Track announcement and allotments"
[ACNA22-TrackNum]: https://lists.apache.org/thread/znz2j5mgvlwlxvn7hngh2w1735z65lb6 "Track allotments (Email)"
[ACNA22-TrackReminder]: https://lists.apache.org/thread/w07pcmjmc49b5p1lctfzg6qq37bxddjg "Reminder: Track Schedules Deadline (Email)"
[CoCAsia23CFP-Twitter]: https://twitter.com/TheASF/status/1663344745983234048 "Call for Presentations (Twitter)"
[CoCNA23-CFP-News]: https://news.apache.org/foundation/entry/announcing-our-annual-event-community-over-code "Call for Presentations (News)"
[CoCNA23-CFP-Site]: https://communityovercode.org/call-for-presentations/ "Call for Presentations (Site)"
[CoCNA23-CFP-Twitter]: https://news.apache.org/foundation/entry/announcing-our-annual-event-community-over-code "Call for Presentations (Twitter)"
[CoCNA23-CFP]: https://lists.apache.org/thread/c86dog0pzb2pphrt0kshjnnzmd0mqpfk "Call for Presentations CoC NA 2023 (Email)"
[CoCNA23-CFT]: https://lists.apache.org/thread/w1kmo97osfyts73mf3kbqobtc2zhc15h "Call for Tracks CoC NA 2023 (Email)"

ApacheCon 2022 Tracks
------------------------------------------------------------------------------

* Big Data
* Cassandra
* Cloud Runtime/Cloud Native
* CloudStack
* Community
* Data Engineering
* FinTech
* Geospatial and Remote Sensing
* Groovy
* Highlights
* Incubator
* Internet of Things
* Libraries, Frameworks and Developer Tools
* Performance Engineering
* Pulsar Event Streaming
* Search (Lucene/Solr)
* Tomcat

Call for Tracks
==============================================================================

Goals:

* **Identify the categories of talks that will make up the program.**
* Finding track leads (and others interested in joining the Program Committee).
* Testing community interest in different subjects, merging/splitting as necessary.
* Estimating the number of sessions per-track and tentatively blocking out rooms and dates to help guide the CfP.

Questions: 

* What exactly is a track lead volunteering for?
  - Publicity for the CfP?  Competing for audience at the event?
  - Do they need to be at the conference? Should they be giving a talk?
  - Are there hidden responsibility or benefits? (Free registration, speakers dinner?)
  - If we merge tracks, how do we make sure everybody feels valued?

Audience: 

* [planners@apachecon.com] (Most previous track leads are subscribed)
* Announce on apachecon slack (#general channel), and on the-asf slack #communityovercode and #comm-over-code-eu

Call for Tracks Draft
------------------------------------------------------------------------------
 
It's back *and* it's new!
We're excited to announce that the first edition of Community over Code Europe (formerly known as ApacheCon EU) will be held at the Radisson Blu Carlton Hotel in Bratislava, Slovenia from June 03-05, 2024!
This eagerly anticipated event will be our first live EU conference since 2019.

We are eager to craft an exceptional experience for all attendees, and we're looking for your help.

As we plan the schedule of sessions, we are seeking input on what tracks to host for this year's live event.
Please note: this event is smaller in both time and space than Community over Code NA, and we'll need to be judicious in selecting a program with something for everyone.
There will be approximately 90 slots available for presentations.

To kickstart this process, we are issuing a general Call for Tracks. If you have a compelling proposal for a track at Community over Code EU 2024, please respond to this email with the following information:

* Name of track
* Short description of the track
* Track captain name(s)
* Expected number of sessions for your track
* Optional: ASF Project which might be interested in contributing presentations for your track

Track leads are responsible for promoting the CFP for their tracks, selecting presentations and working as part of the program committee to coordinate the schedule.
Given the constraints, it's likely that we will need to merge tracks and adjust the number of sessions per track.
Your help in making these decisions is highly valued; please don't hesitate to join the discussion on planners@apachecon.com.

Track selection will be based on:

* Past attendance and interest
* Track lead experience and expertise
* Relevance to new technologies and approaches

Please have this information to planners@apachecon.com by 1970/01/18 at 23h59 UTC, so we can begin the selection!

Additionally, we are thrilled to introduce a new feature this year: a poster session.
This addition will provide an excellent platform for showcasing high-level projects and incubator initiatives in a visually engaging manner.
We believe this will foster lively discussions and facilitate networking opportunities among participants.

Call for Presentations
============================================================================== 

Goals:

* **Fill the conference with useful, interesting talks that people want to see**
* Provide opportunities for new speakers, in an welcoming, inclusive environment.

Call for Presentations Draft
------------------------------------------------------------------------------
 
Yo send us talks thx 

Resources
==============================================================================

* ASF
  - [announce@apachecon.com](https://lists.apache.org/list?announce@apachecon.com)
  - [planners@apachecon.com](https://lists.apache.org/list?planners@apachecon.com)
  - [@TheASF](https://twitter.com/TheASF)
  - [ASF Event Planning](https://cwiki.apache.org/confluence/display/CONFERENCES/Apache+Event+Planning)

* General
  - [Advice for Program Chairs][ProgramCommitteeAdvice]
  - [The role of program committees][ProgramCommitteeRole]
  - [Running a program committee meeting][ProgramCommitteeMeeting]

[ProgramCommitteeAdvice]: https://theory.stanford.edu/~aiken/publications/trs/ProgramChair.pdf "Advice for Program Chairs (PDF)"
[ProgramCommitteeRole]: https://www.wisdom.weizmann.ac.il/~oded/on-pc.html "The role of program committees"
[ProgramCommitteeMeeting]: https://homes.cs.washington.edu/~mernst/advice/pc-meeting.html "Running a program committee meeting" See https://github.com/apache/apachecon-eu/wiki/Program-committee-playbook