jackrabbit-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Jackrabbit Wiki] Trivial Update of "ContentTrackApacheConUs2009" by JukkaZitting
Date Wed, 15 Jul 2009 17:44:25 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jackrabbit Wiki" for change notification.

The following page has been changed by JukkaZitting:
http://wiki.apache.org/jackrabbit/ContentTrackApacheConUs2009

The comment on the change is:
Formatting

------------------------------------------------------------------------------
  
  == Additional Events ==
  
-   * !NoSQL meetup
+   * NoSQL meetup
    * "Tapestry vs. Wicket deathmatch"
    * individual project BoFs, based on demand
  
@@ -224, +224 @@

  
  Presentation, 50 minutes by J. Chris Anderson, Thursday 16:00 - 16:50
  
-  This presentation takes a look at !CouchDB from 10,000 ft.
+  This presentation takes a look at CouchDB from 10,000 ft.
   We try not to lose you in technical details and paint the big picture
-  that you need to understand !CouchDB's strengths and weaknesses.
+  that you need to understand CouchDB's strengths and weaknesses.
  
-  !CouchDB is a document oriented database.  It does not adhere
+  CouchDB is a document oriented database.  It does not adhere
   to the relational principles of traditional databases.
   You will learn what that means for your application design.
  
-  !CouchDB's replication support solves the problems of high-traffic
+  CouchDB's replication support solves the problems of high-traffic
   web sites, distributed peer-to-peer, and offline applications
   all at the same time.  We show you what kind of applications you
   are able to build with that.
  
-  However, !CouchDB is no Silver Bullet and there are cases where it
+  However, CouchDB is no Silver Bullet and there are cases where it
   is a poor fit.  You will learn to decide when to use it for your
   project and when you are better off with a different solution.
  
@@ -281, +281 @@

  
  SUGGESTIONS
  
- * People pay to see the scheduled content at !ApacheCon. Provide material which will reach
and attract our paying audience. If you have Geeks for Geeks content to present, please save
that for the daytime un-con tracks, or evening !MeetUps/BOFs. Consider that people attending
the main tracks probably need to have a clear business case for registration costs - but your
community are free to attend the free evening programming (and that's free as in beer!), so
choose appropriately!
+  * People pay to see the scheduled content at !ApacheCon. Provide material which will reach
and attract our paying audience. If you have Geeks for Geeks content to present, please save
that for the daytime un-con tracks, or evening !MeetUps/BOFs. Consider that people attending
the main tracks probably need to have a clear business case for registration costs - but your
community are free to attend the free evening programming (and that's free as in beer!), so
choose appropriately!
  
- * Work with your community. Some of the best presentations have been from presenters who
don't belong to that project's PMC.
+  * Work with your community. Some of the best presentations have been from presenters who
don't belong to that project's PMC.
  
- * Be creative! You're not limited to the strict 50-minute-sessions model. You can organize
the schedule in whatever way makes the most sense for your project's content. (Ensure that
your attendees still get their coffee- and lunch-breaks and keynote sessions.)
+  * Be creative! You're not limited to the strict 50-minute-sessions model. You can organize
the schedule in whatever way makes the most sense for your project's content. (Ensure that
your attendees still get their coffee- and lunch-breaks and keynote sessions.)
  
- * The main track drives paid attendence, so you must submit well-written proposals. If the
proposals are not clearly written, and answer "Who, What, and Why?", then what can be expected
of the presentations? We've reviewed the proposals that were received in the main CFP, and
they accompany this email. You can use these verbatim (appropriately edited for spelling/to
fit the program!), or work with the submitters to refine them to work better within the track
you're planning and/or solicit completely new proposals. Use whichever solution creates the
most effective program.
+  * The main track drives paid attendence, so you must submit well-written proposals. If
the proposals are not clearly written, and answer "Who, What, and Why?", then what can be
expected of the presentations? We've reviewed the proposals that were received in the main
CFP, and they accompany this email. You can use these verbatim (appropriately edited for spelling/to
fit the program!), or work with the submitters to refine them to work better within the track
you're planning and/or solicit completely new proposals. Use whichever solution creates the
most effective program.
  
- * During the day, we will run un-con tracks on Wednesday through Friday in smaller rooms
(capacity ~50), also coordinated by PMCs. They do not need to be formalized until the morning
of the track, but guidance for the prospective audience can be gathered on the un-con tracks'
wiki pages. Registration will be required to attend these parallel tracks, but they're a great
place to schedule the Geeks4Geeks content that's really interesting for a narrower audience.
+  * During the day, we will run un-con tracks on Wednesday through Friday in smaller rooms
(capacity ~50), also coordinated by PMCs. They do not need to be formalized until the morning
of the track, but guidance for the prospective audience can be gathered on the un-con tracks'
wiki pages. Registration will be required to attend these parallel tracks, but they're a great
place to schedule the Geeks4Geeks content that's really interesting for a narrower audience.
  
  FREE STUFF!
  

Mime
View raw message