I have noticed that PITs entries don't seem to be much exposure (eg on mailing lists), discussion (eg comments on the page), or support (eg votes).<div><br></div><div>I'd like to see a bit more boldness and vitality in the PmWiki community,</div>
<div>the pace of change when I started using PmWiki was exciting, </div><div>and encouraged me to hop on board the train.</div><div><br></div><div>I worry that we have changed to an era where we should be more progressive,</div>
<div>and now have a philosophy of being overly conservative about changing the core.</div><div>Perhaps we have an opportunity for the committers to lead a discussion about the road map for the core, and for extensions.</div>
<div><br></div><div>I'd like to see more submissions from code submitters taken on board and acted upon.</div><div>Particularly where those enable recipe writers to improve there recipes,</div><div>and where they fix identifiable issues in the core.</div>
<div><br></div><div>While I wouldn't like PmWiki to because a swiss army knife (one of the reasons I chose it), on the other hand I didn't want UseMod (as an example of a low feature low change wiki) either.</div>
<div>When it gets to the point that I have to individually select and install 20 or so recipes to get the functionality I want I have to wonder if the balance has swung too far in the other direction.</div><div>I don't have a problem with changing PmWiki behaviour, or removing some backward compatibility between major releases, especially if it supports a clean code base, and a more consistent experience for authors.</div>
<div><br></div><div>I recognise that adding to the core adds to complexity, and the the load of the maintainers - my suggestion, increase the community of submitters.</div><div>I also recognise that in in some areas - eg images - there are a number of great recipes, in others there are exactly one that do a good job of enabling some 'basic' functionality,</div>
<div>I can think of several, but examples to me (off the top of my head) are <a href="http://www.pmwiki.org/wiki/Cookbook/Attachtable">attachtable</a>, <a href="http://www.pmwiki.org/wiki/Cookbook/RowspanInSimpleTables">rowspan</a>, and the jt patch to <a href="http://www.pmwiki.org/wiki/Cookbook/Tabtable-jt">ExcelPaste</a>, all of which, to me, add what I consider to be needed and basic functionality.</div>
<div><br></div><div>I also do appreciate the responsiveness of the current committers and the size of the task facing them, its partially for this reason that a good discussion from the PmWiki community is required.</div>
<div><br></div><div>PmWiki is a fantastic product, lets keep it that was through keeping it active, evolving, and through the participation and contributions of us, its community.</div><div><br></div><div>thanks</div><div>
<br></div><div>Simon</div><div><br></div><div><a href="http://www.pmwiki.org/wiki/PmWiki/Audiences-Talk">http://www.pmwiki.org/wiki/PmWiki/Audiences-Talk</a></div><div><br><br><div class="gmail_quote">2009/6/27 Chris Cox <span dir="ltr"><<a href="mailto:ccox@endlessnow.com">ccox@endlessnow.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">I think there are two sides... I like PmWiki as a set of lower level<br>
tools... a toolkit upon which we can build extensions (we often call<br>
these recipes).<br>
<br>
The other side are those looking for a feature rich deployment platform<br>
where little to no configuration (even downloading a "recipe") is<br>
required.<br>
<br>
So, with that said, I think the idea of "recipes" in the core is<br>
possible, but I'd like to see it done in a way that does not require<br>
adding bloat to the base PmWiki. Perhaps some automated way to pull in<br>
"signed" extensions afterward (?)... or maybe a large add-on download.<br>
Of course, there will also be the normal "recipe" way of pulling in othe<br>
rextensions (along with the problems and conflicts that they might<br>
cause).<br>
<br>
So, for example, I download PmWiki, which allows ME to build great<br>
things. But let's say there's feature-full blogging package that is now<br>
part of the core (a "signed" extension). And it has all the bells and<br>
whistles of the major blogging packages out there, perhaps is close to<br>
the size of the PmWiki core itself. That piece could be optionally<br>
added using some kind of automatic PmWiki package install command... or<br>
it might be part of the larger inclusive extension package that I could<br>
install.<br>
<br>
Obviously, things like this would require some work.<br>
<br>
Bug fixes though are fine. And additions to the core that make it a<br>
better more flexible toolkit is also fine.<br>
<br>
<br>
<br>
Just some ideas...<br>
<div><div></div><div class="h5"><br>
<br>
<br>
<br>
_______________________________________________<br>
pmwiki-users mailing list<br>
<a href="mailto:pmwiki-users@pmichaud.com">pmwiki-users@pmichaud.com</a><br>
<a href="http://www.pmichaud.com/mailman/listinfo/pmwiki-users" target="_blank">http://www.pmichaud.com/mailman/listinfo/pmwiki-users</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>____<br><a href="http://kiwiwiki.co.nz">http://kiwiwiki.co.nz</a><br>
</div>