Ah, the joy and pain of being a Lotusphere track manager.

For Lotusphere 2006, over 200 proposals for sessions were received in the infrastructure track (the IDXXX sessions).  Over the last few weeks, that was whittled down to the 50 sessions we'll have as that track at the conference.  This morning, the selections are 90%+ final.  My colleagues managing the other tracks are at or close to the same point as well.

We've promised several times that Lotusphere 2006 will continue the tenets established over the last couple of years -- deeper and deeper technical content, along with more focus on sessions with here-and-now value.  We can't be successful with this conference if it gets too far ahead of those of you who might attend -- a session on deploying "Hannover" in a Notes 7 environment might sound gee whiz cool, but nobody is going to do that until "Hannover" ships...so why talk about it in depth now?

The session titles and preference voting should be pushed out to the web within a week to ten days.  I hope that detail will help more of you justify spending your company's budget on Lotusphere '06.

Also, Chris Miller reports that a few of the Lotusphere hotels are waitlist only, though talk on the Turtle's unofficial site says to check out some of the various dates -- some have more availability than others depending on the day.

Post a Comment

  1. 1  l larsson  |

    I would like to see a session called "advanced Domino development strategies". Today Domino lacks many of the "obvious" stuff that MS or JAVA has (versioning, check in/out). Im kind of interested how other solved this stuff especially in large oragnisations with many developers.

    Did i mention background-agent clustering - not fun at all? (ought to be native in Domino and easy to use)

    /LL

  1. 2  Chris Whisonant http://cwhisonant.blogspot.com |

    Versioning? That's basically what templates are for. You have a live template and a dev template. Each is a different version and then once you've tested you just roll up the live databases to the next template/version.

  1. 3  l larsson  |

    The template is fine for small sites that include small numer of databases, but the template-think isnt enough when you have 60+ databases and 10 sites to develop and maintain.

    One other issue with templates is that you cant see the dependencies in a simple way.

    I've seen demos of Teamstudios products CIAO, which is good but there must be other products or?

  1. 4  Ed Brill www.edbrill.com |

    L. Larsson -- Please use a valid e-mail address.

  1. 5  R. J. Lesch  |

    L Larsson writes: "One other issue with templates is that you cant see the dependencies in a simple way."

    I added a view to my Domain Catalog, "Databases/By Template Inheritance" to show this. First column (categorized) has the formula "@Trim(DbInheritTemplateName:DbTemplateName)". Works reasonably well for my purposes. I'm sure someone could come up with something juicier.

  1. 6  Dave http://www.weblayouts.net |

    MS has versioning and check-in/out built in? Really? Wow. I work in an MS shop, and apparently we are wasting our money on the 3rd party products that we need to do that.

    Yes, it would be lovely if Domino did all that. But the competitors don't do it either.