Welcome!

Open Source Cloud Authors: Elizabeth White, Liz McMillan, Jeev Trika, William Schmarzo, Derek Weeks

Related Topics: Open Source Cloud, Linux Containers

Open Source Cloud: Article

Managing an Open Source Project

A first-person perspective from idea to code complete

In December 2004 it was decided that DotNetNuke would break out its existing core modules into separate Projects so that they could be enhanced, released, and supported independently from the core Web Application Framework. It was further decided that some additional modules would also be added as official Projects to provide an increased level of richness to the platform. The first modules that we determined were going to be added were the TTT Forum and TTT Gallery, authored by Tam Tran Minh of TTT Corporation.

I was already working closely with Tam on these modules, and I volunteered to co-lead the development of these Projects and to help morph them into modules that take full advantage of the DotNetNuke Web Application Framework.

When the projects were first starting, the current DotNetNuke framework was in a transition. This transition included breaking changes that would not allow modules developed for the current released version, 2.1.2, to operate in the new upcoming version 3.0. My expectations were that Tam and I would work with members of the core team to convert the modules to work in the new 3.0 environment. After the modules were running in the 3.0 environment we would fix a few bugs that already existed in the modules and then have our first release. After this release we would start to form teams that would aid in enhancing the modules and fixing additional bugs, which I knew would surface over time. I expected it would take about three months until we were at the point of forming teams. What I expected and what actually happened were quite different.

Incubating a Third-Party Module Project
Because I was a member of the core team since its inception, I felt I had a pretty good understanding of what it would take to make these modules follow the unwritten rules of the current DotNetNuke core modules. The first part of this process was to convert the namespace and assembly names to follow the current patterns used by the other core modules. While doing this we also added in the copyright that was included in all current core .vb files to the .vb files of these modules. This process was pretty straightforward and required minimal effort; however, it took slightly longer than I had anticipated.

Once this was completed the remaining changes were not so obvious. Prior to these Projects, no outside module was ever brought into the core, so there was no preexisting checklist for us to follow. Another challenge we faced is that none of the core modules that are currently available were as complex as either one of these. After several discussions with other core team members we formed a plan. This plan was to focus on a single module - the DNN Forums - and get it released first. This decision, as we would later find out, would also speed up the development of the DNN Gallery project because it gave us a checklist to follow.

Now that we were focused on the DNN Forum project alone, we outlined what we knew had to be done prior to a release. The first item was to rename the custom class names that used a pattern not consistent with any of the core modules. At the time we thought it best to make use of the existing classes that were included in the default skins. We would later determine that because the module uses its own custom themes implementation, we should rename all classes to use a more standard ModuleName_ prefix to avoid conflicts with the preexisting classes.

Once the renaming was completed, the next item on our list was to remove any dependencies the module had on third-party assemblies. The reason this had to be done was due to licensing. Even though the only dependency was on a freely available assembly, this assembly did not have the same BSD license that is distributed with the DotNetNuke Web Application Framework. This meant that if the authors of this assembly decided to change their license, which they could do at any time, we could be forced to remove a release that was available for download to avoid legal ramifications. This dependency was on an assembly that allowed the module to interact with newsgroups. Removing support for this was no easy task because it existed throughout the entire module. This process seemed to only take a few weeks, but we would later find out that some of the remnants were causing one of the major bugs at the time.

Preparing for a First Release
When developing any project, you must determine a set of goals that should be accomplished to reach a release point. When dealing with an open source project that is constantly in development, this is even more important because you lack a well-defined set of requirements that you must achieve. Lacking these requirements makes it all too easy to keep developing and never reach a release point.

With the project now underway for almost three months, I knew the community was getting anxious to see the first official subproject release. I knew there were bugs in the existing code, but with only two of us actively working on the module, we were having difficulty filling the roles of architect, developer, and the Q&A team. We were trying to stick to the original plan of releasing then forming a team, so we decided to release a beta and use the community as our Q&A team.

Before we could release, we had to make sure that what we released is what people would expect from a DotNetNuke module. Among these expectations were the following:

  • Installable as a standard packaged module
  • Support the standard DotNetNuke data access layer and object qualifier
  • Allow the source code version to simply be copied over on top of an installed version
  • Support upgrades of this install in all future releases
  • Not altering the core Web Application Framework
  • Implementing ISearchable to expose to core search indexing
Once all this criteria was met we hit another road block. Since no module had been released separately from the core before, there was no proper procedure for releasing a module independently from the core. Since DotNetNuke has always been in the habit of installing its releases on www.DotNetNuke.com prior to distributing, we took this approach with the DNN Forum module. After fixing several bugs that we determined was necessary prior to public release, we finally made the module available for download.

After the First Release
With the module now available for download to the community, I prepared myself to start answering usability questions and to start focusing on bug fixes. To support the module release, we created a set of groups and forums on DotNetNuke.com. This turned out to be the most critical part of this project's development. It allowed me and other core team members, along with a few community members, to use the module on a daily basis as users and not developers. Using the module daily brought out many usability issues that were overlooked in the local development environment. It also was a place for others who would not normally test the module to see it in action and report any feedback they had on it.

After making the module available for download, there was no shortage of feedback. During the first week or two the module was available I found myself spending roughly two hours a day in the forums and in the project's bug tracker answering support questions and logging bugs. Trying to keep up with the feedback and fix the issues logged was becoming increasingly difficult.

One of the other things this release showed us was that most of the community was having a difficult time following and understanding the code. I don't think this was because the module was overly complex; rather, I feel it was because they had only been exposed to it for a very brief period of time. Our original goal was to start forming a project team now that we released, but with so many support issues I wasn't exactly sure where I would find the time. Working a full-time job and keeping up with other aspects of DotNetNuke, when was I going to form a team, teach them about the module, and manage them?

After spending a bit of time debating what would be best for the project, it was decided to continue development of the module as we were before, and then form a team after a release came out that we felt was fairly stable. This ended up taking two more releases and three additional months. Looking back on this decision now I feel that we made the right choice because I think even with a project team we wouldn't have stabilized the module this quickly.

Forming a Team
Now that the project had a release that we felt was fairly stable, it was time to start the recruiting process to form a project team. Once again we were at a point where there were no previous examples to follow. Until now, all those involved with the core were chosen and not recruited. We gave this some thought and decided that we would recruit members using posts in forums and ask the recruits to submit resumes so that we'd have an idea of their knowledge. I felt a bit uncomfortable asking for resumes from volunteers to work on an open source project, but I wasn't sure how else we were going to measure the recruits' knowledge.

We received about 10 submissions for the Forum Project. I wasn't really sure how many people we should have on the team, so I took the approach of accepting the eight applicants who seemed qualified. I e-mailed those whom I accepted and sent them the documents required to be a member of a DotNetNuke Project (an NDA and a Contributor License Agreement), and informed them that they were on a probationary period. The probationary period functioned to avoid their announcing publicly until we received all necessary agreements. Out of the eight, two never returned the agreements and two more resigned.

Managing an Open Source Project Team
It is my belief that regardless of whether your project is big or small, managing a development team in a commercial environment and managing one in an open source project are very similar. There are a few things, however, which are distinctly different. I think the aspect that is the most obvious, as well as the most difficult, is that you are managing volunteers.

In the commercial environment there is accountability. If someone is given a task, that person must complete it within a reasonable amount of time and if not, he or she must account for the reasons why it was not done on time. If the person fails to deliver repeatedly, there are some consequences that he or she might suffer. In an open source project, what consequences can you really dish out to volunteers? The only one I can think of is removing them from the team, but what do they really loose? So far I have been fortunate that all my team members contribute, but I am still unsure how I would handle it if things had gone differently.

Another one of those differences is communication. Everyone in the core team and in my projects speaks English. It may not be everyone's native tongue, but so far it has not been a barrier. Even with everyone speaking English there are still communication issues. Since we have no budget for traveling or phone conversations, it seemed best to use chat sessions for team meetings. This proved to be difficult because at our first chat we had one team member online at 8 p.m. Thursday and another online at 10 a.m. Friday. This wasn't so bad, except for those members who were online at 11 p.m. and 6 a.m. for a two-hour session.

The last major difference I have found between the two is how you would decide who does what. In the commercial environment I normally ask people to do things and based on their results, I let them continue doing so or replace them with someone else. I am not exactly sure why, but in the open source environment it just doesn't seem to work this way. So far, I have just let everyone do what he feels he is best at. This seems to be working because everyone is getting a better understanding of his module and the projects are moving forward faster than before. I do worry about this from time to time though, because I think I will eventually have to address it.

Despite all of the differences, there are many similarities between the two environments. One is you have a set of tools and have to get everyone adjusted to using those tools. The usage may not happen as frequently in the open source environment, but I think it is more than enough to keep the project organized. Procedure is another thing that is common between the two. I think this is even more important in the open source projects because it helps fill the communication gap.

Before becoming involved with the DotNetNuke Web Application Framework, one of the things I heard about open source projects is that they are a thankless effort. I have found this to be far from the truth. Just as with anything else, there is some negativity involved. In my experience however, this has been almost negligible compared to the praise received. This praise, combined with what I learn by doing this, makes it well worth the effort.

The Future
It has been roughly nine months since these Projects began. To the community, it may not seem as though much was accomplished. From my perspective, these Projects have come a long way. The previous release of the DNN Forum Project had over 35,000 downloads in only a three-month span. Now with the support of a team, features can be added, bugs can be fixed, and time between releases can be reduced. This increased efficiency, along with the implementation of continuous integration, should lead to more users and a better end result.

More Stories By Chris Paterra

Chris Paterra is is the lead developer and project manager working on a variety of different DotNetNuke projects for client and internal use at AppTheory in Atlanta, GA. He is part of the DotNetNuke core team and is project lead of the Forum and Gallery sub-projects.

Comments (2) View Comments

Share your thoughts on this story.

Add your comment
You must be signed in to add a comment. Sign-in | Register

In accordance with our Comment Policy, we encourage comments that are on topic, relevant and to-the-point. We will remove comments that include profanity, personal attacks, racial slurs, threats of violence, or other inappropriate material that violates our Terms and Conditions, and will block users who make repeated violations. We ask all readers to expect diversity of opinion and to treat one another with dignity and respect.


Most Recent Comments
Enterprise Open Source Magazine News Desk 05/05/06 04:11:45 PM EDT

In December 2004 it was decided that DotNetNuke would break out its existing core modules into separate Projects so that they could be enhanced, released, and supported independently from the core Web Application Framework. It was further decided that some additional modules would also be added as official Projects to provide an increased level of richness to the platform. The first modules that we determined were going to be added were the TTT Forum and TTT Gallery, authored by Tam Tran Minh of TTT Corporation.

Enterprise Open Source Magazine News Desk 05/05/06 04:10:52 PM EDT

In December 2004 it was decided that DotNetNuke would break out its existing core modules into separate Projects so that they could be enhanced, released, and supported independently from the core Web Application Framework. It was further decided that some additional modules would also be added as official Projects to provide an increased level of richness to the platform. The first modules that we determined were going to be added were the TTT Forum and TTT Gallery, authored by Tam Tran Minh of TTT Corporation.

@ThingsExpo Stories
Customer experience has become a competitive differentiator for companies, and it’s imperative that brands seamlessly connect the customer journey across all platforms. With the continued explosion of IoT, join us for a look at how to build a winning digital foundation in the connected era – today and in the future. In his session at @ThingsExpo, Chris Nguyen, Group Product Marketing Manager at Adobe, will discuss how to successfully leverage mobile, rapidly deploy content, capture real-time d...
A strange thing is happening along the way to the Internet of Things, namely far too many devices to work with and manage. It has become clear that we'll need much higher efficiency user experiences that can allow us to more easily and scalably work with the thousands of devices that will soon be in each of our lives. Enter the conversational interface revolution, combining bots we can literally talk with, gesture to, and even direct with our thoughts, with embedded artificial intelligence, wh...
IoT generates lots of temporal data. But how do you unlock its value? How do you coordinate the diverse moving parts that must come together when developing your IoT product? What are the key challenges addressed by Data as a Service? How does cloud computing underlie and connect the notions of Digital and DevOps What is the impact of the API economy? What is the business imperative for Cognitive Computing? Get all these questions and hundreds more like them answered at the 18th Cloud Expo...
As cloud and storage projections continue to rise, the number of organizations moving to the cloud is escalating and it is clear cloud storage is here to stay. However, is it secure? Data is the lifeblood for government entities, countries, cloud service providers and enterprises alike and losing or exposing that data can have disastrous results. There are new concepts for data storage on the horizon that will deliver secure solutions for storing and moving sensitive data around the world. ...
What a difference a year makes. Organizations aren’t just talking about IoT possibilities, it is now baked into their core business strategy. With IoT, billions of devices generating data from different companies on different networks around the globe need to interact. From efficiency to better customer insights to completely new business models, IoT will turn traditional business models upside down. In the new customer-centric age, the key to success is delivering critical services and apps wit...
The IoT is changing the way enterprises conduct business. In his session at @ThingsExpo, Eric Hoffman, Vice President at EastBanc Technologies, discuss how businesses can gain an edge over competitors by empowering consumers to take control through IoT. We'll cite examples such as a Washington, D.C.-based sports club that leveraged IoT and the cloud to develop a comprehensive booking system. He'll also highlight how IoT can revitalize and restore outdated business models, making them profitable...
Designing IoT applications is complex, but deploying them in a scalable fashion is even more complex. A scalable, API first IaaS cloud is a good start, but in order to understand the various components specific to deploying IoT applications, one needs to understand the architecture of these applications and figure out how to scale these components independently. In his session at @ThingsExpo, Nara Rajagopalan is CEO of Accelerite, will discuss the fundamental architecture of IoT applications, ...
The essence of data analysis involves setting up data pipelines that consist of several operations that are chained together – starting from data collection, data quality checks, data integration, data analysis and data visualization (including the setting up of interaction paths in that visualization). In our opinion, the challenges stem from the technology diversity at each stage of the data pipeline as well as the lack of process around the analysis.
SYS-CON Events announced today that ContentMX, the marketing technology and services company with a singular mission to increase engagement and drive more conversations for enterprise, channel and SMB technology marketers, has been named “Sponsor & Exhibitor Lounge Sponsor” of SYS-CON's 18th Cloud Expo, which will take place on June 7-9, 2016, at the Javits Center in New York City, New York. “CloudExpo is a great opportunity to start a conversation with new prospects, but what happens after the...
SYS-CON Events announced today that MangoApps will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. MangoApps provides modern company intranets and team collaboration software, allowing workers to stay connected and productive from anywhere in the world and from any device. For more information, please visit https://www.mangoapps.com/.
SYS-CON Events announced today that 24Notion has been named “Bronze Sponsor” of SYS-CON's 18th Cloud Expo, which will take place on June 7-9, 2016, at the Javits Center in New York, New York. 24Notion is full-service global creative digital marketing, technology and lifestyle agency that combines strategic ideas with customized tactical execution. With a broad understand of the art of traditional marketing, new media, communications and social influence, 24Notion uniquely understands how to con...
WebRTC is bringing significant change to the communications landscape that will bridge the worlds of web and telephony, making the Internet the new standard for communications. Cloud9 took the road less traveled and used WebRTC to create a downloadable enterprise-grade communications platform that is changing the communication dynamic in the financial sector. In his session at @ThingsExpo, Leo Papadopoulos, CTO of Cloud9, will discuss the importance of WebRTC and how it enables companies to fo...
SYS-CON Events announced today TechTarget has been named “Media Sponsor” of SYS-CON's 18th International Cloud Expo, which will take place on June 7–9, 2016, at the Javits Center in New York City, NY, and the 19th International Cloud Expo, which will take place on November 1–3, 2016, at the Santa Clara Convention Center in Santa Clara, CA. TechTarget is the Web’s leading destination for serious technology buyers researching and making enterprise technology decisions. Its extensive global networ...
Korean Broadcasting System (KBS) will feature the upcoming 18th Cloud Expo | @ThingsExpo in a New York news documentary about the "New IT for the Future." The documentary will cover how big companies are transmitting or adopting the new IT for the future and will be filmed on the expo floor between June 7-June 9, 2016, at the Javits Center in New York City, New York. KBS has long been a leader in the development of the broadcasting culture of Korea. As the key public service broadcaster of Korea...
In his session at 18th Cloud Expo, Bruce Swann, Senior Product Marketing Manager at Adobe, will discuss how the Adobe Marketing Cloud can help marketers embrace opportunities for personalized, relevant and real-time customer engagement across offline (direct mail, point of sale, call center) and digital (email, website, SMS, mobile apps, social networks, connected objects). Bruce Swann has more than 15 years of experience working with digital marketing disciplines like web analytics, social med...
With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo 2016 in New York and Silicon Valley. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be! Internet of @ThingsExpo, taking place Nov 3-5, 2015, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with 17th Cloud Expo and will feature technical sessions from a rock star conference faculty ...
The 19th International Cloud Expo has announced that its Call for Papers is open. Cloud Expo, to be held November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, brings together Cloud Computing, Big Data, Internet of Things, DevOps, Containers, Microservices and WebRTC to one location. With cloud computing driving a higher percentage of enterprise IT budgets every year, it becomes increasingly important to plant your flag in this fast-expanding business opportunity. Submit y...
There are several IoTs: the Industrial Internet, Consumer Wearables, Wearables and Healthcare, Supply Chains, and the movement toward Smart Grids, Cities, Regions, and Nations. There are competing communications standards every step of the way, a bewildering array of sensors and devices, and an entire world of competing data analytics platforms. To some this appears to be chaos. In this power panel at @ThingsExpo, moderated by Conference Chair Roger Strukhoff, panelists will discuss the vast to...
Internet of @ThingsExpo, taking place November 1-3, 2016, at the Santa Clara Convention Center in Santa Clara, CA, is co-located with the 19th International Cloud Expo and will feature technical sessions from a rock star conference faculty and the leading industry players in the world and ThingsExpo New York Call for Papers is now open.
SYS-CON Events announced today that Enzu, a leading provider of cloud hosting solutions, will exhibit at SYS-CON's 18th International Cloud Expo®, which will take place on June 7-9, 2016, at the Javits Center in New York City, NY. Enzu’s mission is to be the leading provider of enterprise cloud solutions worldwide. Enzu enables online businesses to use its IT infrastructure to their competitive advantage. By offering a suite of proven hosting and management services, Enzu wants companies to foc...