Urban Versioning Systems 1.0 JEANETTE LIN, lin.je@husky.neu.

edu

CH.01 CH.02 CH.03 CH.04 CH.05 CH.06 CH.07 CH.08 CH.09 CH.10 CH.11 CH.12 CH.13 CH.14 CH.15 CH.16 CH.17 CH.18 CH.19 CH.20 CH.21 CH.22 CH.23 CH.24

CH.24 CH.23 CH.22 CH.21 CH.20 CH.19 CH.18 CH.17 CH.16 CH.15 CH.14 CH.13 CH.12 CH.11 CH.10 CH.09 CH.08 CH.07 CH.06 CH.05 CH.04 CH.03 CH.02 CH.01

URBAN VERSIONING SYSTEM 1.0 Matthew Fuller, and Usman Haque

1. Text Summary and Analysis In the article Urban Versioning System 1.0 the authors provide a preamble for a better understanding of the computer impacts on the architectural discipline in the form of design aids. Eventually these computers will increasingly be part of the architecture itself by enabling user-centered interaction systems to configure enviornmental conditions. The authors then focused on lessons that can be learned for architecture from computing or the way in which software is made by focusing on FLOSS and proposing seven constraints to creating the open source architecture software. The first point the authors touch upon is the current most significant mode of software development: Free, Libre and Open Source Software (FLOSS). FLOSSs basic principles states: 0.0 The freedon to run the program, for any purpose. 0.1 The freedon to study how the program works, and adapt it to your needs. 0.2 The freedom to redistribute copies so you can help your neighbor. 0.3 The freedom to improve the program, and release your improvements to the public, so that the whole community benefits. To relate to architecture, the authors point out the source is the drawings and open is the way it is designed or produced. The goals to consider for this propose opensource platform are enabling non designers to participate more closely in the design and construction process and formulating the frameworks for the spatial design. By setting these two approaches the authors

introduces seven constraints to consider for the design. The constraints are: 01Build rather than Design, 02 Materials must come pre-broken, 03 Make joints, 04 Rubbish is the Root of Virtuoisty, 05 Collarborate with Collaborators, 06 Copying or not Copying is Irrelevant, and 07 01 Build Rather than Design: Because it is assumed that building (construction) only begins once the design process is complete. To abandon this assumption, desinging, planning and types of brainstorming are abandoned and only thinking about construction first. 02 Materials Must Come Pre-Broken: Not everything can live forever and everything has its own life span. Broken artefacts encourage reuse and repurposing because any cracks or broken areas provides a heightened sense of individual reponsibiltiy and technical audactiy which enables people to participate. 03 Make Joints: For software to function fully it is necessary for it make joints outside such as interfaces, protocols, interpreters, compilers and screens to integrate with other platforms. 04: Rubbish is the Root of Virtuoisty: There are glitches or errors or bugs of platoforms and codes. However these are not rubbish as the authors call it but a chance for the program to fix it self and better make amendments to better accompany the user. 05 Collarborate with Collaborators: Rivarly companies find themselves working on the same project however if the company who are at least nomi-

nal rivarly with each other may build their businesses around sharing codes. By using shared codes it allows companies to develop alternative platforms to propretary software for market shares. 06 Copying or Not Copying is Irrelevant: Copying and not copying is irrelevant because of the DoIt-Yourself concept is applied. It doesnt matter if the program is copied because the user itself created it to be suitble and user friendly for itself. 07 Property Must be Invented: The authors proposes a capitalism or a way to controll the distribution of the programs. It is better to have full list of rules of property or ownership of the program. By examining the constraints of producing an open source software it allows the user and developers the insights of how a FLOSS program is produced.

CH.01 CH.02 CH.03 CH.04 CH.05 CH.06 CH.07 CH.08 CH.09 CH.10 CH.11 CH.12 CH.13 CH.14 CH.15 CH.16 CH.17 CH.18 CH.19 CH.20 CH.21 CH.22 CH.23 CH.24

CH.24 CH.23 CH.22 CH.21 CH.20 CH.19 CH.18 CH.17 CH.16 CH.15 CH.14 CH.13 CH.12 CH.11 CH.10 CH.09 CH.08 CH.07 CH.06 CH.05 CH.04 CH.03 CH.02 CH.01

URBAN VERSIONING SYSTEM 1.0 Matthew Fuller, and Usman Haque

2.Questions and Challenges 1. What is FLOSS? and the principles? 2. What is the definition of open source? 3. What are the constraints that the author introduced as a set of guidelines to consider when developing a software? 4. What are the main key points of the constraints discussed?

3. Documentation of Responses