I think that DotNetNuke is the best open source CMS. There no LAMP based CMS with the same number of modules. And, if you can't find the one for you, you can write it simply.
The only real limit of DNN is the environment. DNN run only on Windows and SQLServer.
I removed the second limit writing my own MySQL data adapter. I'm testing it. I wrote a TSQL translator that I can customize to write adapter for every DBMS. But TSQL is very hard to parse and some translation was made by hand.

I planned to remove first limit using Mono, available on Linux, MacOs, Solaris, ... The first big problem is with path handling. I think I will have to modify DNN core

I think that writing DNN code thinking about standard ANSI SQL and system dependent path separator shouldn't be so difficult. But it could bring to have an Open System. available on several dbms and several os. With no competitors.

Cristian Vanti

I had a client who was pretty strict on Linux. I started to look into Mono, but eventually convinced him that a Windows-based solution would be better. Despite that, I would love to see DNN supported on Mono and would definitely do what I could to help move in that direction.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com

This wouldn't be a project, per se. Based on how DNN projects are managed, the "right" way to do this would be to submit new issues in Gemini for each place that is problematic in Mono. These issues can be grouped, but it's best to submit them in fixable groups. If someone can provide specifics as to what places the problems exist, then that should be good enough for one issue. Having an over-arching "Mono support" issue wouldn't really be all that good, tho, because it'd be hard to tell when it was really accomplished.

The reason for not standing up a Mono project is because the code exists in all independent DNN projects. Each project lead needs to know how to manage and integrate necessary changes in their own time-frame.

As far as responsibility goes, PMI owns the copyright on all code; however, as I mentioned, project leads are responsible for getting source code updated. If a project lead falls too far behind, the core team can pick up the slack.

---

Michael Flanakin | Microsoft Consulting Services
www.michaelflanakin.com