Introductions / Announcement

I am the QA team leader and have been on the core team for the past 2 year.  Being a  part of an open-source project as big as DNN has really taught me a lot, and I expect will teach me even more in the future.  For one I never thought I'd want to "volunteer" so much time to a development project that there was no monetary compenstatin.  But money is not everything, and I would not trade being on the core team for anything.  One of my first duties on the core was to keep the issues database clean. Keeping the issue database clean and trying to get a more defined QA process in place takes up a lot more time that most people think.  I tried to do it all myself my first year on the core team, and honestly almost burnt myself out.  But then after multiple talks with Shaun Walker and Scott Willhite, I realized I was trying to get everything done at once and by doing that it was destined to fail.  I am now taking the approach that "baby steps" are the way to go. 

That is why I am very happy that I have finally started getting a QA team created to help with QA related tasks.  The new QA team members are:

Oliver Hines
John Wilson
Rhonda Jernigan

The first task that will be tackles is to clean up the public DNN project in Gemini.   This will help keep the public database smaller and only contain the most recently reported bugs.  It will also move the  known issue to the correct private projects.

The next task that will be tackled is to clean up the private DNN project in Gemini. This process will include: Cleaning up duplicates, issues that are not longer issues in latest version, and Verifying that fixed issues were actually fixed and are no longer issues. 

By getting the 2 tasks above completed the community, project development teams, and the core team will have a more realistic view of what issue are outstanidng and what work still needs to be done.  Once we get these cleaned up it should also be easier to keep these 2 main projects in Gemini clean.  The cleanup will not happen overnight, but you should see improvements in the future in both projects.

Check my blogs periodically to read updates on other initiatives that are being worked on to improve the QA process of the sub-project (core modules) and DotNetNuke in addition to general blogs.  As we roll out some of these initiative we will need more team members for the QA team, so there will be more opportunities for other to get invovled in the QA team.  This is an exciting time for DotNetNuke, the core team and the community and I am proud to be a part of it.