Products

Solutions

Learn More

Partners

Community

Blog

About

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.


New CLA Process for DNN!

As you most likely know, there has been a lot of change lately within the DNN Community. The good news is that the change is positive! The focus on the community driving again and the return to true open source is real. Continuing with the focus on open source today we’re announcing a new CLA process that should make things a lot easier for everyone.

What is a CLA?
If you are a developer who makes contributions on GitHub this is not news to you, but to everyone else who touches DNN (those outside of the pull request world) it may not be so obvious. The source code for DNN is maintained on GitHub which makes it publicly visible. As DNN is an open source project, developers can contribute updates, enhancements, bug-fixes, documentation and more through GitHub.

Whenever a developer makes a contribution a Contributor’s License Agreement (CLA) needs to be in place. Having a CLA in place ensures that the developer is ok with freely donating their code to the greater platform with no strings attached. The CLA has a legal “feel” to it, but that is to protect everyone that’s involved with the project.

DNN’s Current CLA Process
Our current process for getting a contribution is a manual process that requires multiple communications, printing, scanning, and way to many emails. It goes like this… when a pull request is made the reviewer must check to see if the contributor has a CLA on file. If they do, the appropriate label is assigned. If not, the reviewer reaches out to me and I contact the individual who made the pull request linking them to the document they must sign, print, scan, and email back to me. After receiving the signed document I then update the list, email the reviewer, and let them know that we are ok to merge the pull request should it be beneficial.

Current CLA Process Image

Obviously this is inefficient and that’s why we’re happy to we’re able to leverage resources provided to us by the .NET Foundation. The new and updated process will remove roadblocks to contributing, to be more efficient, and to provide our contributors with a better experience.

Being in the .NET Foundation is Beneficial (Again)
.NET Foundation LogoEarlier this year it was announced that DNN joined the .NET Foundation. Although everyone may not have understood what this meant or how it was beneficial it was indeed a big moment in the history of DNN. It was an inflection point because it outwardly confirmed to the community that DNN would never be a closed solution and that DNN would remain open source with attributions to the .NET Foundation.

Along with following the general core principle of being open source, being a member of the .NET Foundation has allowed us access to resources we previously didn’t have such as access to VSTS automated build tooling, paid Meetup accounts for our user groups, access to share our info with larger bodies of Microsoft developers, and more. And this new CLA automation functionality that we’re leveraging is just another reason why we’re happy that we joined. Without being a member of the .NET Foundation this wouldn’t be possible… so thanks again to the .NET Foundation and everyone who is a part of it!

So we’ve got this new "thing" that makes "stuff" better… let's add some clarity...how does it work?

How Do I Sign a CLA Under the New Process?
So the question is… how do we use the new CLA process? Moving forward if a contributor does not have a signed CLA on file, they will be prompted with the automated CLA request before the pull request process is complete.

We’ve just put this in place and you can see the email copy that gets sent to the contributor below.

Automated Email Requesting CLA Signature

Once the CLA is signed then you’ll see the CLA on file tag showing with the purple .NET Foundation logo present - Automation FTW!

Screenshot of GitHub Showing the CLA Process has been completed

Automation, Efficiency, and More Wins For the Community
Having this new automated CLA process in place is definitely a win for our community. Along with providing a better experience to our contributors, reviewers, and maintainers this is again a sign of progress and commitment to both open source and community. The reason it’s a sign is because we’re only able to use this CLA tool via the .NET Foundation and we’re only able to be in the .NET Foundation because of the recommitment and focus on open source and the community.

I think it’s important to keep the big picture in mind as we navigate the waters of change. The Community is driving again, we are making progress, and we are becoming more efficient.

Now submit those pull requests!

Comments

Will Strohl
Very cool stuff! Can you please expand on the free meetup stuff?
Will Strohl Monday, July 2, 2018 3:15 PM (link)
Clint Patterson
Yes... one of the benefits offered by the .NET Foundation is that they pay for a Meetup Pro account and extend that to any .NET OSS based meetups. You can see their account here (https://www.meetup.com/pro/dotnet) So by being associated with the .NET Foundation our user group no longer has to pay a meetup fee + we get visibility/exposure to a larger body of .NET developers. I know that our user group and the TADUG are both leveraging this. It removes one of the burdens of running a user group!
Clint Patterson Monday, July 2, 2018 3:22 PM (link)

Comment Form

Only registered users may post comments.

NewsArchives


Aderson Oliveira (20)
Alec Whittington (11)
Alessandra Davies (1)
Alex Shirley (10)
Andrew Hoefling (3)
Andrew Nurse (30)
Andy Tryba (1)
Anthony Glenwright (5)
Antonio Chagoury (28)
Ash Prasad (36)
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 (212)
Chris Paterra (55)
Clint Patterson (89)
Cuong Dang (21)
Daniel Bartholomew (2)
Daniel Mettler (165)
Daniel Valadas (6)
Dave Buckner (2)
David Poindexter (10)
David Rodriguez (3)
Dennis Shiao (1)
Doug Howell (11)
Erik van Ballegoij (30)
Ernst Peter Tamminga (79)
Francisco Perez Andres (8)
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 (3)
Ken Grierson (10)
Kevin Schreiner (6)
Leigh Pointer (31)
Lorraine Young (60)
Malik Khan (1)
Matt Rutledge (1)
Matthias Schlomann (16)
Mauricio Márquez (5)
Michael Doxsey (7)
Michael Tobisch (3)
Michael Washington (202)
Miguel Gatmaytan (3)
Mike Horton (19)
Mitchel Sellers (32)
Nathan Rover (3)
Navin V Nagiah (14)
Néstor Sánchez (31)
Nik Kalyani (14)
Oliver Hine (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 S (11)
Scott Wilkinson (3)
Scott Willhite (97)
Sebastian Leupold (81)
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 (2)
Vicenç Masanas (27)
Vincent Nguyen (3)
Vitaly Kozadayev (6)
Will Morgenweck (40)
Will Strohl (171)
William Severance (5)

Content Layout

Subscribe to DNN Digest

Subscribe to DNN Digest

DNN Digest is our monthly email newsletter. It highlights news and content from around the DNN ecosystem, such as new modules and themes, messages from leadership, blog posts and notable tweets. Keep your finger on the pulse of the ecosystem by subscribing.  

What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out