Actualiser Zurich hackathon

Milovann Yanatchkov 2025-01-01 19:02:17 +01:00
parent fde6f1ff92
commit 2f2e9b069a

@ -2,7 +2,7 @@
# Exploring the future of design platforms for AEC # Exploring the future of design platforms for AEC
**Git<sup>AEC</sup>** was bootstrapped at the [AEC Hackathon Zurich](https://opensource.construction/events/aec-hackathon-zurich/) in 2024. **Git<sup>AEC</sup>** was bootstrapped at the **[AEC Hackathon Zurich](https://opensource.construction/events/aec-hackathon-zurich/)** in 2024.
## A Forge for AEC ## A Forge for AEC
@ -11,20 +11,19 @@ For more details on the project's origin, and the purpose of a forge for AEC, pl
## A Commit History ## A Commit History
One of the great feature of **Git** is the `commit` [history](https://about.gitlab.com/blog/2018/06/07/keeping-git-commit-history-clean/), which keeps tracks of every file changes. \ One of the great feature of **Git** is the `commit` **[history](https://about.gitlab.com/blog/2018/06/07/keeping-git-commit-history-clean/)**, which keeps tracks of every file changes. \
When working with text-based [native IFC](https://github.com/brunopostle/ifcmerge/blob/main/docs/whitepaper.rst) files, it's possible to view each stage of the modeling process. \ When working with text-based **[native IFC](https://github.com/brunopostle/ifcmerge/blob/main/docs/whitepaper.rst)** files, it's possible to view each stage of the modeling process. \
Here's an example of a single IFC model viewed at different moments in time : Here's an example of a single IFC model viewed at different moments in time :
* [Added model ifc](https://gitaec.org/brunopostle/creative-freedom/src/commit/b28fbd13d182fb78d4cc79dad1b390c92e1750af/model.ifc) * [Added model ifc](https://gitaec.org/brunopostle/creative-freedom/src/commit/b28fbd13d182fb78d4cc79dad1b390c92e1750af/model.ifc)
* [Added terrain, retaining walls, stairs and deck columns](https://gitaec.org/brunopostle/creative-freedom/src/commit/c367f58c307db840494b58b991115f13b3687679/model.ifc) * [Added terrain, retaining walls, stairs and deck columns](https://gitaec.org/brunopostle/creative-freedom/src/commit/c367f58c307db840494b58b991115f13b3687679/model.ifc)
See more [commit history](https://gitaec.org/brunopostle/creative-freedom/commits/branch/main) on the [revision graph](https://gitaec.org/brunopostle/creative-freedom/graph). \ See more **[commit history](https://gitaec.org/brunopostle/creative-freedom/commits/branch/main)** on the **[revision graph](https://gitaec.org/brunopostle/creative-freedom/graph)**. \
This is made possible thanks to [IfcMerge](https://github.com/brunopostle/ifcmerge). This is made possible thanks to **[IfcMerge](https://github.com/brunopostle/ifcmerge)**.
## An Automation System ## An Automation System
Git<sup>AEC</sup> enables CI/CD design pipelines like Speckle [Automate](https://speckle.systems/blog/automate-with-speckle/) \ Git<sup>AEC</sup> enables CI/CD design pipelines like **[Speckle Automate](https://speckle.systems/blog/automate-with-speckle/)** \
Samples of computations based on [IfcOpenShell](http://ifcopenshell.org/) and [Compas](https://compas.dev/#/) : Samples of computations based on **[IfcOpenShell](http://ifcopenshell.org/)** and **[Compas](https://compas.dev/#/)** :
* Automation [sample](https://gitaec.com/rvba/hackathon-zurich/src/branch/main/python/extract.py) in Python * Automation [sample](https://gitaec.com/rvba/hackathon-zurich/src/branch/main/python/extract.py) in Python
* Automation action [sample](https://gitaec.com/rvba/hackathon-zurich/src/branch/main/.forgejo/workflows/update.yaml) and [logs](https://gitaec.com/rvba/hackathon-zurich/actions) * Automation action [sample](https://gitaec.com/rvba/hackathon-zurich/src/branch/main/.forgejo/workflows/update.yaml) and [logs](https://gitaec.com/rvba/hackathon-zurich/actions)
@ -32,16 +31,16 @@ Samples of computations based on [IfcOpenShell](http://ifcopenshell.org/) and [C
## Use Git>AEC ## Use Git>AEC
* The simplest way to run Git<sup>AEC</sup> is to use the [Docker image](https://gitaec.org/rvba/-/packages/container/gitaec/latest). * The simplest way to run Git<sup>AEC</sup> is to use the **[Docker image](https://gitaec.org/rvba/-/packages/container/gitaec/latest)**.
* Learn how-to run and deploy a [container](https://en.wikipedia.org/wiki/Containerization_(computing)) from [docker.com](https://www.docker.com/) * Learn how-to run and deploy a **[container](https://en.wikipedia.org/wiki/Containerization_(computing))** from [docker.com](https://www.docker.com/)
## Build Git>AEC ## Build Git>AEC
* **Source code** of Git<sup>AEC</sup> is available on the `gitaec` branch of the **[forgejo repo](https://gitaec.org/rvba/forgejo/src/branch/gitaec)**. * **Source code** of Git<sup>AEC</sup> is available on the `gitaec` branch of the **[forgejo repo](https://gitaec.org/rvba/forgejo/src/branch/gitaec)**.
* Visit the **Forgejo** [documentation](https://forgejo.org/docs/next/contributor/from-source/) for details on how-to build the platform from source. * Visit the Forgejo **[documentation](https://forgejo.org/docs/next/contributor/from-source/)** for details on how-to build the platform from source.
## Contribute to Git>AEC ## Contribute to Git>AEC
Git<sup>AEC</sup> is developed by [Milovann Yanatchkov](https://rvba-fr.translate.goog/my.html?_x_tr_sl=fr&_x_tr_tl=en&_x_tr_hl=fr&_x_tr_pto=wapp). \ Git<sup>AEC</sup> is developed by **[Milovann Yanatchkov](https://rvba-fr.translate.goog/my.html?_x_tr_sl=fr&_x_tr_tl=en&_x_tr_hl=fr&_x_tr_pto=wapp)**. \
📨 Send a mail to `contact` at `gitaec.org` to join the development platform or for hosting services. 📨 Send a mail to `contact` at `gitaec.org` to join the development platform or for hosting services.