# Sunday, April 01, 2007

Loosen up for goodness sake and GET YOUR FACTS RIGHT.

Check this post out... and note these words - We do ask all of our Project Leads - LEADS.. that's a big difference to being just part of the team isn't it... and guess who was the LEAD on the compression project .. Ben Lowery - the person elevated to Project Lead status without wanting to be there, never responnding to email and that's why the project sat for months with no direction or guidance even after many email between the Project MEMBERS to change the status to get the project going. Get that guys - John Mitchell was NEVER a LEAD. He was a Project MEMBER.

Now to lock that post simply amazes me...

The offending LOCKED post - Locked by the DNN Board to 'protect the community'

CLICK HERE TO VIEW FULL POST

 John Mitchell wrote

I offered to integrate PageBlaster technology into the core when I was on the core team, but it was rejected because I have another commercial module with the same technology.

For the sake of clarification only...

Any substantial (largely complete) code contribution to DotNetNuke must be accompanied by a "Software Grant".  Essentially, this provides for the ability to have dual copyright by both the original contributor & DotNetNuke.  This means that the contributor is protected because they can continue to do anything they like with the code without restriction (which includes commercial use).  However it also ensures that it can be included in DotNetNuke without "tarnishing" our BSD license, which protects all users of the DotNetNuke platform.

We do ask all of our Project Leads NOT to engage in commercial development (retail) of DNN applications that are like the project they are responsible for.  This is simply to avoid any appearance or possibility of conflict of interest which might arise from "holding back" on a project due to competition with their own offerings.  However, many of our Project Leads engage in commercial development (retail) of other modules and also enhancement of their projects for custom use, which generally winds up back in the Projects (and provides broad benefit).

>>> End Post

I think if you want to make an attempt to hang people out to dry and lock posts so others can't respond here's a tip - get your facts straight so there is no room for error in 'transparent' behaviour.

I'm back and with avengence... and in the coming weeks you're all going to know why.

Nina Meiers


 

Archive
<March 2007>
SunMonTueWedThuFriSat
25262728123
45678910
11121314151617
18192021222324
25262728293031
1234567


Disclaimer
The opinions expressed herein are my own personal opinions and do not represent my employer's view in any way.

© Copyright 2009 Nina Meiers
Sign In