[geeklog-devel] we don't need to maintain the plugin's upgrade function

Michael Jervis mjervis at gmail.com
Thu Mar 20 07:55:02 EDT 2008

On Thu, Mar 20, 2008 at 7:49 AM, Joe Mucchiello <joe at throwingdice.com> wrote:
> Then what was the point of making them plugins? Some of them use to
>  just exist in the core.
>  Dirk has expressed hope that someone will take over control of some
>  of them. Part of that I assumed included decoupling their release
>  from the core. But as long as those plugins are inseparable from the
>  core, who is going to come along and take control of them?

They are separable, they are plug ins, but until the time comes that
someone picks them up and runs them separately why have an upgrade
function? The next release of the plugins will be with 1.5.0, thus
they don't need one and it's extra effort for us to have one.

As soon as someone makes changes and has it ready for a separate
release, that plugin can have an upgrade (for that version) created by
that new author.

>  Finally, when I finish the calendar bounty, it will be released
>  independently of Geeklog. And frankly I'm haven't said "I'll take
>  over calendar" because I don't want to be tied to GL releases. This
>  is a big step backwards away from giving those plugins separate life.

Sort of as above, if you do want to take over calendar and that's
agreed, then as soon as you're ready to release, then it can be
instantly divorced from the Geeklog release cycle and you'll need ot
write and maintain upgrades.

We just don't have the time/effort to make separate releases, as such
we don't need the upgrade function, which doesn't mean the plugin
can't have one just as soon as it's released separately, the big work
is done.

>  With forum and mediagallery having support for taking over index.php,

I think a plugin can already take over index.php, I'm sure there's a
hook in there (code not to hand)

More information about the geeklog-devel mailing list