Skip to content

Commit

Permalink
Update aasc.mdx (#202)
Browse files Browse the repository at this point in the history
* Update references to architecture-as-code repo to point to the finos GitHub org.
* Point meeting minutes to the architecture-as-code repo
  • Loading branch information
rocketstack-matt authored May 29, 2024
1 parent 3c813ca commit 4a6d8b3
Showing 1 changed file with 6 additions and 6 deletions.
12 changes: 6 additions & 6 deletions docs/working-groups/aasc.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -7,16 +7,16 @@ sidebar_position: 4
"Architecture as Code" (AasC) aims to devise and manage software architecture via a readable and version-controlled codebase, fostering a robust understanding, efficient development, and seamless maintenance of complex software architectures.

## About this Working Group
The Architecture as Code Working Group is a forum for the discussion and coordination of the [Architecture as Code](https://github.com/finos-labs/architecture-as-code) Manifest and its associated projects. The group is open to all interested parties, and we welcome contributions from all members of the community.
The Architecture as Code Working Group is a forum for the discussion and coordination of the [Architecture as Code](https://github.com/finos/architecture-as-code) Manifest and its associated projects. The group is open to all interested parties, and we welcome contributions from all members of the community.

## Objectives

### Maintain the Architecture as Code Manifest
This Working Group is responsible for maintaining the [Common Architecture Language Model](https://github.com/finos-labs/architecture-as-code/tree/main/calm). The manifest is a collection of JSON schemas that defines the structure and content of a system architecture. The manifest is designed to be used as a single source of truth for the architecture of a system.
This Working Group is responsible for maintaining the [Common Architecture Language Model](https://github.com/finos/architecture-as-code/tree/main/calm). The manifest is a collection of JSON schemas that defines the structure and content of a system architecture. The manifest is designed to be used as a single source of truth for the architecture of a system.

The manifest is split into a core schema, the key elements required to define a system architecture, and domains, which are supplementary schemas that provide additional context and capabilities for a specific domain of the architecture such as security, deployment, data, etc.

For more details on how the manifest is structured, please see the [CALM docs](https://finos-labs.github.io/architecture-as-code/)
For more details on how the manifest is structured, please see the [CALM docs](https://finos.github.io/architecture-as-code/)

### Develop Architecture Capabilities
In addition to the manifest, the working group also oversees the development of key capabilities. A capability is the implementation of a key feature to support the architecture community such as:
Expand All @@ -25,7 +25,7 @@ In addition to the manifest, the working group also oversees the development of
* Drift detection tools
* Automated documentation generation

As this community is still in its infancy we are focusing on a few key capabilities to help evolve the manifest specification. To see what capabilities are currently being developed, to contribute or to propose additional capabilities please visit the [Architecture as Code Repository](https://github.com/finos-labs/architecture-as-code/).
As this community is still in its infancy we are focusing on a few key capabilities to help evolve the manifest specification. To see what capabilities are currently being developed, to contribute or to propose additional capabilities please visit the [Architecture as Code Repository](https://github.com/finos/architecture-as-code/).

### Advocacy
Raise awareness of the benefits and practicalities of Architecture as Code within the wider software development community. By engaging more professionals and organizations with this innovative approach to software design and architecture, we aim to advance the entire industry.
Expand Down Expand Up @@ -59,6 +59,6 @@ The Working Group is organised by . . .
## Meetings
Meetings of the working group are held on the fourth Tuesday of each month at 11am Eastern / 16:00 UK, and are open to anyone who would like to participate.

* [Upcoming Meetings](https://github.com/finos/devops-automation/issues?q=is%3Aopen+label%3Ameeting+label%3Aarchitecture-as-code)
* [Previous Meetings](https://github.com/finos/devops-automation/issues?q=label%3Ameeting+label%3Aarchitecture-as-code+is%3Aclosed)
* [Upcoming Meetings](https://github.com/finos/architecture-as-code/issues?q=is%3Aissue+label%3Ameeting+is%3Aopen)
* [Previous Meetings](https://github.com/finos/architecture-as-code/issues?q=is%3Aissue+is%3Aclosed+label%3Ameeting)

0 comments on commit 4a6d8b3

Please sign in to comment.