[pmwiki-users] The Philosophy of PmWiki: adding to the core
nzskiwi at gmail.com
Tue Nov 5 18:14:37 CST 2013
Ian and Tamara
I am not advocating PmWiki becoming bloatware or 'all things to all
people'. Far from it.
And I think that the recipe system is great. I've created two recipes, it
was a challenge for me, but I could do it, great.
My concern is the opposite.
If the PmWiki core is (too?) small, and (too?) many features are in the
PmWiki websites will end up being inconsistent, with each PmWiki
implementing a different subset of cookbook based features, fixes, and
markup, depending on the knowledge and ability of the wiki webmaster to
'know' which extensions to use, and be able to install and configure it,
On 4 November 2013 10:54, Tamara Temple <tamouse.lists at gmail.com> wrote:
> On Nov 2, 2013, at 4:59 PM, Simon <nzskiwi at gmail.com> wrote:
> > I'm soliciting some discussion from the PmWiki community on the approach
> to having features and functionality added to the PmWiki core.
> > There are a number of PITS entries that request modest enhancements to
> PmWiki, most of which would benefit writers and administrators, that are
> not being added to the core
> > Is this because there is a desire to avoid creeping "featureitis",
> > or because there is not the capacity to do these changes, awaiting
> feedback, suspended, or some other reason.
> > Often a suggestion is made to add these as a recipe or configuration
> item in config.php.
> > My concern is that if PmWiki is 'all recipes' and 'no improvements' it
> leads to a 'balkanisation' by recipe of PmWiki (and some recipes themselves
> are balkanised - which to use?), that is to say that while my wiki(s) might
> use a number of these great recipes, other don't, and writers can't reply
> on the same markup or features across different PmWikis. Consistency and
> completeness (orthogonality) have a place.
> > Now personally I don't use C2 wiki, or Usemod engines, because they
> don't have 'enough' features. PmWiki fits for me in the sweet spot, good
> features, easy to install, extremely responsive developers, doesn't try to
> be to much or all things to all people.
> > But I'd like to see the core PmWiki improving too.
> > As an administrator of several wikis I'd like to see more 'out of the
> > We don't have any way of installing recipes automatically (think app
> store), so both an ongoing maintenance effort is required and quite some
> knowledge of Pmwiki is required to carry out such customisations and recipe
> > over to you
> > Simon
> I’d like to see the core improving, and it does. What I would definitely
> *not* want to see is the core expanding and PmWiki turning into bloatware.
> A smaller core with extensions is a much better way to build and maintain a
> system. Monolithism is rather awful to deal with on many systems. What I
> would love to see, though, is a package management system that makes
> installing and updating recipes and skins easier, and aids development of
> local and shared recipes and skins. This is rather ambitious, I know.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the pmwiki-users