Giters

rhughes42 / osc-org

Open-source construction organisation repo.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

This document outlines the core activities of the os.construction initiative. The activities are clustered in three chapters:

  • communication
  • events
  • project facilitation

Goals 2024

deliverables

  • number of project stories published (6) / online meet ups (linking individuals with existing projects)
  • local chapter: one event in each country (Denmark / Germany / UK)
  • membership structure established (individual 99, basic , gold, platinum)
  • 50 paying members in 2024
  • funds raised to allow for 20% FTE, maintenance of website, templates and other research commitments

exposure

  • number of followers (today 1'200 on linkedin & 450 on email list >>> 3'000 on linkedin & 1'000 on email list)
  • website hits: xxx

facilitation

  • number of bootcamps & clusters (5)
  • 3 templates for existing projects on opensource.construction github live and maintained

communication

objectives

create a place where stakeholders from the real estate and construction industry can self-inform themselves about the what, why and how of open source solutions

activities

we provide

  • text about os in general
  • project insights from industry specific collaborations of AECO organisations and os solutions
  • links to valuable resources
  • short intros to all things open source on linkedin

we think about further activities

  • tech radar

maintenance

the goal is to have one new text or project story published every month – open call and on the website and through linkedIn

project "foundation"

project "Linkedin"

  • we use personal accounts for posts and repost with os.construction account
  • templates for posts (visuals) develop over time

project "templates" (Yashar)

  • CI/CD, unit testing, how to use git
  • notebook with compas and sample project
  • updates? done by the maintainer of the template
  • support? github issues
  • monetization > service for integration into individual tech stacks next steps:
  • define templates (speckle, thatopencompany, compas)

project "Data Management for AEC Professionals" (Max)

https://docs.google.com/document/d/1jDg9FZw5zTEpOzjjWpPd0i4izGALYIJKuyGYE_RFfHo/edit?usp=sharing

mark down & github pages involving further actors: BuildingSmart / AIT

project "FAQ" (Thorben)

mark down file to collect content reference: https://openjsf.org/about

to dos: links

  • make a list of interesting links
  • define visually attractive way to present links
  • next step: 1. collect open questions 2.answering individually

project "collaboration profile" (Max)

project "stories" (Lukas F.)

  • simple coda structure to collect organisations and technology which is used (View 1: Organisationen (mit welcher Tech arbeiten sie?) / View 2: Technology solutions (welche Organisationen arbeiten mit der Technologie?)

  • entry organisation: name of organisation / website / contact person (mail) / tools they use / one description field (max.2000 / three guiding questions: motivation / three key take aways from working with open source solutions)

  • entry tool: name of organisation / website / contact person (mail) / problem they adress / one description field (max.2000 / three guiding questions: problem adressed / licence model / about the team)

  • vision: case studies with interviews and videos, project based financing

  • idea: short video to introduce people (only one question: introduction + motivation)

  • open responses (abstract / phoenix3d / speckle)

  • old project brief: https://docs.google.com/document/d/16Sg_zUKv6IMSYERHd8TGpSp9rsZBa7zWRt5YlcuByHE/edit#heading=h.5e60ddgpw6zy

ideas: tech radar

references

to dos: general updates to website

  • add core team
  • adapt registration for courses
  • update structure (more pictures from events / add service section)
  • FAQ (Offerte einholen)
  • SEO optimization
  • Download WhitePaper mit Angaben credentials
  • language: ideal https://www.weglot.com/ 150 bwz. 290 im Jahr /// sonst https://wpml.org/purchase/

events

objectives

The aim of our events is to give those who design, build and maintain our built environment the opportunity to work with cutting-edge technologies and their developers. We want to achieve a good mix of students and professionals, non-coders and coders. The focus is on cooperation between the participants, breaking down fears of contact and building up the energy that is generated during such a hacker weekend.

activities

hackathon

07.-09.2025 Hackathon Zurich Link to description: hackathon

potential collaboration with TUM (Yashar)

  • credit points for students
  • collaboration with TU Dresden, Berlin, Uni Stuttgart
  • focus on Symposium / focus on entire event
  • our role: creating awareness for open source / growth hacking for opensource.construction

lectures

  • 07.03. session light+building Frankfurt
  • 08.04. construction summit Hamburg
  • 19.04. Input HSLU
  • Webinar Bimondis
  • tbd Universität Liechtenstein

community events

Copenhagen:

open source & sustainability OKNF / architecture office / Victor (SHL) / AI and open source (Stjepjan) / openBIM university guy (too nerdy?)

London:

Intro event with Foundation (making open collaboration successful) & Organisation OSPO (os pyramid > open source, inner source, closed source) & Hypar (why open source) Hackathon? sponsorship by Genssler: list of arguments (saving costs on maintenance / attracting talent / os.c as platform to take the first steps and get visibility by doing so)

project facilitation

objectives

Making open collaboration successful

activities

maintenance

blackboard

Link to description: blackboard

budget

  • update to budget and potential new partnerships

Link to description: texts Link to description: project stories

About

Open-source construction organisation repo.