Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 4.0

...

Track

...

Title

...

Project

...

Management

...

Committee:

...

Subprojects

...

covered

...

by

...

Track:

...

PMC

...

Liason/Spokesorganizer(s):

...

Planning

...

Team

...

Mentor

...

&

...

Liason:

...

Track

...

Description

Wiki Markup
{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}

Target Audience

Wiki Markup
{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}

Proposed Schedule

Wiki Markup
{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

Wiki Markup
{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}

Session Title

Session Code:

Wiki Markup
{htmlcomment:hidden}
## [Original from CMS, even if it will be revised, or leave blank if not entered]
{

...

htmlcomment}

...

Speaker:

...


Wiki Markup
{htmlcomment:hidden}
## Include title, company affiliation, and note [email] here as a comment
{

...

htmlcomment}

...

Session

...

Description

Wiki Markup
{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

Wiki Markup
{htmlcomment:hidden}
## For planners use, only if different than the main track
##
{

...

htmlcomment}

Wiki Markup
{htmlcomment:hidden}
## Please list rejected sessions (by session code only), these submittors
## will be extended courtesies/discounts for their effort:
##
##
{

...

htmlcomment}

Additional Events

Wiki Markup
{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}

Questions and Answers