DotNetNuke Roles in 2007
As part of our recent DotNetNuke re-organization, every returning core team
member was asked to commit to specific areas of responsibility. This is
something we have been very lax about enforcing in past years, but which is
something that is desperately needed so that the entire team feels like we are
all working together towards a set of common goals. Also, as a co-founder
of the DotNetNuke Corporation we are required to spend part of our time working
on the Open Source side of the house. Even though I have spent much of the
last year trying to get the Marketplace and Review programs running, I still
have an obligation, first and foremost, to make sure that we are doing our best
to put out a great Open Source product.
In years past I have helped architect and code some portions of the
DotNetNuke core framework and to some degree, time permitting, I will continue
to assist in these efforts. However, going forward, I will primarily be
responsible for aiding our Project teams in architecting their solutions.
My job will be to provide guidance, and support where needed, to ensure that our
projects are following consistent practices. In this role I will also be
trying to identify common features that span modules and working with the
project leads to come up with a common API that can be added to the Core for use
by all of our projects and 3rd party developers.
Project leads should feel free to speak with me about technical challenges
they are facing so that we can find solutions that not only meet their specific
needs, but that also are in keeping with the overall architectural direction of
Finally, my job will also require close coordination with Shaun, who will
continue to head up architecture and coding of the core platform. The aim
is to ensure that I am providing appropriate guidance to the project teams and
to ensure that the core platform continues to evolve in a manner that will aid
module and skinning developers in meeting their common challenges.