On 02/02/2010 05:55 AM, Evan Prodromou wrote:
I'm mildly opposed to this on a number of levels.
Plugins are not fundamental. The unit of extension in StatusNet is the event
hook, and I'd like it to stay that way.
At the low level yes, but not at the administrative level. We don't
expose event hooks to configuration in config.php or admin panels -- we
tell administrators how to install and enable individual plugins, and
event hooks are behind the scenes hidden away in the code.
Also, there's only so much saving people from themselves that we should
reasonably do. If you don't know what's going on in your config file, you're
going to have other problems.
The problem we've had isn't with what's in config.php -- it's with
what's in lib/defaults.php changing unexpectedly, in a different way
from how everything else changes.
When we change most default settings, any custom settings that override
them in config.php are simply kept. But when we add a default plugin
that had been explicitly loaded, now you get two instances of the plugin.
Following the principle of least surprise leads me to think that
anything on the default plugin list that's been loaded manually doesn't
need to be loaded a second time -- this would make plugins work like
every other configuration setting.
-- brion
_______________________________________________
StatusNet-dev mailing list
StatusNet-dev@lists.status.net
http://lists.status.net/mailman/listinfo/statusnet-dev
