DUE TO SPAM, SIGN-UP IS DISABLED. Goto Selfserve wiki signup and request an account.
| Wiki Markup |
|---|
h2. Track Title
Project Management Committee:
Subprojects covered by Track:
PMC |
#format wiki
#language en
#pragma section-numbers off
#acl ConcomGroup:read,write,revert,admin,delete ProducerGroup:read,write ApacheMembersGroup:read,write +All:read
== Track Title ==
Project Management Committee:
Subprojects covered by Track:
...
Liason/Spokesorganizer(s): |
...
Planning Team Mentor & Liason: |
...
=== Track Description ===
- Must be suitable for program, one paragraph, identify Who, What and Why.
- This must be oriented towards the technologist familiar with this subject
- matter, one who is not yet familiar but would be interested if they knew
- what the technology was, and the decision maker who would approve their
- attending this conference!
##
=== Target Audience ===
- This is for the planners use and marketing
##
- This is for the planners use and marketing
- Please list companies who might be interested in sponsoring this content,
- and include contact name and email, if known, for Delia to contact them
##
##
== Proposed Schedule ==
- Your mentor will come in and insert any applicable trainings
09:00 - 10:00 | REGISTRATION |
|---|---|
10:00 - 10:50 | Session 1 |
10:50 - 11:15 | BREAK |
11:15 - 12:05 | Session 2 |
12:05 - 13:30 | LUNCH |
13:30 - 14:20 | KEYNOTE |
14:30 - 15:20 | Session 3 |
15:20 - 16:00 | BREAK |
16:00 - 16:50 | Session 4 |
17:00 - 17:50 | Session 5 |
18:00 | END OF PROGRAM |
- Do not change capitalized items! These are part of the master schedule.
- The individual Session time blocks may be re-sliced, but remember that
- only five speakers per full day of content receive any speaker benefit.
##
- Each session must be commercially attractive to the audience identified,
- if content doesn't "fit" into this track but is interesting or useful,
- consider an Additional Event, below
##
- This must be completed in June, site opens on the 22nd.
=== Session Title ===
Session Code:
Speaker:
- Include title, company affiliation, and note email here as a comment
Session Description
- Must be suitable for program, one paragraph, identify Who, What and Why,
- note the requirements under the Track description, above.
##
Target Audience
- For planners use, only if different than the main track
##
- For planners use, only if different than the main track
- Please list rejected sessions (by session code only), these submittors
- will be extended courtesies/discounts for their effort:
##
##
== Additional Events ==
- Small-room (max 50) day of content? No speaker compensation is attached
- to such events. Attendees must be registered/paid for the conference.
- It can be organized as an unconference or other structure, or it can have
- a partially or fully spelled out program. The first deadline to request
- this is the end of June, with no deadline yet for its content.
- Evening Meetup/BOF's/Other? No speaker compensation is attached to such
- events, they are free to the public. The first deadline to request
- this is the end of July, with no deadline yet for its content.
== Questions and Answers ==
...
h3. Track Description
{HTMLComment:hidden}
## Must be suitable for program, one paragraph, identify Who, What and Why.
## This must be oriented towards the technologist familiar with this subject
## matter, one who is not yet familiar but would be interested if they knew
## what the technology was, and the decision maker who would approve their
## attending this conference!
##
{HTMLComment}
h3. Target Audience
{HTMLComment:hidden}
## This audience information is for the planners use and marketing
##
## Please list companies who might be interested in sponsoring this content,
## and include contact name and email, if known, for Delia to contact them
##
{HTMLComment}
h2. Proposed Schedule
{HTMLComment:hidden}
## Your mentor will come in and insert any applicable trainings
{HTMLComment}
| 09:00 - 10:00 | REGISTRATION |
| 10:00 - 10:50 | Session 1 |
| 10:50 - 11:15 | BREAK |
| 11:15 - 12:05 | Session 2 |
| 12:05 - 13:30 | LUNCH |
| 13:30 - 14:20 | KEYNOTE |
| 14:30 - 15:20 | Session 3 |
| 15:20 - 16:00 | BREAK |
| 16:00 - 16:50 | Session 4 |
| 17:00 - 17:50 | Session 5 |
| 18:00 | END OF PROGRAM |
{HTMLComment:hidden}
## Do not change capitalized items! These are part of the master schedule.
## The individual Session time blocks may be re-sliced, but remember that
## only five speakers per full day of content receive any speaker benefit.
##
## Each session must be commercially attractive to the audience identified,
## if content doesn't "fit" into this track but is interesting or useful,
## consider an Additional Event, below
##
## This must be completed in June, site opens on the 22nd.
{HTMLComment}
h3. Session Title
Session Code:
{HTMLComment:hidden}
## [Original from CMS, even if it will be revised, or leave blank if not entered]
{HTMLComment}
Speaker:
{HTMLComment:hidden}
## Include title, company affiliation, and note [email] here as a comment
{HTMLComment}
_Session Description_
{HTMLComment:hidden}
## Must be suitable for program, one paragraph, identify Who, What and Why,
## note the requirements under the Track description, above.
##
{HTMLComment}
_Target Audience_
{HTMLComment:hidden}
## For planners use, only if different than the main track
##
{HTMLComment}
{HTMLComment:hidden}
## Please list rejected sessions (by session code only), these submittors
## will be extended courtesies/discounts for their effort:
##
##
{HTMLComment}
h2. Additional Events
{HTMLComment:hidden}
## Small-room (max 50) day of content? No speaker compensation is attached
## to such events. Attendees must be registered/paid for the conference.
## It can be organized as an unconference or other structure, or it can have
## a partially or fully spelled out program. The first deadline to request
## this is the end of June, with no deadline yet for its content.
## Evening Meetup/BOF's/Other? No speaker compensation is attached to such
## events, they are free to the public. The first deadline to request
## this is the end of July, with no deadline yet for its content.
{HTMLComment}
h2. Questions and Answers
|