Apparently I missed this. Sorry wicket, for the late reply.

I'm afraid that the source you're using has sacrificed conciseness for brevity. In an effort to not be "too long to read", they've chosen their wording poorly, giving a vague answer where a precise one is needed.

If you look at the wiki page for LGPL, and the terms themselves, it clearly states that there are several instances where LGPL code can be bundled into and with commercial products, and the resultant code does NOT need to be made public. It also states one can put copyright and other such restrictions on the resultant work, so long as it includes the proper text showing it contains LGPL libraries. See section 5 & 6 in particular for exact terms.

That is, in fact, the whole reason LGPL exists: To allow for commercial, non-public use of some parts of the Gnu project. You can read the FSF reasoning on why they created the LGPL here, and why they now advise against using it.

The part that requires you release source is if you modify the base library and want to re-distribute it as a separate thing. Then you have to supply code of the changes you made to the library for that purpose. Things like "plugin modules" (Karma), themes, forms, and code that interfaces with the library but are not part of it, are all exempt under LGPL.

Reality is that MidGard was put under LGPL for a reason, one which it's co-creator made very clear on the wiki page for MidGard itself. They placed it under LGPL so that they could turn around and create custom CM sites to sell to others without them having to worry about the legal ownership issues.