New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

The Community Blog is a personal opinion of community members and by no means the official standpoint of DNN Corp or DNN Platform. This is a place to express personal thoughts about DNNPlatform, the community and its ecosystem. Do you have useful information that you would like to share with the DNN Community in a featured article or blog? If so, please contact .

The use of the Community Blog is covered by our Community Blog Guidelines - please read before commenting or posting.

Welcome Aboard!

DNN_Team Last year at OpenForce, DotNetNuke Corporation was on the verge of closing our first round of funding.  2006, 07 and 08 were challenging years as we struggled to find a business model that would support our company of 6 and allow us to grow.  Shaun, Scott, Nik and I formed DotNetNuke Corp. with the goal of building a company that would allow us to better manage the project and improve DotNetNuke with access to increased resources.  With the investment we received in 2008 we have been able to grow the company to nearly 30 employees and contractors.  As we have brought in additional employees, it has allowed us to further focus our efforts rather than running around trying to do everything ourselves.

One of our first people we hired after OpenForce last year was Cathal Connolly from the core team.  Cathal joined Charles Nurse who already worked for DotNetNuke Corp and brought his deep understanding of DotNetNuke security to the company.  At the same time we began to build out our engineering office in Abbotsford, British Columbia, Canada – not far from Vancouver.  We quickly hired Sarah Darkis and John Lucarino who both had prior experience working with Shaun and who also had extensive experience working with DotNetNuke and ASP.Net.  This was our engineering team for the better part of the first 9 months in 2009.

As sales of DotNetNuke Professional continued to grow, we were able to start a second round of hiring.  We brought in Ken Grierson this past summer. Ken is a senior test engineer, with many years of experience working as a tester at Microsoft.  He has worked hard to help us add more rigor to our testing and QA processes which is starting to pay off as we near our 5.2.0 release.  Ken has also started working with our community QA team to ensure that we are fully aligned with our QA efforts on the community side. 

Around this same time we were able to hire a network engineer.  What many people did not know is that this is a role that sort of fell in Scott Willhite’s lap several years ago.  Scott is not a network engineer, but has been able to keep the DotNetNuke infrastructure for both the project and the corporation running quite well over the past 7 years.  I am often amazed at how well he did, but know that it involved quite a few late nights and long weekends.  When we hired Konstantine Tcherenkov for the network engineering position in September, Scott was able to finally able to begin focusing on his primary responsibilities as Director of Community Relations.  Konstantine quickly came up to speed on our infrastructure and has already begun work on a restructuring of our servers and infrastructure to provide greater stability, redundancy and scalability for many of our critical systems.

Another recent addition to the engineering team is Chris Kendall who was hired to head up our support team.  If you are a Professional Edition customer, you have probably already had a chance to talk with Chris as he is managing our customer support for Professional and Elite customers.  This has been one part of my job over the last year, but a part I was quite happy to turn over to Chris.  Chris brings a passion for the job that is unbelievable and even without  a lot of DotNetNuke experience was able to jump in and begin making a huge difference from his very first week onboard the team. 

As everyone already knows, Shaun has also worn many hats during the first 7 years of DotNetNuke’s growth.  Like all of the founders, Shaun has been pulled in many different directions and desperately needed some additional help in engineering to manage our growing team.  We were very fortunate to be able to entice Rob Chartier to join DotNetNuke Corp as the Director of Engineering.  As an ASP.Net Insider, Microsoft MVP and longtime DotNetNuke user and evangelist, Rob was a natural fit for the position.  Rob’s brings his background in agile development practices to the engineering team and is using those skills as he heads up feature development for the community and commercial DotNetNuke editions.

With Rob onboard, I have formally taken on responsibility for the Quality, Support and Maintenance side of the engineering department.  I have the privilege of working with Ken, Chris, and Cathal to ensure we are putting out the best possible product.  We are focused on ensuring that we have a good grasp on all of the items that exist in Gemini for the DotNetNuke Core as well as Professional and Elite editions and will be working hard over the coming weeks to close them as quickly as possible, and putting the appropriate tests in place that they do not re-appear in future releases.

With the exception of Cathal, all of our engineering hires work from our Abbotsford office.  This is great for building team cohesion and simplifying communications.  Unfortunately, many of the great developers in the DotNetNuke community don’t live near Abbotsford.  With a solid core engineering team in place, I was happy to hear that were approved to make a few hires from outside the Abbotsford area.  Over the past couple of years Shaun and I had the opportunity to hear from a number of people in the community that they were interested in joining DotNetNuke Corp. whenever we had an opening.

Well, the day has finally come, where I am happy to say that we have hired two more members of the DotNetNuke Core team.  Both of the individuals have been working with DotNetNuke for many years and have a passion for the project that matches that of almost anybody in the community.  Shaun and I recognized that as capable as Ken, Chris, Cathal and I are, it is probably not enough to meet the goals we have for the quality and maintenance team.  We needed some additional people with a deep understanding of DotNetNuke who could immediately jump in and begin helping our support, quality and maintenance efforts on their first day.

I am happy to welcome aboard Phil Beadle to the DotNetNuke Corp. team.  As many of you already know, Phil was a founding member of the Core Team and was recently named a Trustee in our latest team re-organization.  Phil has worked for the past four years at Readify where he built up an impressive resume working on some very cutting edge DotNetNuke projects.  Phil was the lead architect of the Readify team working on the and sites, some of the largest public DotNetNuke sites anywhere in the world.  Like Rob, Phil also comes from an agile development background.  I am looking forward to working with Phil to use his knowledge to implement automated unit testing and improved continuous integration practices.  Phil is a great addition to our engineering team and I am looking forward to December 7th when he will officially begin work as a new member of the DotNetNuke Corp. engineering team.

The second core team member who has accepted a position with the engineering team is someone who may come as a surprise to many people.  I am happy to welcome Alex Shirley as our newest member of the support and quality team.  Anyone who frequents the forums or pays attention to our bug tracking system, knows that Alex has been a very dedicated member of the DotNetNuke QA team for the past several years.  As a core team member Alex has been a passionate advocate for improving the quality of our releases.  As the release manager for the past couple of years for the project, I often have the task of making sure we get releases out the door.  Even when Alex and I have disagreed on issues regarding the project releases, we both wanted what was best for the DotNetNuke project.  I love Alex’s passion and willingness to be a strong advocate for his position.  During his tenure on the core team he has kept the team focused on making sure that each release was the best possible version of DotNetNuke given the constraints that we often are forced to live with.  I look forward to working with Alex to help put in place additional processes to ensure that we are living up to his high quality standards.  Alex will also have the opportunity to work with Chris Kendall on the support team and to ensure that issues found by our customers are getting the appropriate attention from our maintenance team.

Our final hire is someone that Rob Chartier has worked with in the past, Keivan Beigi.  Keivan joins the Abbotsford/Vancouver team and helps round out the DotNetNuke development team with his real-world enterprise experience.  Recently, he has worked with many of the large US Telco providers, not to mention many of the Fortune 500 with the design, implementation, deployment and support of various projects focused around transaction processing.  It is in his enterprise experience we will gain the most value.

I am really excited at all the growth that has occurred on engineering team this year.  I look forward to continuing this trend in 2010 and further improving DotNetNuke.  This is an exciting time to be a member of the DotNetNuke Corporation engineering team and the DotNetNuke Community.  I can’t wait to sit at OpenForce 2010 and talk about all the great things we accomplished in 2010.

Technorati Tags: ,,


There are currently no comments, be the first to post one.

Comment Form

Only registered users may post comments.


Aderson Oliveira (22)
Alec Whittington (11)
Alessandra Davies (3)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (37)
Ben Schmidt (1)
Benjamin Hermann (25)
Benoit Sarton (9)
Beth Firebaugh (12)
Bill Walker (36)
Bob Kruger (5)
Bogdan Litescu (1)
Brian Dukes (2)
Brice Snow (1)
Bruce Chapman (20)
Bryan Andrews (1)
cathal connolly (55)
Charles Nurse (163)
Chris Hammond (213)
Chris Paterra (55)
Clint Patterson (108)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (181)
Daniel Valadas (48)
Dave Buckner (2)
David Poindexter (12)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (80)
Francisco Perez Andres (17)
Geoff Barlow (12)
George Alatrash (12)
Gifford Watkins (3)
Gilles Le Pigocher (3)
Ian Robinson (7)
Israel Martinez (17)
Jan Blomquist (2)
Jan Jonas (3)
Jaspreet Bhatia (1)
Jenni Merrifield (6)
Joe Brinkman (274)
John Mitchell (1)
Jon Henning (14)
Jonathan Sheely (4)
Jordan Coopersmith (1)
Joseph Craig (2)
Kan Ma (1)
Keivan Beigi (3)
Kelly Ford (4)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (2)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (40)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (1)
Patricio F. Salinas (1)
Patrick Ryan (1)
Peter Donker (54)
Philip Beadle (135)
Philipp Becker (4)
Richard Dumas (22)
Robert J Collins (5)
Roger Selwyn (8)
Ruben Lopez (1)
Ryan Martinez (1)
Sacha Trauwaen (1)
Salar Golestanian (4)
Sanjay Mehrotra (9)
Scott McCulloch (1)
Scott Schlesier (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (80)
Shaun Walker (237)
Shawn Mehaffie (17)
Stefan Cullmann (12)
Stefan Kamphuis (12)
Steve Fabian (31)
Steven Fisher (1)
Timo Breumelhof (24)
Tony Henrich (3)
Torsten Weggen (3)
Tycho de Waard (4)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (180)
William Severance (5)
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out