Dear Wiki user,

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

The following page has been changed by Rudolf Korhummel:
http://wiki.apache.org/lenya/MeetingFreiburg2007

------------------------------------------------------------------------------
  During the sucessful developer and user meeting in Zürich there was the idea 
to have a second meeting this year at the Albert Ludwig University Medical 
Center Freiburg [http://www.uniklinik-freiburg.de].
  
  Date: '''Monday, Oktober 29 to Wednesday, Oktober 31 2007'''
+ 
+ 
[http://maps.google.de/maps/ms?oe=UTF-8&hl=de&ie=UTF8&t=h&om=1&msa=0&msid=110149293182005781717.00043cae423b4060bbfa9&ll=47.998573,7.844346&spn=0.005607,0.010257&z=17
 Location of the meeting and hotel information.]
  
  == Current List of Participants ==
  Sign up here if you can make it to Freiburg:
@@ -17, +19 @@

   * JannForrer (arriving on Monday evening or Tuesday morning).
   * JürgenRagaller
  
- We can have a talk about our experiences in Freiburg with the migration of 
our webseite to lenya.
+ 
  
  This is an early draft. Feel free to add other topics of interests here:
  
@@ -25, +27 @@

   * Problems and solutions
    * Review and clean up the (few) remaining bugzilla issues
    * 2.0-dev concurrency testing as a group, using the zones-server default 
publication
-   * locking - discuss possible improvements 
+   * locking - discuss possible improvements
+   * Migration of lenya 1.2.x to 2.0 
   
  === Schedule ===
  
  === Talks / Presentations ===
   * Jürgen Ragaller - Using xi:include or cinclude to mix user data and 
dynamic data blocks (e.g. a database query) inside the editable area - and make 
shure the include statement survives the editing process.
+  * Rudolf Korhummel - Experiences made with the migration of our website to 
lenya. (www.uniklinik-freiburg.de)
  

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to