* [11/25/01 23:45] Of all the gin joints in all the towns in all the world,
* Sean 'Shaleh' Perry <[EMAIL PROTECTED]> walks into mine and says:
> My goals for blackbox are as follows:
>
> infrastructure:
> have a current and updating website
> a bug tracker so that we do not rely on the memory of this mailing list
Definitely a good idea. I'd like to add to that list a publicly accessible
CVS repository, ideally with a cvsweb-cgi front end or what have you.
> a place for patches that are waiting to be applied
>
> code:
> once we know the current bugs we need to decide which of them can be fixed and
> which of them require a redesign or rewrite. Ones that can be fixed will. I
> suspect bb will fork and there will be the tried and true one we have now,
> slowly having its holes plugged as well as a development branch.
>
Shaleh, I don't rememeber if you were in the channel when we had this
same discussion in #blackbox, but kyle and myself and a few others have
started a pretty comprehensive list of things that NEED to be done for a
stable, updated blackbox. I send this to the list because most of the
people in #blackbox have long-since unsubscribed from this mailing list.
Please check with kyle in #blackbox, as he's the current keeper of the
list.... =:)
> Currently there is myself and two others involved. We all have been here a
> long time and believe in the current blackbox approach. You will not see lots
> of crazy new features. let waimea and fluxbox handle that.
Amen and hallelujah. Please include me in the list of interested
parties and need-to-know-during-code-writing's, since internal changes to
blackbox will affect bbkeys as well as all of Kennis's bbtools.
>
> As soon as the todo list is more substantial the people on this list become
> aware of it.
See above. =:)
--
----%<----------%<----
Jason Kasper (vanRijn)
bash$ :(){ :|:&};:
Numbers 6:24-26
