[Bug 481536] Review Request: enano - Enano CMS, a php-based modular content management system

[bugzilla at redhat.com]

Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.


https://bugzilla.redhat.com/show_bug.cgi?id=481536





--- Comment #10 from Dan Fuhry <dan at enanocms.org>  2009-05-27 00:05:14 EDT ---
Hi. I'm the project manager, and your contact for Enano upstream. Here is the
official word on these packages and how Enano uses them.

Text_Wiki stopped being developed in 2007. Enano forked the last version and
customized it heavily. It's now an integral part of Enano; the engine will not
work outside of an Enano environment. For now, I honestly think it would be
best to include our modified Text_Wiki with the Enano package.

We are doing some research on cutting Text_Wiki out of the picture entirely. It
was really only a band-aid solution until I could get good enough with PCRE to
hack up an engine myself, and now I have that level of knowledge, it's just a
matter of finding the time to go through it and build a list of things to
parse, design the new engine, and implement it. Patches welcome.

TinyMCE is not forked. We actually do not modify the code in their core package
at all. But we do throw a few extra files, tinymce_gzip*, into the TinyMCE
root. Those ARE modified, because the gzip script's caching feature has to
integrate with Enano's. Otherwise, you would have cached files in two
locations. From the webmaster's perspective, that is a disaster waiting to
happen. In any case, tinymce_gzip.php seems to depend on being in the TinyMCE
root. I can fork the hell out of that script for the sake of leaving the rest
of TinyMCE alone, or we can distribute TinyMCE with the Enano package, which is
probably safer anyway seeing as MoxieCode has historically been very good at
breaking their API on us.

freeCap is another thing we were forced to fork. The upstream package includes
a lot of overhead for deciding on a word to obfuscate into the image, but Enano
already took care of that so we had to remove that. Like the TinyMCE caching,
Enano has its own way of storing the captcha code and does not and cannot use
what freeCap provides.

Most other third-party components are single files - small PHP classes I found
on the net or borrowed from other projects because I didn't have the knowledge
to write them myself. This is the case with MediaWiki's table engine, phpWiki's
diff engine, etc. I'm not going to write out and get approval for packages for
a couple hundred KB of code from 10+ different sources. Reusing code != one
copy on the entire system.

That's the gist of things. Please take these into consideration and
re-evaluate.

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.