SV: [Phpwebsite-developers] Roadmap

[Frits J. <FJ...@uv...>]

I totally agree! This way the obvious danger of mess, interference and
disagreements is avoided. It cannot be avoided that some want to make things
different than others out of need, religion or whatever reason. Is
everything in modules, forced to compatibility by standards set by the core
program, set by Appalachian on input of everybody, hey - everybody is happy
:) More product, less fuss. We can easily have two 'official' versions of a
plugin, thus having creative and productive "arguments" (my plugin is more
popular than yours) instead of stopping democracy - Join the force of your
choice.

Less chance of core problems! 'This plugin returns error' is better than
'This product returns error'

Also it will reduce the betaversions, as the central core will be easier to
produce, and then one may have to wait for plugins, but this must be better
than to wait for the whole package..

Another obvious, and I should think extremely giving bonus, is that
programmers will have more to show; "Plugin by:.." instead of "Contributors
to the project, version this and that:..."

The core should *never* sacrifice anything in order to be
backwards-compatible between major releases. A plugin should have a number
in its name, referring to which version of core it worked with, eg
'weather_plugin_7.php'. The reason for this is that this is free code, not
expansive hardware - you can just upgrade everything if you want to move to
next major release - This way we can get a head start, and move fast and
flexible - not get stuck like some well known DOS-based OS, or as a large
non-module-based project easily could be.

The guys at Appalachian should kick back and decide which plugins they'd
recognise, then put them on the official site after validating XTML, safe
programming, etc.


BTW; I am working on a proposal for CSS standards. Anyone read my (and
Karstens) thoughts, and have comments?


=) I think this whole community thing is way far out funny; Humanoids are
moving from individuals to interacting cells in a large producing organism.
Maybe if the right circumstances are there, life eventually will occur.
Given the chance of communicating with ASCII in real-time on a global basis,
coding eventually will occur. Hello fellow cells :) Forgive me for looking
down.. Hail Todd. Frits.

> -----Oprindelig meddelelse-----
> Fra: Todd Owen [mailto:to...@da...]
> Sendt: 30. marts 2001 16:39
> Til: php...@li...
> Emne: Re: [Phpwebsite-developers] Roadmap
> 
> 
> My proposal is that EVERYTHING should be a plug-in, including 
> much of what
> is now "core" functionality, like the referrer tracking, 
> categories and
> polls.  I want to see phpWS as more of an erector site, with 
> just about
> everything available a la carte.  What does everyone think 
> about this?  I
> think it helps a user mentally organize phpWS and makes my 
> database scheme
> ;) look more logical.
> 
> Each plug-in module would have its own admin page too and it 
> would be the
> perfect place to add access control.
> 
> --Todd
> 
> 
> 
> _______________________________________________
> Phpwebsite-developers mailing list
> Php...@li...
> http://lists.sourceforge.net/lists/listinfo/phpwebsite-developers
>