planning

[Susanne Lefvert]

Things I have thought about regarding AG2.0:

Collaboration:
-------------
* Develop a test plan.  Suggestion:
 1 Have a strict cvs stop
 2 Test code in cvs according to well defined test scenarios
 3 If code is error free, stop! Else do step 4 and 5.
 4 If bugs are found, commit fixes to cvs after all tests are done
 5 Go back to step 1

* Regular meetings, maybe once a week.

Application issues:
------------------
* Personal data and data storage
* Follow needs locks
* Lead protocol? Should we implement lead?
* Use other text tool or include more functionality in current chat?
* Refactor VenueClient - Should all non ui code be in 
AccessGrid/VenueClient
(personal data storage, simple text processor, personalNodeManager etc)
* Refactor VenueManagement (Add and ModifyVenue methods). One idea would 
be to include static streams and encryption options in server calls and
not call individual venues from VenueManagement.  The VenueDescription now
includes streams and encryption so it shouldn't change the current
interface but would make code in VenueManagement cleaner.


User interface issues and things to do:
--------------------------------------
* What is the difference of a node service, application service, and a
service.  This seem to be very confusing for users/developers.  Could we
change the names somehow?
* Should we put exits in the tree or is current solution fine?
* In some places we have programmer terminology in the ui
(servicemanager, passphrase etc), could be good to use normal text
instead.
* Implement the dock
* Implement option to add administrators for venues in Venue Management
* Be able to rename exits in Venue Management
* Default venue indicators
* Where should manual files point to? Currently pointing to my public_html
* Be able to tear off dock and text chat
* Add access control to ui

-- Susanne


On Thu, 5 Jun 2003, Ivan R. Judson wrote:

> 
> Hey,
> 
> Next week we're going to be dealing with our planning for 2.1, I'd like
> folks to provide lists of what they think is missing or needs to be fixed
> (or started) to make AG2.X better, faster, cheaper, more widely used, etc.
> 
> Please send lists by Friday afternoon.
> 
> --Ivan
> 
>