Editing Open-Source Architecture Community
From Wiki.OSArch
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone. Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 13: | Line 13: | ||
The architecture, engineering, construction, and building operations industry has a large, systemic problem with its ability to collaborate digitally. The digital ecosystem largely consists of isolated digital silos, where each tool does not integrate well with other tools by design. Behind these tools are a small selection of monopoly software vendors with predatory business practices, forcing [https://www.gnu.org/proprietary/proprietary-incompatibility.html proprietary incompatibility], [https://www.gnu.org/proprietary/proprietary-obsolescence.html proprietary obsolescence], and [https://www.gnu.org/proprietary/proprietary-subscriptions.html proprietary subscriptions] onto users. There is also a lack of training material and knowledge sharing around digital standards. These problems enforce a culture onto the industry that our ability to manipulate the data about our built environment relies on what vendors who provide off-the-shelf software allow us to do. Resources are wasted on building workarounds and an ecosystem on top of this proprietary foundation, instead of focusing on what matters: working together to make a better built environment. | The architecture, engineering, construction, and building operations industry has a large, systemic problem with its ability to collaborate digitally. The digital ecosystem largely consists of isolated digital silos, where each tool does not integrate well with other tools by design. Behind these tools are a small selection of monopoly software vendors with predatory business practices, forcing [https://www.gnu.org/proprietary/proprietary-incompatibility.html proprietary incompatibility], [https://www.gnu.org/proprietary/proprietary-obsolescence.html proprietary obsolescence], and [https://www.gnu.org/proprietary/proprietary-subscriptions.html proprietary subscriptions] onto users. There is also a lack of training material and knowledge sharing around digital standards. These problems enforce a culture onto the industry that our ability to manipulate the data about our built environment relies on what vendors who provide off-the-shelf software allow us to do. Resources are wasted on building workarounds and an ecosystem on top of this proprietary foundation, instead of focusing on what matters: working together to make a better built environment. | ||
| − | The OSArch community aims to solve this problem, by providing support for a community and ecosystem of software that respects the digital freedom of the industry and its users. This digital freedom allows collaboration to occur, and is increasingly important as the industry and next generation of digitally savvy professionals leave academia to join us in our journey to improve the built environment. In particular, we help support four types of digital freedom | + | The OSArch community aims to solve this problem, by providing support for a community and ecosystem of software that respects the digital freedom of the industry and its users. This digital freedom allows collaboration to occur, and is increasingly important as the industry and next generation of digitally savvy professionals leave academia to join us in our journey to improve the built environment. In particular, we help support four types of digital freedom: |
# The freedom to use software as you wish for any purposes, whether it be educational, commercial, R&D, in any context with no time limit, no arbitrary vendor restrictions, or any other rules governing your usage. | # The freedom to use software as you wish for any purposes, whether it be educational, commercial, R&D, in any context with no time limit, no arbitrary vendor restrictions, or any other rules governing your usage. | ||
| Line 20: | Line 20: | ||
# The freedom to distribute copies of your modified versions to others. By doing this you can give the whole community a chance to benefit from your changes. | # The freedom to distribute copies of your modified versions to others. By doing this you can give the whole community a chance to benefit from your changes. | ||
| − | A precondition to provide these four freedoms is to ensure that we are able to do all the work we need to do in the AEC industry using open source software | + | A precondition to provide these four freedoms is to ensure that we are able to do all the work we need to do in the AEC industry using open source software. Access to, and the freedom to change this code empowers and puts the users (that's you!) in control over the data in the built environment, instead of vendors. |
== How OSArch supports the AEC industry == | == How OSArch supports the AEC industry == | ||
