Re: [Pyblosxom-devel] New entry triggered events.

[Wari W. <wa...@ho...>]

will wrote:

>Oh--I didn't know about that directory.  I'm thinking we should move the 
>existing plugins to that directory so that people can opt-in to the ones 
>they want.  Unless you're thinking that there would be a series of plugins 
>that almost everyone will want (calendar, categories, archives, comments, 
>(track|ping)backs...)?
>  
>
Thing that write to a file or is slow in execution, or not something 
everyone would need (like the 404 error generator or the conditional 
HTTP) will have to be in the contrib/plugins/ directory, in the case of 
comments or feedback modules where there are going to be more than one 
file involved, it should stay in a contrib/xxxx/ directory and should 
contain some documentation to it. Agreed?

>Maybe we should split this from the rest of pyblosxom almost into its own 
>subproject with its own CVS tree.
>  
>
Yes, I'm thinking about this as well, hence I want a name for it that we 
can agree (pyblosxom-extensions, etc)

>There are varying degrees of vocal users, though.  There are vocal users 
>who correctly point out that a portion of the architecture is ugly and do 
>so over and over again, 
>
They will have to suggest and give some diffs for proof of concept. I 
know pyblosxom is ugly, it was ugly as I did it without planning 
following blosxom.

>and there are the vocal users who either haven't 
>read the documentation or they have fundamental differences in how they 
>see the project.
>
Documentation is lacking, yes :) I do try to give the best of my time 
for it.

>I don't think it makes sense to cater to either category.  Though in
>regards to the first category of vocal users, it's better to fix the issue
>before they get vocal because they can be a pain in the ass and no one
>likes bad architecture.
>  
>
Yeah, I don't like it too, blame it on me for being a python newbie 
trying to take on such a project :)

>However, with the contrib directory, this becomes a moot point.
>  
>
:)

>There's a pretty severe lack of documentation for pyblosxom.  This is both
>user documentation as well as project documentation.  For instance, no
>where can I find what pyblosxom's purpose and goals are.  What is the
>target audience?  What should someone know before running pyblosxom?  
>What requirements are there for running pyblosxom?
>  
>
The main documentation for pyblosxom is at 
http://wiki.subtlehints.net/moin/PyBlosxom which I try my best updating, 
it got tiring after a while, but I do update here and there whenever 
possible.

>I think we're going to start attracting users like Kai who will notice the
>lack of documentation and will just start asking the same questions over
>and over again on the list.
>  
>
Hey, Kai actually did some documentation on the Wiki site, See: 
http://wiki.subtlehints.net/moin/PyBlosxom_2fExtendingPyBlosxom_2fPreFormatters_2fGenericWiki 
actually it's a copy from my mails, whatever info I give from my blog, I 
tried to copy it over there as well. And this: 
http://wiki.subtlehints.net/moin/PyBlosxom_2fExtendingPyBlosxom_2fPlugIns 
need some input too :)

>I'm not really sure what to do about this.  There doesn't seem to be a
>central project page for pyblosxom other than the roughingit site which is
>a blog and not really conducive to solid project documentation.
>  
>
I still think the wiki page should be the site documentation where 
everyone can contribute.

BTW, yeah the wiki was linked by my site, probably too low down the 
menu, or people don't know what a wiki is :)