"Andreas J. Koenig" wrote:
>
> I'd suggest to workinggroupize and pumkingify the development system.
> Well, thia apparently has happened already. You should be the first
> pumpking unless you can name a candidate that is willing and able to
> take that role.
OK, short of any other suggestions, I'll do it for the forseeable.
Does that mean I get a job/pumpking description Nat ?-)
'Perlbug tracking' or 'Perlbugtron development' or ...?
???
On a similar theme, I was going to enquire about an authoritative(?)
namespace for the perlbugtron (or whatever it should/will be called,
to sit under, assuming the current system is developed.
At the moment it's called Perlbug, that is, it's mostly a bundle of
modules under a Perlbug/ directory with a load of sub modules:
Perlbug::Base
Perlbug::Cmd
Perlbug::Config
Perlbug::Email
Perlbug::Fix
Perlbug::Log
Perlbug::Ticket
Perlbug::Web
etc.
Historical context for the name:
It used to be called PbDb, but that is easily confusable with a debugger.
Tron means nothing in particular on it's own.
Perlbugtron everyone knows it by this name, but might be too long.
Perlbug (note the capital 'P' :) is just short enough and descriptive.
Any other suggestions, should we stick with Perlbug, or ...?
Ciao
Richard Foley
---
[EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL PROTECTED]
'Ciao' - shorter than 'Aufwiedersehen'
