Hi,

> > A list isn't a good solution, nobody is going to read a list and the
> > people that are doing the work aren't going to recieve their due credit.
> > View the following page and click on the colored things, replace the 
> build
> > information with reports on snippets, features, who is writing them, 
> state
> > of development, anticipated completion dates, etc.
> > http://community.roxen.com/developers/autobuild/pike71.html
> 
> While it gives me great ideas for representing nightlybuild reports, I 
> have a hard time envisioning what you are proposing. Perhaps I need to 
> get a clearer view first.


If you'd learn to read my mind, I wouldn't have to be explicit. :)

Those build reports give the reader a great deal of information in a
compact environment.

I am attempting to define a solution to several Requirements; credit where
it's due, state of the project, contact information, everything in one
interface, marketing, development organization, etc.

I want an interface that tells me:
* Feature; Repligard
* Start date
* Projected completion date
* Author
* Author contact
* Sponsor for the feature, if Aurora is paying to have this developed and
I am Aurora, I want everyone to know.
* Description of the feature or application
* If application, license statement
* Report of progress and issues that concern development
* Link to documentation

I want everything in one interface. I want to know everything that's
being worked on, who is working on it and its state of developement;
alpha, beta, stable. If I'm a writer, I will go to this interface and
examine the documentation. If I'm a user, I'll go to this interface to
learn how to use the feature...this would probably just be a link to
documenation (Commentext?). :)

If we use a seperate list of sponsors, nobody is going to read the list.
It's not interesting information. If everythign is in one well designed
interface, all this information becomes useful and interesting.

This is the interface that prospective users will visit to determine
whether we have an active healthy project and developers will use to keep
current on the seperate parts of the project.

Ron


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to