status: June 12th, 2011

Hi!

I've been really busy the last few months and haven't gotten anything 
I've wanted to do on PyBlosxom done.  Things have cleared up a bit and I 
finally have some breathing space, but...  probably not for long since 
I'm on another aggressive software release schedule.

For June, I want to focus on the following three things:

1. work on pyblosxom 1.5 and finish it up

2. work on cleaning up the PyBlosxom and project documentation

3. clear out my queue of things people are waiting on me to do


I won't be able to get all of these things accomplished, but these are 
the things I am focusing on.

Today, I spent some time with gitorious and wrapped my head around merge 
requests (finally).  It makes a lot more sense now.  One thing that's 
really important for a merge request is that we switch the way we're 
doing contributions to make sure contributions are done in bugfix branches.

I've overhauled the development docs accordingly:

    http://pyblosxom.bluesock.org/static/development.html

They assume you have a working knowledge of git currently.  I plan to 
add links on how to learn git, but really don't want to host our own git 
tutorial.  With that in mind, does the changes in the documentation make 
sense?  Are they still hard to follow?  What specific changes would you 
make?


There are some things I want to clean up in the PyBlosxom core, but 
first I think I need to step back a bit, go through the issues in the 
1.5 roadmap, and make sure there are issues for all the things I think 
need to be in PyBlosxom 1.5.  Part of the issue here is that I've been 
away so long, that I don't really remember what I was doing.


There have been people popping up on #pyblosxom with questions.  As 
people ask questions, I need help identifying the root of the issues and 
addressing those issues in either the documentation or the code. 
Probably the best thing to do is copy and past the IRC conversation into 
an issue with a sentence or two identifying the issue and possible 
solutions.

I think that's where things are at.

If you're waiting on me for something, let me know.  I've got 2000 
emails in my inbox and I'm tossing around declaring email bankruptcy 
because I can't work through them all.

/will

------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev