While I'm finishing a couple of sites here (having some Mozilla challenges atm) I have been a bit neglectful responding to all my email because I just have, and will be spending this weekend answering heaps of them, so if you're feeling neglected, you're not singled out. It's again, be a bit overwhelming managing email, my servers, responding to forum issues, finishing jobs, configuring my next server, working out how to migrate from one to another... and attending to some other DotNetNuke core team roles that have been assigned in the last few days.

Overall I've seen that people are coming back to work, some of the core team members have been called to do work that puts them out of the picture for some time, wheras some haven't come back yet, and I expect that next week they'll be back in full force.

I have seen builds coming through addressing some of  the bugs and it's been a little bit fiddly because there have been different decisions made in the resolution.  Fortunately, from my perception (and only mine based on the fact I'm not a coding person) there has been no inference to anything regarded as *code breaking* which means for the current developers converting their modules to 3, it's good news you can keep forging ahead.

The upgrading path has been the biggest challenge lately with many changes that are bigger than those who moved from dnn1 to dnn2, and I suppose this is simply shifting DotNetNuke into another dynamic area of growth. 

I've had a look on the 30 for 3 website there is alot of activity, mostly question changes between 3.07 and 3.08 and some persistent areas being nutted out.  It's good to see a collaboartive group of developers who are sharing their knowledge as best as they can, considering we have a wide range of mulit lingual talent now who are frequently assisting and showing by examples/solutions just how powerful the DotNetNuke open source environment is.

Some of the areas of great interest are the optimising of sites to make them run faster, and while I note a few forum comments have been to remove some of the not needed modules, etc, it makes me wonder if that crosses over into the design aspect.  I've been reading up on design theory, website usablity, and to a certain extent, ergonomics and how we naturally do things and see there is bridge to cross when designing within DotNetNuke environment.

I'm still convinced that DNN is rigid and fixed, with lots of rules, but still gives an enormous amount of scope to work within and each day, I'm learning something new, and yesterday was happy to learn more about the ability to display container site wide, by incorporating them into the ascx file. This is an extremely good design element to learn and will make that one of the new things to learn for DNN3, although I'm using for DNN2 as well.

So, it's just around lunchtime today and I'm hoping to make another post today now that I've nearly finished these projects for patient people.  My goal is to have my new site and my skinning resource site live and running for next week packed with many months of ideas and new directions for 2005.

Thanks for  dropping in.. I like this time putting my thoughts down somewhere.  It's like thinking out loud sometimes and I do go back and review what I write to help keep me on track.. You should all get stuck into having some blogs/online thinking areas...

Nina Meiers