[Pyblosxom-devel] Re: my issues

[<su...@ho...>]

On Mon, Feb 10, 2003 at 09:23:48AM -0600, will wrote:
> Um, Theodore, did you read the thread from last week regarding the url
> handling stuff I was working on that Wari asked you to read?

Ah yes, issues that bugs me still.

> I'm seriously concerned right now.  I think there are way too many
> cooks with their hands in the soup who aren't bothering to coordinate
> with the other cooks.  

I guess what we can do for now is to at least define some form of roles
and what each of us can do to contribute to pyblosxom. I for one is
trying to make things as modular as possible, Ted and Blake are doing
comments, and as for you, in charge of api functionality.

> I go on vacation for a few days and come back to find a flurry of
> development (which is fine) which (unless you guys are communicating
> off the list--which sucks for coordination) seems to be totally
> uncoordinated.

As far as I know, I did not communicate off the list, as far as
possible.

> My basic problems with this project go like this:
> 1. there are no coding conventions--everyone's using their own style
>    and the code base is a mess of several different styles which makes
>    it difficult to figure out what's going on.

We could solve this by following some coding guidelines, I guess the one
you have for lyntin would be a good base to start.

> 2. people aren't adequately documenting what they're doing.  this is
>    both specifications that should be written to the devel list so we
>    can discuss things BEFORE they happen as well as inline
>    documentation in the code.

I hope I've given enough information as to what I'm doing so that no one
gets lost.

> 3. there are some fundamental architecture changes that need to be
>    done.  my first blush impression by looking at the checkin diffs
>    over the last week, we're duplicating functionality and calling it
>    different names.

Can you point out which of these fires needs to be put out? Yeah, being
new to python development doesn't help, but at least I do try my best to
point out what will break big picture.

> So what's the deal?  I definitely don't want to be involved if it's
> going to be this chaotic.  

I guess you could give us a chance? pyblosxom-devel with all the cooks
in it are quite young, basically, it's just two months old (does it feel
like a long time or what?). Heck even most of the code contribution is
not mine.

> I'm totally not down with the "throw code together then discuss"
> method of doing things--I think it's an extremely poor development
> model which leads to a very large and unwieldy code-base with a lot of
> funkiness in edge-case scenarios.  It's not like we're inventing a
> totally new wheel here--many of the things we're discussing have been
> done over and over again in other projects.

What we need is to give out specs, or throw in working diffs before
checking it (at least for major changes), bug fixes can be checked in as
they are found.

> I'll be honest--if this is the way you guys want this to work, then I
> can't be involved and I'll bow out.

Don't leave just yet, ok?