[MTOS-dev] Proposal: Lose the "extras" dir

[Jay Allen]

+1 on this proposal wrt to the plugins directory.  I think it's
crucial to be able to ship certain important plugins which, for all
intents and purposes are only plugins because they were deemed
important to be completely pluggable yet provide important benefit to
the system.  It's also desirable to ship other useful or widely used
plugins to save people (read newbies) time and hassle on the
installation, but these can be disabled by default.

I agree about the extras directory.

Jay

On Feb 19, 2008 11:09 AM, Mark Carey <mark at mt-hacks.com> wrote:
> On Tue, Feb 19, 2008 at 2:28 PM, Su <hamletcomplex at gmail.com> wrote:
> > I remember running across something to the effect that more effort would be
> > put into making sure that the extras plugins /are/ functional in the future,
> > but if so, then why would they not be placed in the regular plugin dir? They
> > just seem kind of like afterthoughts here.
>
> A related proposal is this:
>
> MTOS should have a means to ship "included" plugins in a disabled
> state.  In other words, plugins that live in the /plugins/ directory
> but are disabled by default, until explicitly enabled by the user.
>
> This doesn't solve the issue of having extra files in the download
> distributions, but it could save resources by not loading potentially
> "unnecessary" plugins, yet making it *very* easy to enable them,
> without needing to seek them out, download/upload, etc.
>
> I suppose a dead-simple version of Plugin Manager that "just works" on
> all systems (without needing additional perl modules, etc.) would be
> enough, but I don't think we are there yet.  Barring that, being able
> to bundle plugins in a disabled (default) state would be nice.
>
> -Mark
> _______________________________________________
> MTOS-dev mailing list
> MTOS-dev at sixapart.com
> http://www.sixapart.com/mailman/listinfo/mtos-dev
>