Welcome!

Open Source Authors: Trevor Parsons, Dmitriy Stepanov, Carmen Gonzalez, Lacey Thoms, Yeshim Deniz

Related Topics: Open Source, Linux

Open Source: 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
Software AG helps organizations transform into Digital Enterprises, so they can differentiate from competitors and better engage customers, partners and employees. Using the Software AG Suite, companies can close the gap between business and IT to create digital systems of differentiation that drive front-line agility. We offer four on-ramps to the Digital Enterprise: alignment through collaborative process analysis; transformation through portfolio management; agility through process automation and integration; and visibility through intelligent business operations and big data.
There will be 50 billion Internet connected devices by 2020. Today, every manufacturer has a propriety protocol and an app. How do we securely integrate these "things" into our lives and businesses in a way that we can easily control and manage? Even better, how do we integrate these "things" so that they control and manage each other so our lives become more convenient or our businesses become more profitable and/or safe? We have heard that the best interface is no interface. In his session at Internet of @ThingsExpo, Chris Matthieu, Co-Founder & CTO at Octoblu, Inc., will discuss how these devices generate enough data to learn our behaviors and simplify/improve our lives. What if we could connect everything to everything? I'm not only talking about connecting things to things but also systems, cloud services, and people. Add in a little machine learning and artificial intelligence and now we have something interesting...
Last week, while in San Francisco, I used the Uber app and service four times. All four experiences were great, although one of the drivers stopped for 30 seconds and then left as I was walking up to the car. He must have realized I was a blogger. None the less, the next car was just a minute away and I suffered no pain. In this article, my colleague, Ved Sen, Global Head, Advisory Services Social, Mobile and Sensors at Cognizant shares his experiences and insights.
We are reaching the end of the beginning with WebRTC and real systems using this technology have begun to appear. One challenge that faces every WebRTC deployment (in some form or another) is identity management. For example, if you have an existing service – possibly built on a variety of different PaaS/SaaS offerings – and you want to add real-time communications you are faced with a challenge relating to user management, authentication, authorization, and validation. Service providers will want to use their existing identities, but these will have credentials already that are (hopefully) irreversibly encoded. In his session at Internet of @ThingsExpo, Peter Dunkley, Technical Director at Acision, will look at how this identity problem can be solved and discuss ways to use existing web identities for real-time communication.
Can call centers hang up the phones for good? Intuitive Solutions did. WebRTC enabled this contact center provider to eliminate antiquated telephony and desktop phone infrastructure with a pure web-based solution, allowing them to expand beyond brick-and-mortar confines to a home-based agent model. It also ensured scalability and better service for customers, including MUY! Companies, one of the country's largest franchise restaurant companies with 232 Pizza Hut locations. This is one example of WebRTC adoption today, but the potential is limitless when powered by IoT. Attendees will learn real-world benefits of WebRTC and explore future possibilities, as WebRTC and IoT intersect to improve customer service.
From telemedicine to smart cars, digital homes and industrial monitoring, the explosive growth of IoT has created exciting new business opportunities for real time calls and messaging. In his session at Internet of @ThingsExpo, Ivelin Ivanov, CEO and Co-Founder of Telestax, will share some of the new revenue sources that IoT created for Restcomm – the open source telephony platform from Telestax. Ivelin Ivanov is a technology entrepreneur who founded Mobicents, an Open Source VoIP Platform, to help create, deploy, and manage applications integrating voice, video and data. He is the co-founder of TeleStax, an Open Source Cloud Communications company that helps the shift from legacy IN/SS7 telco networks to IP-based cloud comms. An early investor in multiple start-ups, he still finds time to code for his companies and contribute to open source projects.
The Internet of Things (IoT) promises to create new business models as significant as those that were inspired by the Internet and the smartphone 20 and 10 years ago. What business, social and practical implications will this phenomenon bring? That's the subject of "Monetizing the Internet of Things: Perspectives from the Front Lines," an e-book released today and available free of charge from Aria Systems, the leading innovator in recurring revenue management.
The Internet of Things will put IT to its ultimate test by creating infinite new opportunities to digitize products and services, generate and analyze new data to improve customer satisfaction, and discover new ways to gain a competitive advantage across nearly every industry. In order to help corporate business units to capitalize on the rapidly evolving IoT opportunities, IT must stand up to a new set of challenges.
There’s Big Data, then there’s really Big Data from the Internet of Things. IoT is evolving to include many data possibilities like new types of event, log and network data. The volumes are enormous, generating tens of billions of logs per day, which raise data challenges. Early IoT deployments are relying heavily on both the cloud and managed service providers to navigate these challenges. In her session at 6th Big Data Expo®, Hannah Smalltree, Director at Treasure Data, to discuss how IoT, Big Data and deployments are processing massive data volumes from wearables, utilities and other machines.
All major researchers estimate there will be tens of billions devices – computers, smartphones, tablets, and sensors – connected to the Internet by 2020. This number will continue to grow at a rapid pace for the next several decades. With major technology companies and startups seriously embracing IoT strategies, now is the perfect time to attend @ThingsExpo in Silicon Valley. Learn what is going on, contribute to the discussions, and ensure that your enterprise is as "IoT-Ready" as it can be!
P2P RTC will impact the landscape of communications, shifting from traditional telephony style communications models to OTT (Over-The-Top) cloud assisted & PaaS (Platform as a Service) communication services. The P2P shift will impact many areas of our lives, from mobile communication, human interactive web services, RTC and telephony infrastructure, user federation, security and privacy implications, business costs, and scalability. In his session at Internet of @ThingsExpo, Erik Lagerway, Co-founder of Hookflash, will walk through the shifting landscape of traditional telephone and voice services to the modern P2P RTC era of OTT cloud assisted services.
While great strides have been made relative to the video aspects of remote collaboration, audio technology has basically stagnated. Typically all audio is mixed to a single monaural stream and emanates from a single point, such as a speakerphone or a speaker associated with a video monitor. This leads to confusion and lack of understanding among participants especially regarding who is actually speaking. Spatial teleconferencing introduces the concept of acoustic spatial separation between conference participants in three dimensional space. This has been shown to significantly improve comprehension and conference efficiency.
The Internet of Things is tied together with a thin strand that is known as time. Coincidentally, at the core of nearly all data analytics is a timestamp. When working with time series data there are a few core principles that everyone should consider, especially across datasets where time is the common boundary. In his session at Internet of @ThingsExpo, Jim Scott, Director of Enterprise Strategy & Architecture at MapR Technologies, will discuss single-value, geo-spatial, and log time series data. By focusing on enterprise applications and the data center, he will use OpenTSDB as an example to explain some of these concepts including when to use different storage models.
SYS-CON Events announced today that Gridstore™, the leader in software-defined storage (SDS) purpose-built for Windows Servers and Hyper-V, will exhibit at SYS-CON's 15th International Cloud Expo®, which will take place on November 4–6, 2014, at the Santa Clara Convention Center in Santa Clara, CA. Gridstore™ is the leader in software-defined storage purpose built for virtualization that is designed to accelerate applications in virtualized environments. Using its patented Server-Side Virtual Controller™ Technology (SVCT) to eliminate the I/O blender effect and accelerate applications Gridstore delivers vmOptimized™ Storage that self-optimizes to each application or VM across both virtual and physical environments. Leveraging a grid architecture, Gridstore delivers the first end-to-end storage QoS to ensure the most important App or VM performance is never compromised. The storage grid, that uses Gridstore’s performance optimized nodes or capacity optimized nodes, starts with as few a...
The Transparent Cloud-computing Consortium (abbreviation: T-Cloud Consortium) will conduct research activities into changes in the computing model as a result of collaboration between "device" and "cloud" and the creation of new value and markets through organic data processing High speed and high quality networks, and dramatic improvements in computer processing capabilities, have greatly changed the nature of applications and made the storing and processing of data on the network commonplace. These technological reforms have not only changed computers and smartphones, but are also changing the data processing model for all information devices. In particular, in the area known as M2M (Machine-To-Machine), there are great expectations that information with a new type of value can be produced using a variety of devices and sensors saving/sharing data via the network and through large-scale cloud-type data processing. This consortium believes that attaching a huge number of devic...
Innodisk is a service-driven provider of industrial embedded flash and DRAM storage products and technologies, with a focus on the enterprise, industrial, aerospace, and defense industries. Innodisk is dedicated to serving their customers and business partners. Quality is vitally important when it comes to industrial embedded flash and DRAM storage products. That’s why Innodisk manufactures all of their products in their own purpose-built memory production facility. In fact, they designed and built their production center to maximize manufacturing efficiency and guarantee the highest quality of our products.
Can call centers hang up the phones for good? Intuitive Solutions did. WebRTC enabled this contact center provider to eliminate antiquated telephony and desktop phone infrastructure with a pure web-based solution, allowing them to expand beyond brick-and-mortar confines to a home-based agent model. Download Slide Deck: ▸ Here
All major researchers estimate there will be tens of billions devices - computers, smartphones, tablets, and sensors - connected to the Internet by 2020. This number will continue to grow at a rapid pace for the next several decades. Over the summer Gartner released its much anticipated annual Hype Cycle report and the big news is that Internet of Things has now replaced Big Data as the most hyped technology. Indeed, we're hearing more and more about this fascinating new technological paradigm. Every other IT news item seems to be about IoT and its implications on the future of digital business.
BSQUARE is a global leader of embedded software solutions. We enable smart connected systems at the device level and beyond that millions use every day and provide actionable data solutions for the growing Internet of Things (IoT) market. We empower our world-class customers with our products, services and solutions to achieve innovation and success. For more information, visit www.bsquare.com.
With the iCloud scandal seemingly in its past, Apple announced new iPhones, updates to iPad and MacBook as well as news on OSX Yosemite. Although consumers will have to wait to get their hands on some of that new stuff, what they can get is the latest release of iOS 8 that Apple made available for most in-market iPhones and iPads. Originally announced at WWDC (Apple’s annual developers conference) in June, iOS 8 seems to spearhead Apple’s newfound focus upon greater integration of their products into everyday tasks, cross-platform mobility and self-monitoring. Before you update your device, here is a look at some of the new features and things you may want to consider from a mobile security perspective.