This is completely unedited as I'm running off the the next session!
Well, that's what you get for showing up late. Us Engage guys are sitting in the very front row of Shaun's keynote. Hopefully my neck hold's up to the strain of looking straight up for the next hour and a half.
Joe opens up the keynote and introduces Shaun. Shaun will be covering the overview, progress and what the corporation is and will be providing to the community, as well as the long term vision.
While most people in the room are probably fairly well versed in the project/platform Shaun is doing a quick overview of what DNN is and what it provides.
Some project specs: Largest opensource project on MS platform, active community support forum, 200 vendors of modules and skins. Large support from volunteer core and project teams from around the world.
Progress:
150k downloads/month
500k users, 500k user registered within the last hour
Registrations from over 250 countries
Number of awards and recognition within media and community programs.
30% annual growth rate of the user base
4 million downloads to date 40% annual growth in the number of downloads. 400k downloads per quarter
Page views, over 9million page views on DotNetNuke.com per quarter
Visual Studio Magazine editor's choice award
Info-Tech
InfoWorld rated DNN "very good" with a 8.4 out of 10
Releases:
averaging 1 release every 4 months
56 Public releases
11 Major Releases
4.7 released today available for DotNetNuke.com
Stewardship of the project by DotNetNuke Corp.
Goal to provided services, dedicated resources, protect intellectual property of the project, promotion of the brand, manage infrastructure, funding product development, developing/managing business relationships.
Values: Brand is the most valuable asset. Open source license is the key to the growth, BSD license allow for significant growth. Creating opportunities to succeed allows the project/corp to succeed. Community support allows the community to continue support back to the project. Personal honest and integrity is the foundation of the projects success.
Funding: DNN Corp. has invested over $500k in the development and growth of DNN to date.
Current and future funding sources: (primary sources) Advertising & Sponsorship, Private Equity Investment, Strategic Services, Commercial Products for Emerging Markets. (Secondary sources) Benefactor Program, Marketplace.
Strategic Services:
DNN Subscription Program, SLA Based Technical support for Business Users, provided by Core Team Experts. Eliminates risk around the product with the use of Open Source software for business. for more info check out www.dotnetnukecorp.com
Business partners: Vital for continued growth of the ecosystem. Partner program coming soon, possibly November, will formalize relationships with the Corp and Commercial Partners, create official recognition system
Introduction of business partners, first Microsoft via the Windows LiveID platform, Koji Kato. Demonstration from Windows Live team. Hotmail, ID, Messenger Search, Spaces, the list got very huge I'm not going to try to write them all down, there must be 30 items on the list :)
MS is in the process of evolving the platform into a developer platform, allowing for developers to utilize the services that MS provides. Live platform provides a simple and consistent terms of use, threshold that allows developers to use the services for free, and what you have to cover if you go over that threshold.
Demo in VS of DNN running Windows LiveId authentication, login with Koji's login with LiveID. In VS Koji adds a DNN module, that will allow you to integration with Live services, Windows Live Tools, contacts control, installs this on a control and executes the site, will add the module definition for this new module. I'm actually impressed, I don't know Koji but he seems to be very well versed in DNN so far with adding a module and definition. He's logged back in with his Windows LiveId, this new control allows him to add a list of contacts from his LIveID account, basically a windows live messenger look and feel, allowing the control to show who is online with Live Messenger.
Control allows creating a new Live message that includes the URL that is sent out, this basically allows users to send easy links to their MSN contacts list. This is a pretty sweet control, now to figure out where this control is so I can start writing some modules to use this.
Live tools has a lot of announcements, CTP of Windows Live Tools for VS. IM control publicly available, contoso ISV Windows Live Quick app, Windows Live SPaces Photo API, more Windows Live sessions on Thursday, I may have to attend some of these.
Koji has handed control back to Shaun. Shaun is now talking about aspdotnetstorefront as a vendor providing their products as DNN modules and available for purchase.
C4
C4 runs the AFL and NRL websites in Australia, which reach 40% of all australian internet users. 2.5 million unique users/month, 500k sessions per day peak, 50k sessions/hour peak. 60k HTTP connections simultaneous. Richar Gellis and Pete Diemert of C4 introduced and taking up on stage.
NRL site is not yet publicly launched, AFL site launches in February. Why C4 chose DNN, Free, Great License, .NET. They new if that if DNN couldn't scale they would be able to scale it themselves, as opposed to proprietary systems that they wouldn't be able to get into code.
Top 10 scalability issues they had with AFL2007. SQL cluster, 4 zeon processors in each 16gb ram, file servers clustered, 12 frontend web servers. F5 load balancer with a firewall, georedundant, duplicated in 2 data centers. Load simulators with 100mb pipe for testing, saturated the pipe and the sites stayed up.
10. DNN Application, a few file based caching issues, not too many issues. 9. Firewalls 8. Load Balancers 7.IIS Servers 6. Network Saturday (if firewall is 1gb that gives you roughly 300mb throughput 5. File server bottlenecks 4. SQL Throughput (25 terrabytes of data on high weekends) 3. SQL XML Explicit "bug" read from a DB can turn into a write 2. SAN disk trhoughput 1. Stupidity, tripping over cables, resetting app in web.config, random bad things you shouldn't do with any application. Overview, DNN was the least of their problems from Scalability.
DNN scales, more often than not it's infrastructure.
Vision
Adapt to the emerging needs of developers, business users, and consumers. Increase adoption of platform. Identify technology/social/business trends.
Trends: Technology - User generated content, Social Networking, Rich User Experience, Search and Syndication
Social- Always online, pervasive communication, participation, broadband
Business- Global economics, Mainstream Tech Adoption, Commodization, Data Collection
In context - Project needs to evolve to keep up with technology and needs.
530 million years ago, evolution explosion occurred, rate of evo accellerated by order of magnitude (Cambrian Period)
DotNetNuke Cambrian (DNN 5.0)
Make DNN the world's foremost platform for creation of contemporary, socially enabled, collabrative, etc.
- Widget Platforms
- Workflow
- Core Module Suites
- Dynamic Localization
- Admin UI Skinning/engine
Social Networking
Api to provider networking, rating, bookmarks, shared media, should feed external widgets, live, google, mac, facebook widgets. Host third party widgets, mashups, within DNN
Workflow
Simple and advanced scenarios, approval process, approval chains, interportal workflows between staging and production environment. Content versioning
Core Module Suites
Quality and meeting user expectations for product package. Increase complexity of modules well suited for usiness usage. CMS based modules, Social Networking Suite of modules
Localization
30% of registered userbase is in USA. Complete localization story, need to create abililty to dynamically localize full content. Workflow integration. Localized search and indexing capabilities. Complete internationalization support
User Experience
Improved UE, ability to do more with less clicks, admin side of things. More contemporary UI, easier to work with. Improved skinning engine.
Timeline
Last major 4.x release will be VS2008 IIS7 compatibility. Not all cambrian will be at once, iterative steps to provide continuos value and minimize risk.
Cambrian first-look 01/08, first production release in Q1 2008. Fully implemented by Q4 2008
Thanks to the sponsors, Texas Insturments (video taping services), Active Modules, R2i, (bi4orce).
Taking Questions:
How well does the implementation with AD work today. 4.6 overhaul of authentication providers. AD has been reimplemented.
Do you have any idea of what the migration path will be from 4-Cambrian: Goal is to maintain backwards compatability, in general always strive for a seamless migration path. 1.0 to 4.6 will upgrade now.
Will there be UI designers on the Core Module teams: Yes, the goal is to have UI input on all of the core modules and project.
Wow, that was a lot of info! If you're reading this my battery must of survived and I've gotten online.