[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#187920: RFP: steam -- Environment for cooperative knowledgemanagment



Package: wnpp
Version: N/A; reported 2003-04-07
Severity: wishlist

* Package name    : steam
  Version         : 1.3.5
  Upstream Author : Thomas Bopp <astra@upb.de>, Ludger Merkens <balduin@uni-paderborn.de>, many others
* URL             : http://www.open-steam.org/
* License         : GPL
  Description     : Environment for cooperative knowledgemanagment

 sTeam provides a technical platform which allows groups of students,
 lecturers and any other groups to construct and arrange their individual
 and cooperative learning and working space.
                                       .
 sTeam consists of a server with an object database and Web, Java and
 other (ftp, irc, ...) clients. The server is event-driven and manages
 all user objects as well as the communication among the connected clients.
                                       .
 Different from most other content managment tools is the novel
 possibility of self-organisation and self-administration by the members
 within the virtual environment as well as a focus on combining
 asynchronous and synchronous communication
                                       .
 In the core, the system provides the following self-administrating
 functions to every user:
                                       .
     * creation of areas and groups
     * granting of access authorisations
     * carrying objects and passing them on to other users
     * use of areas as cooperative media (e.g. chat room, shared whiteboard)

the sTeam project includes the server and webinterface,
java clients (whiteboard, chat, application launcher)
and java, php, c/c++ and pike client libraries.


server and webinterface are already debianized (build straight out of
our cvs) and only need some policy checking.

use of the server does not depend on or share code with the clients so
they can be packaged independently by different people.

greetings, martin.




Reply to: