PORT <port-peer-review@bootstrap.org>
Summary? (6854)
High-level design approach needed to design and integrate collaborative tools (6858)
Presents some design principles (6867)
Presents some PORT requirements (6873)
Introduces tool context model (7408)
General comments? (6684)
Framework/methodology not precise, clear, easily applicable (6688)
Don't know of any that are (6693)
Other frameworks not cited (6704)
Why? (7380)
Most methodologies focus on lowest levels (7386)
Pragmatic methodologies at higher level hardly exist (7392)
Sentence on linking system processes (6739)
What does last part of second sentence mean? (6747)
Links increase complexity, which is not always desirable (7444)
Concept of "link" needs to be worked out (7455)
Typology of links useful for collaboratory evolution modeling? (7473)
Suggests primary importance of human processes, secondary importance of automatic tools (7941)
Practical (7951)
Temporary solution (7959)
Benefits of high-level methodologies for collaboratories? (6719)
Lead developers to new ideas (6728)
Ease integration of existing tools (6733)
Lens for focusing on missing links between models and methodologies (7425)
Makes it possible to identify gaps in socio-technical methods (7435)
Prerequisites for collaboration? (7915)
Some form of a common ontology (7919)
Useful in selecting right people to work on particular design problem (8032)
How to generate this automatically? (7926)
Need better forms of knowledge representation (7932)
How? (8005)
Stepwise approach (8000)
Paradigm change (8012)
Cannot be done; requires human negotiation (8023)