Re: filestat - a different perspective
"Wai Yip Tung" <tungwaiyip-/[email protected]>
| Newsgroups | gmane.comp.web.pyblosxom.user |
|---|---|
| Message-ID | <[email protected]> |
How many pyBlosxom users are not Python hackers? My bet is nearly none. pyBlosxom have just enough functionality to us v.s. a complete blogging application. We are happy to hack the rest to suit the way we want. Perhaps we should really rebrand pyBlosxom not as a blogging application like MovableType but a toolkit for building your own blog. Keep improving the framework to meet the hacker users' requirement but not necessary doing the work for them. Build a plugin registry to help users to assemble their own blogs quicker. Keep the core small, that's what makes it hackable. It is always possible for someone to independently start a project using pyBlosxom to build a complete application out of it. I still think it is good to have at least one decent template as a demonstration. Kust so not to turn off new users before they have a chance to evaluate it. Wai Yip > On Fri, 20 Aug 2004, David Ascher wrote: >> >> Speaking for myself, the problem is that the strengths of blosxom for >> one audience: >> >> - the simple text-file formats >> - the 'simple' publishing model (create a file) >> - configuration through config.py > > The way I view PyBlosxom is that it's not for "users" in the general > sense. I would never tell my mom she should use PyBlosxom. I tell most > of my friends (some of whom have degrees in Computer Science) to use > LiveJournal. I see PyBlosxom's audience as other > developers/hackers--people who just want a framework to build off of. > > I realize that disenfranchises a lot of people and that some will > disagree > and/or dislike this "mission". And I also realize gearing things towards > hacker-types doesn't necessarily get us out of the business of making > things work better out of the box. > > > I think what you and Lee are talking about (I just read your response to > Lee's message) would help to satisfy both camps and possibly simplify > portions of the existing PyBlosxom codebase as well. > > >> Again, think of Zope vs. Plone. Zope does it all, but as far as I can >> tell, Plone makes it more accessible to a broader set of users. I think >> the same dichotomy applies here, and the same synergies can apply. > > Maybe we should slim down PyBlosxom some more into a pyblosxom-core > package (details to be figured out at some later date). Then have "New > Project" either extend the pyblosxom-core or interface with it. > > /will > > > ------------------------------------------------------- > SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media > 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 > Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. > http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285 > _______________________________________________ > pyblosxom-users mailing list > pyblosxom-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org > https://lists.sourceforge.net/lists/listinfo/pyblosxom-users ------------------------------------------------------- SF.Net email is sponsored by Shop4tech.com-Lowest price on Blank Media 100pk Sonic DVD-R 4x for only $29 -100pk Sonic DVD+R for only $33 Save 50% off Retail on Ink & Toner - Free Shipping and Free Gift. http://www.shop4tech.com/z/Inkjet_Cartridges/9_108_r285