Outline Development Deadline August 5th

[Tim Cunningham]

We are now moving to the Outline Review Phase as outlined in out Speaker / Topic Selection Process Thread.

Outline Review

• Speakers should develop an outline of points they will cover and submit to the content committee for review
  
• Speakers should also develop prerequisites required for their topic.
  
• If their topic is an advanced topic that builds on another topic or has prerequisites that are covered in a prior talk those speakers should collaborate to ensure there are no gaps in coverage or too much overlap.
  

What we expect from yoru outline

Please post to your Trello Card that you are assigned to 10 to 15 bullet points of what you will be covering in your talk.  If there are any points that are not public knowledge yet, leave them off the card but please repost it here to this group.  Your outline will help the content committee make sure that we have good coverage of material with out much gap or overlap.  Also if we decide to publish the points on the schedule it can help the audience choose which sessions best fit their needs.

Deadline to have this done is August 5th

Thanks,

Tim

PS. Below is the Process we are following:

Speaker / Topic Selection Process (6 & 7 have been reversed from the original thread)

1. Survey
• Use the Trello board to collect topic ideas & popularity. 
  
2. Targeted Invitation
• Invite ColdFusion community / Adobe members to comment on which of the Surveyed topics they would be will to develop.
• Assign a potential speaker to the topic card on the trello board
3. Topic Selection
• Choose which topics will be part of the CFSummit this year.
4. Open Invitation (optional)
• If we do not have speakers from the Targeted Invitation put the remaining topics up for public comment
  
• Invite speakers to pitch why they could present on the topics
5. Speaker Selection
• Content committee will finalize the speakers selected for the topics
• Send speaker agreement form to speakers
6. Title Review
• Speakers should submit their final title for content committee review
7. Outline Review
• Speakers should develop an outline of points they will cover and submit to the content committee for review
• Speakers should also develop prerequisites required for their topic.
• If their topic is an advanced topic that builds on another topic or has prerequisites that are covered in a prior talk those speakers should collaborate to ensure there are no gaps in coverage or too much overlap.
8. Slide collection
• Just prior to the CFSummit finalized slides will be collected for sharing and distribution after topic delivery.
• Speakers are responsible for the final content of their slides and delivery.
• Content Committee may review the slides if they wish, but this is not required (and is way too much work to do properly.)
9. Conference and Speaker Survey review (After the conference)
• There should be a speaker survey available online where people can score the quality of the topic and the presentation
• There should also be a conference survey
• Committee should review both of these to determine areas of improvement

[Charlie Arehart]

For any who missed it, today was the deadline to get our outlines posted on the trello board card (s) for our talk(s).

Tim/team, I did mine, on “What’s new and different about Tomcat on CF10”. I put the outline in the “description”. Was that the right place?

/charlie

 

From: cfsummit...@googlegroups.com [mailto:cfsummit...@googlegroups.com] On Behalf Of Tim Cunningham
Sent: Tuesday, July 23, 2013 5:27 PM
To: cfsummit...@googlegroups.com
Subject: [cfsummit-speakers] Outline Development Deadline August 5th

 

We are now moving to the Outline Review Phase as outlined in out Speaker / Topic Selection Process Thread.

 

Outline Review

• Speakers should develop an outline of points they will cover and submit to the content committee for review
• Speakers should also develop prerequisites required for their topic.
• If their topic is an advanced topic that builds on another topic or has prerequisites that are covered in a prior talk those speakers should collaborate to ensure there are no gaps in coverage or too much overlap.

 

What we expect from yoru outline

 

Please post to your Trello Card that you are assigned to 10 to 15 bullet points of what you will be covering in your talk.  If there are any points that are not public knowledge yet, leave them off the card but please repost it here to this group.  Your outline will help the content committee make sure that we have good coverage of material with out much gap or overlap.  Also if we decide to publish the points on the schedule it can help the audience choose which sessions best fit their needs.

 

Deadline to have this done is August 5th

 

Thanks,

 

Tim

 

 

 

PS. Below is the Process we are following:

 

Speaker / Topic Selection Process (6 & 7 have been reversed from the original thread)

 

1.     Survey

o Use the Trello board to collect topic ideas & popularity. 

2.     Targeted Invitation

o Invite ColdFusion community / Adobe members to comment on which of the Surveyed topics they would be will to develop.

o Assign a potential speaker to the topic card on the trello board

3.     Topic Selection

o Choose which topics will be part of the CFSummit this year.

4.     Open Invitation (optional)

o If we do not have speakers from the Targeted Invitation put the remaining topics up for public comment

o Invite speakers to pitch why they could present on the topics

5.     Speaker Selection

o Content committee will finalize the speakers selected for the topics

o Send speaker agreement form to speakers

6.      Title Review

o Speakers should submit their final title for content committee review

7.     Outline Review

o Speakers should develop an outline of points they will cover and submit to the content committee for review

o Speakers should also develop prerequisites required for their topic.

o If their topic is an advanced topic that builds on another topic or has prerequisites that are covered in a prior talk those speakers should collaborate to ensure there are no gaps in coverage or too much overlap.

8.     Slide collection

o Just prior to the CFSummit finalized slides will be collected for sharing and distribution after topic delivery.

o Speakers are responsible for the final content of their slides and delivery.

o Content Committee may review the slides if they wish, but this is not required (and is way too much work to do properly.)

9.     Conference and Speaker Survey review (After the conference)

o There should be a speaker survey available online where people can score the quality of the topic and the presentation

o There should also be a conference survey

o Committee should review both of these to determine areas of improvement

--
You received this message because you are subscribed to the Google Groups "CFSummit Speakers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cfsummit-speak...@googlegroups.com.
To post to this group, send email to cfsummit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

[Jason Dean]

Yes.

Jason

[Scott Stroz]

I hate to say this, but the formatting available on Trello is not really a good fit for 'outlines'

Any suggestions?

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

--

[Dave Ferguson]

Make sure you have a space after the hyphen to create a bullet for a list.  Also, put spaces before the hyphen to create indent.

====================
= Dave Ferguson
====================
= http://blog.dkferguson.com
= http://www.cfhour.com
= http://twitter.com/dfgrumpy
= Adobe Community Professional
====================

[Raymond Camden]

I'm updating my session to be: "Using Trello."

===========================================================================
Raymond Camden, Adobe Developer Evangelist

Email : raymon...@gmail.com
Blog : www.raymondcamden.com
Twitter: cfjedimaster

[Scott Stroz]

I think we need more than one session for that.

Maybe this is a case of using the wrong tool?

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Jason Dean]

Just do a modern-day outline.  We call them bullet lists now. 

Jason

[Scott Stroz]

Trying to do an nested bullet list. Seems I cannot go further than 2 levels.

That is awesome.

And by 'awesome', I mean, 'not awesome'

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Dave Ferguson]

I would tell you to read the documentation on the markup syntax but it is total shit.  They need to get Luis to rewrite it for them.

====================
= Dave Ferguson
====================
= http://blog.dkferguson.com
= http://www.cfhour.com
= http://twitter.com/dfgrumpy
= Adobe Community Professional
====================

[Scott Stroz]

I did read the documentation.

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Dan Wilson]

I think we are just looking for 10-15 bullet points. Summarize at a high level and it'll be fine.


DW

Scott Stroz

Tuesday, August 06, 2013 10:47 AM

Trying to do an nested bullet list. Seems I cannot go further than 2 levels.

That is awesome.

And by 'awesome', I mean, 'not awesome'

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

--
You received this message because you are subscribed to the Google Groups "CFSummit Speakers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cfsummit-speak...@googlegroups.com.
To post to this group, send email to cfsummit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Jason Dean

Tuesday, August 06, 2013 10:35 AM

Just do a modern-day outline.  We call them bullet lists now. 

Jason

--
You received this message because you are subscribed to the Google Groups "CFSummit Speakers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cfsummit-speak...@googlegroups.com.
To post to this group, send email to cfsummit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Scott Stroz

Tuesday, August 06, 2013 10:21 AM

I hate to say this, but the formatting available on Trello is not really a good fit for 'outlines'

Any suggestions?

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

--
You received this message because you are subscribed to the Google Groups "CFSummit Speakers" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cfsummit-speak...@googlegroups.com.
To post to this group, send email to cfsummit...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Tim Cunningham

Tuesday, July 23, 2013 5:26 PM

[Raymond Camden]

Maybe you're over thinking this? I didn't think twice about making it fancy. I just did:

1) some shit

2) some shit

And was done. It looks like line breaks automatically format right. Can't you just write it?

[Scott Stroz]

One section of my outline is supposed to look like this:

1. Main point
1. sub point
1. sub sub point

Apparently, that is too complicated for Trello (or markdown)

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Scott Stroz]

45 minutes of my life I am never getting back........

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Raymond Camden]

As an audience member - I can tell you I'm not going to read an outline that deep. ;) IMO I'd keep it simpler. 

[Scott Stroz]

Well..Trello made it so it is 'simpler'. Problem solved...I guess

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Jason Dean]

Feel free to just add a link to your Google Doc if you are really that upset about it. 

Jason

[Tim Cunningham]

+1 Jason

[Scott Stroz]

I am not a fan of markdonw....took me much longer than it should have to even generate the link correctly.

Now, get off my lawn

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Tim Cunningham]

You sound like a COBOL programmer, Scott

[Scott Stroz]

Just give me some punch cards next time, will be easier on all of us.

Seriously, though, the markdown documentation on Trello is awful

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Scott Stroz]

Sorry if I am annoying/annoyed you guys. I have been having a shit time fixing an issue in an app at work and it sapped any patience I may have had to effectively deal with the stupidity that is markdown

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Raymond Camden]

I think some of us know about that issue (if it is the same one as the other listserv) and understand your frustration. :)

[Scott Stroz]

It is :D

Scott Stroz
http://www.boyzoid.com
--------------------------------------------------
No trees were killed in the sending of this message, but a large number of electrons were terribly inconvenienced

[Adam Tuttle]

Markdown is awesome. Scott is old. Unresolved bugs suck. Get off his lawn?

[Carol Hamilton]

Adobe has asked features of Thunder not be released on the conference site.  Below are the key points I am working on.  I have also added a description to the Trello board.  

·  Complete workflow for mobile application development 

o Mobile Project

o Code assist for Mobile specific APIs

o Support for debugging mobile applications running on device

o Support for inspecting DOM elements in mobile application (Weinre Integration)

o Integration with PhoneGap build for packaging mobile applications

·  Support for new language features of CF server

·  Editor Performance improvements (complete re-write, removal of Aptana editors)

·  Improved Debugging

Thanks,

Carol