approving messages

[Brian Behlendorf <br...@apache.org>]

So I've been moderator-approving lots of messages to this list recently
from what appear to be non-subscribers who downloaded the distribution and
are looking for support queries.  I am working on getting a bug database
up (anyone who wants to help write a servlet-based bug database, please
contact me privately), so I figure this is a short-term situation.
However, it occured to me that you might want someone other than me acting
as the "moderator", so if it's a question that's already been asked, you
could answer it directly rather than rebroadcasting the question over and
over to the tomcat-dev mailing list.  It appears to be 4-10 messages/day
of this nature.  Does anyone want to take on this task?  If not, should I
just allow non-subscribers to post to the list?

	Brian

Re: approving messages

[Co...@eng.sun.com]

> of this nature.  Does anyone want to take on this task?  If not, should I
> just allow non-subscribers to post to the list?

I think it would be a good ideea - the only problem is the spam, but everyone

gets it anyway.

Costin

RE: approving messages

[GW Estep <GW...@riva.com>]

Any reason not to user GNATS as the foundation of this?  I just started
looking for this type of product for our internal development efforts and
came across GNATS which seems to have a lot if not all of the functionality
we need.

Just wondering,

GW

-----Original Message-----
From: pascal@field.videotron.net [mailto:pascal@field.videotron.net]On
Behalf Of pascal.forget@videotron.ca
Sent: Tuesday, January 04, 2000 7:23 PM
To: tomcat-dev@jakarta.apache.org
Subject: Re: approving messages


Hi Brian,

> I am working on getting a bug database up (anyone who wants to
> help write a servlet-based bug database, please contact me
> privately), so I figure this is a short-term situation.

I'd be glad to help.

A little background: I'm a Sun certified java programmer, and
I am familiar with JSP (0.92) and servlets (2.0).  I've been
developing server side Java on Apache/Linux full time for the
last two years.

I was planning on writing a to-do list program for the team I
lead at work using Apache+Java+JSP+JSDK.  Basically, a bug is
simply a kind of to do item.  A to do item has a priority
(High, Low, None), is attached to a project, is assigned to
a developer, has a status (done, in progress, etc.), and
either has an expected completion date or is attached to
a deliverable or milestone.  Each to do item also has a
title, a short description, and a comments field for the
developers.

Say you have a prototype or beta software being tested by
clients or the open source community; they fill bug reports,
which are entered into the system but not assigned to any
developer.  The project leader then inspects the new entries
in the list, sets a priority and assigns responsibility to
a developer or to a group of developers.  Each developer
consults his to do list where he/she sees his tasks, with the
higher priorities first.

I wrote such a system, but client/server and on NextStep ages ago.
It was simple, it worked, and it really helped the developers
be more productive by focusing on the important tasks.  Each
morning we'd get in, fire up the to do list application, and
start working on the task that appeared on top of the list.

In a future version I'll also add the capability to enter
time spent on each task, because right now at work they
have us fill in Excel spreadsheets for timesheets and that
sucks.

Anyway if you'd like me to work on the bug database, send me
an email!  I'd like to know what type of solution you had
envisioned, especially for the backend (JDBC? Object
serialization? etc?)

Cheers,

Pascal Forget
pascal.forget@videotron.ca

---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org

Re: approving messages

[pa...@videotron.ca]

Hi Brian,

> I am working on getting a bug database up (anyone who wants to
> help write a servlet-based bug database, please contact me
> privately), so I figure this is a short-term situation.

I'd be glad to help. 

A little background: I'm a Sun certified java programmer, and
I am familiar with JSP (0.92) and servlets (2.0).  I've been
developing server side Java on Apache/Linux full time for the
last two years.

I was planning on writing a to-do list program for the team I
lead at work using Apache+Java+JSP+JSDK.  Basically, a bug is
simply a kind of to do item.  A to do item has a priority
(High, Low, None), is attached to a project, is assigned to
a developer, has a status (done, in progress, etc.), and
either has an expected completion date or is attached to
a deliverable or milestone.  Each to do item also has a
title, a short description, and a comments field for the
developers.

Say you have a prototype or beta software being tested by
clients or the open source community; they fill bug reports,
which are entered into the system but not assigned to any
developer.  The project leader then inspects the new entries
in the list, sets a priority and assigns responsibility to
a developer or to a group of developers.  Each developer
consults his to do list where he/she sees his tasks, with the
higher priorities first.

I wrote such a system, but client/server and on NextStep ages ago.
It was simple, it worked, and it really helped the developers
be more productive by focusing on the important tasks.  Each
morning we'd get in, fire up the to do list application, and
start working on the task that appeared on top of the list.

In a future version I'll also add the capability to enter
time spent on each task, because right now at work they
have us fill in Excel spreadsheets for timesheets and that
sucks.

Anyway if you'd like me to work on the bug database, send me
an email!  I'd like to know what type of solution you had
envisioned, especially for the backend (JDBC? Object
serialization? etc?)

Cheers,

Pascal Forget
pascal.forget@videotron.ca