Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Office Hours - 2024-10-31 #542

Open
5 tasks done
rocketstack-matt opened this issue Oct 31, 2024 · 13 comments
Open
5 tasks done

Office Hours - 2024-10-31 #542

rocketstack-matt opened this issue Oct 31, 2024 · 13 comments

Comments

@rocketstack-matt
Copy link
Member

rocketstack-matt commented Oct 31, 2024

Date

Thursday, 31st October, 15:30 GMT

Meeting notices

  • FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

  • All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

  • FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact [email protected] with any questions.

  • FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

Office Hours is a meeting for maintainers to get together to discuss active development and upcoming priorities.

Zoom info

Join Zoom Meeting

Github Repo: https://github.com/finos/architecture-as-code/

Project Board: https://github.com/orgs/finos/projects/98

Mailing List: Email [email protected] to subscribe to our mailing list

Mailing List: Email [email protected] to subscribe to our mailing list

@rocketstack-matt
Copy link
Member Author

@willosborne
Copy link
Member

Will Osborne / Morgan Stanley

@rocketstack-matt
Copy link
Member Author

Matthew Bain / Morgan Stanley

@LeighFinegold
Copy link
Member

Leigh Finegold / Morgan Stanley

@aidanm3341
Copy link
Member

Aidan McPhelim / Morgan Stanley

@jpgough-ms
Copy link
Member

Jim Gough @jpgough-ms

@dc-ms
Copy link
Member

dc-ms commented Oct 31, 2024

Denis Coffaro / Morgan Stanley

@rocketstack-matt
Copy link
Member Author

rocketstack-matt commented Oct 31, 2024

Minutes

  • Reviews last weeks minutes
  • Demo of Calm Hub Initial Prototype #543
    • Intent would be to run CH in a multi-layer model (local, firm wide, global) which would be chained together enabling architects to work locally, organisations to publish private artefacts and also to be able to fetch publicly visible artefacts.
    • Key foundation for building UI, Authoring Tools, etc.
    • Request to review the Issue and suggest additional features folks think would be useful.
    • CH built in Java / Quarkus
    • Intent is to get the foundation in place with good testing and something folks can then build on.
    • Demo of Swagger API:
      • Namespaces (allows patterns / architectures / etc. to be grouped, would be key to the chaining of hubs)
      • Patterns
      • Core Schemas
    • React App:
      • Building a UI in parallel
      • Both the CALM Hub and the UI will be bundled together into an image
    • How will we handle remote / chained hubs?
    • How do we handle clashing namespaces?
    • Aim to get initial PR submitted in the next week or so.
  • UI Update
    • Working group has formed and had initial meeting
    • @dc-ms raising initial issues from that call
    • Reviewed existing UI frameworks
    • Discussing design aspects and user personas
    • What are the dependencies for the UI dev to get started?
    • Dependency on ensuring we are able to validate documents before attempt to visualise. Ties to CLI currently only being able to validate 2024-04 version
    • Make sure we run the UI meetings on the Office Hours Zoom to anyone can join

Actions

  • @rocketstack-matt to update Office Hours meeting template with correct Zoom details
  • Request Docker Hub setup for CALM Hub images
  • Request AWS setup to host CALM Hub central process
  • @rocketstack-matt / @dc-ms - follow up from @karlmoll on getting CALM promoted out of incubating to help pull extra external contribution
  • @rocketstack-matt to raise an issue about keeping 'testable artefacts' along side the CALM drafts, we would expect the CLI test framework to be able to validate each of these; if a draft / release version exists in the calm project then the CLI should be able to validate them
  • Everyone, please pick up at least one issue from the project board to complete in the next week

@DorothyEwuah
Copy link

Dorothy Ewuah / Turntabl

@abdul-kassim
Copy link

Abdul Faheem Kassim / Turntabl

@YoofiTT96
Copy link

Joseph Yoofi Brown-Pobee / Turntabl

@Elisha-Veve
Copy link

Elisha Amenuveve | Turntabl

@Adwoa-Konadu-Appiah
Copy link
Contributor

Konadu Appiah / Turntabl

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests