pyblosxom 1.4 status

On 5/22/07, Ryan Barrett <pyblosxom-6sb6M7qyT/[email protected]> wrote:
> On Mon, 21 May 2007, John Gabriele wrote:
>
> > Now when I run ``make``, I get what looks like the entire plain text
> > manual spewed to my stdout, starting with::
> ...
> > echo "Copying book1.html to index.html."
> > Copying book1.html to index.html.
> > cp book1.html index.html
> > cp: cannot stat `book1.html': No such file or directory
>
> hmm. i don't have much experience with docbook tools, but i am able to build
> the docs in pyblosoxm svn. which versions of openjade and htmldoc are you
> using? (i'm on ubuntu dapper, with openjade 1.4 and htmldoc 1.8.24.)

I really want to convert the PyBlosxom manual from docbook to reST.
That and reworking the web-site so that it's built with static
rendering are my next set of projects.


> > 2. Seems like it would be nice if there were, by default, always a
> > link at the top of every blog page that pointed back to the main front
> > blog page.
>
> interesting. you can definitely add this to your story template, but it's not
> a bad idea to include it by default. i've done this. will, etc, holler if you
> disagree.

That's a good idea.


> > Incidentally, being a community project, isn't there anyone else who
> > can make a release if you're not available? I notice that there's 11
> > names in the AUTHORS file.
>
> definitely! any of the sourceforge site admins - will, me, ted, wari - can cut
> a release, and we'd be happy to consider adding more. in practice, it's a
> small project, and will is the lead, so he sets the project's direction and
> tone, and he decides what and when to release.

This is something that's hugely my fault.  Since I took over
maintenance, I haven't provided the necessary pieces for the project
to scale beyond more than one or two developers.  Some of the work
that needs to be done is documenting what constitutes the project
(i.e. the mission), where all the pieces are, processes for various
things (releases, submitting bugs, ...), and documenting the design
decisions we've made and why.

The next two weeks are pretty wild, but I've done some work in this
direction already.  I just need to complete it.  It'll (theoretically)
be easier once 1.4 is out the door since that's less that I'm sitting
on.

I really apologize for not managing this project well.  I didn't
realize how much of a bottleneck I was until I didn't have time to fix
it effectively.

/will

-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/