Re: [VANILLA-LIST:2585] Netrek Client Packaging Survey

[Bob Tanner <tanner@real-time.com>]

Quoting James Cameron (quozl@us.netrek.org):
> Do you think the client (COW 3.00) is ready for distribution to the
> freshmeat driven Linux newbie community, or should we at least make a
> few minor changes first to increase acceptance?

This is Kurt's call, but I think we need a bugzilla setup before releasing it
to the freshmeat/slashdot people.

1. I think a bug-tracking would lend credibility to the software.

2. Our jobs would be easier, we would not have to alter the PROJECTS file, or
manually track the bug. Bugzilla would do it for us.

3. Bugzilla would keep the users informed. As bug flows through the developers,
any changes would be automatically sent to the developers AND the submitter of
the bug. It makes the user feel important.

4. Finally, we can share the bugzilla with any netrek projects (heck any open
source projects).

I'd be willing to house the bugzilla database at Real Time
(http://bugzilla.us.netrek.org?)

Just my thoughts.  More info on buzilla at http://www.mozilla.org/bugs/

> Which of the following should be done before first release?
> Please mark "yes" or "no" for each.
> Read on for explanations.
> 
>     - gnome menu entries,
> 	- netrek newbie manual,
yes

> 	- netrek client,
yes

> 	- netrek web site,
yes

>     - netrek client features,
> 	- splash welcome,
yes, simple to do

> 	- first time warning to read newbie manual,
YES!

> 	- metaserver list (GTK),
Next release.

> 	- twink buttons (GTK),
Next release.

> 	- menu bar (GTK),
Yes.

> 	- tooltips (GTK),
Next release.

> 	- orphan keystrokes bound to tactical window,
Yes.

> 	- .xtrekrc editor.
Yes.

>     - metaserver window,
> 	- indicate acceptance of selection,
Yes.

-- 
Bob Tanner <tanner@real-time.com>       | Phone : (612)943-8700
http://www.real-time.com                | Fax   : (612)943-8500
Key fingerprint =  6C E9 51 4F D5 3E 4C 66 62 A9 10 E5 35 85 39 D9