Home

Core Architecture Working Group

The Core Architecture Working Group is tasked with the following items.

Identifying functionality that should be migrated out of the core and into plugins.
Proposing code and process changes that will make it easier to upgrade and update the software while still allowing users the ability to heavily customize to their specific HPC sites needs.

The need to define what the ColdFront software considers its goal, and appropriate features for the "Core".
- Clearer guidelines on what would be accepted as PRs and process on how to submit, and who merges them.
What we might want to use as a core change review process.
The concept of implementing a version 2.0 to introduce the new breaking changes that will probably be needed to some key areas. With most or all future development on this version. Possibly with a stated commitment that this version will be easier for sites to pull updates from in the future.
- Identify main pain points with upgrading and work to address as part of this
  - Plugin architecture is a probable starting point - https://github.com/ubccr/coldfront/discussions/753#discussioncomment-14287367
  - Looking to use other extensible Django projects as a model for how to make extensible, https://github.com/netbox-community/netbox?tab=readme-ov-file
Expanding auth to support providers such as SAML2 and/or OIDC
Other items touched on
- Code Standards, a lot of work has already been done here recently
- Security and Accessibility - Standards, documentation, review
- Providing examples of a couple ways one might implement ColdFront for those new to HPC, or starting from scratch. i.e. explain a couple of the common PI - Project -Allocation models currently in use.