Bit Vizier Design Ideas

This is going to be a long post, but I'm trying to express my main concepts for Bit Vizier itself, and how I can leverage TurboGears to make Bit Vizier happen.

Why Not Launchpad?

samokk asked a very simple question: Why not Launchpad? After all, I get several advantages if I choose to use Launchpad:

1. It's already fully functional
2. It's written in Python
3. It's open source
4. It also seems to be heading in much the same direction that I'm looking to go with Bit Vizier.

I'd dabbled with the idea here and there, especially after hearing that they were doing some of the same things in Launchpad that I'm looking to do with Bit Vizier. So, I went to look at their instructions for getting a working Launchpad development environment working tonight, just to make sure I wouldn't be wasting my time with Bit Vizier.

So, What's The Difference?

I went to reply to a comment on my previous post about Bit Vizier, and realized that I was actually heading into a whole post in and of itself. The commenter had mentioned Ditz, and a spin off of it named Pitz. They have some very good ideas in there, and I'm likely to borrow heavily. However, they focus on distributed issue tracking, while I'm looking to focus on shared issue tracking.

So, as the title asks: What's the difference?

Announcing the Commencement of Bit Vizier Development

I was going to announce this about two weeks ago, but work suddenly kicked into high gear, and left me wishing for time to work on anything.

Considering this previous post of mine, seeing me announce something brand new has to seem more than slightly wrong. After all, why make a new item, rather than extend an existing one? How can I justify making Bit Vizier (AKA yet another issue tracker) when I just condemned making yet another framework?

Reflections on 1.0

I'm working with TurboGears a fair amount lately, so you might be expecting me to discuss TurboGears 1.0. I'm not. I'm talking about the general magic of seeing a program with a version number of "1.0".

Automated Testing and Why You Should Do It

I first learned about automated unit testing (in the style of extreme programming) about four years ago, and decided to experiment with it. I quickly found out that code I thought I had thoroughly debugged had errors in it. Since then, I've become quite fond of automated testing. While it's not perfect, it does help prevent some of the worst errors, such as the one that I saw happen today.

PyFlakes, Wingware, And PEP8

So, as Python developers, we all know about PEP8, right? But how easy is it to follow that standard? If you're like me, having a tool to help you check it is a good thing. Also, if you're like me, you use Wingware.

Why Not Roll Your Own Web Framework?

I was actually going to do a long series of "Why TurboGears, Why Not ___?", but have decided not to do so, especially since a couple of paragraphs will summarize my feelings on the others well. After that, though, I'll explain why you should almost never roll your own framework.

Why TurboGears Instead of Zope / Plone?

Zope and Plone are the most recent ones I tried to work with. I'm discussing them together because Plone is built on top of Zope, so it inherits any/all good (and bad) things from Zope.

So, why did I eventually abandon Zope and Plone?

So, Why TurboGears, Why Not ___ ?

I've decided to skip out on the "Why Linux?" question. If you have to ask, you won't agree with my answer. If you already agree with my answer, there's no point in preaching to the choir.

Instead, I'd like to address a simpler question, and one that is in some ways more important than the choice of OS, or choice of editor, or even choice of IDE. That question is the choice of which web framework to use.