Hi Yasith, Thank you for this thoughtful and much-needed consolidation effort. The proposed repository structure and the cleanup plan you have outlined is very nice.
The refined grouping into middleware, portals, docs, custos securirty and domain-specific stacks like Cerebrum makes a lot of sense and will go a long way in improving discoverability, contributor onboarding, and long-term maintainability. Please try and preserve commit history and the strategic to archiving less active or empty repositories is good. Cheers, Suresh > On Jun 20, 2025, at 1:36β―PM, Jayawardana, Yasith <yas...@gatech.edu> wrote: > > Hello Everyone, > > After discussing with the Airavata community, the refined consolidation > structure is below. > > airavata - consolidating all airavata middleware development, including core > services and data related services. > airavata-portals - consolidating all frontends to airavata middleware. > airavata-docs - consolidating all airavata middleware and portal docs. > airavata-custos - consolidating all custos related backends and frontends. > airavata-cerebrum - consolidating all cerebrum related backends and frontends. > The repos can be cleanly consolidated with commit history intact. So I > propose to drop the empty airavata repositories and archive/drop the now > hanging repos upon consolidation. > > Best Regards, > Yasith > > -- > Yasith Jayawardana <yas...@gatech.edu <mailto:yas...@gatech.edu>> > Research Scientist, IDEaS > Georgia Institute of Technology - Atlanta, GA > From: Jayawardana, Yasith <yas...@gatech.edu <mailto:yas...@gatech.edu>> > Sent: Thursday, June 12, 2025 8:46:31 PM > To: dev@airavata.apache.org <mailto:dev@airavata.apache.org> > <dev@airavata.apache.org <mailto:dev@airavata.apache.org>> > Subject: Proposal to Consolidate Airavata Repositories > > You don't often get email from yas...@gatech.edu <mailto:yas...@gatech.edu>. > Learn why this is important <https://aka.ms/LearnAboutSenderIdentification> > > Hello Everyone, > > Currently, thereβs 22 airavata repositories scattered across the apache > organization, making it difficult for: > (a) contributors - to find repositories, read/updated the docs, and > contribute to. > (b) maintainers β to track dependencies, plan releases, and streamline > development and ci/cd. > > The current project structure (22 repositories) is as follows: > > π§ Core Services > airavata <https://github.com/apache/airavata> β Main microservices and > orchestration engine > airavata-custos <https://github.com/apache/airavata-custos> β Identity and > access management framework > airavata-mft <https://github.com/apache/airavata-mft> β Managed file transfer > services > π₯οΈ User Interfaces > airavata-django-portal <https://github.com/apache/airavata-django-portal> β > Primary reference UI > airavata-django-portal-sdk > <https://github.com/apache/airavata-django-portal-sdk> β SDK for custom > portal development > airavata-django-portal-commons > <https://github.com/apache/airavata-django-portal-commons> β Shared Django > utilities > airavata-cookiecutter-django-app > <https://github.com/apache/airavata-cookiecutter-django-app> β Starter > template for apps > airavata-cookiecutter-django-output-view > <https://github.com/apache/airavata-cookiecutter-django-output-view> β > Template for output views > airavata-custos-portal <https://github.com/apache/airavata-custos-portal> β > UI for Custos > airavata-php-gateway <https://github.com/apache/airavata-php-gateway> β > Legacy PHP gateway > π¦ Data & Metadata Services > airavata-data-lake <https://github.com/apache/airavata-data-lake> β Data lake > and storage backend > airavata-data-catalog <https://github.com/apache/airavata-data-catalog> β > Metadata and search services > airavata-mft-portal <https://github.com/apache/airavata-mft-portal> β Web UI > for file transfers > π Documentation & Branding > airavata-site <https://github.com/apache/airavata-site> β Project website > airavata-docs <https://github.com/apache/airavata-docs> β Developer > documentation > airavata-user-docs <https://github.com/apache/airavata-user-docs> β End-user > guides > airavata-admin-user-docs <https://github.com/apache/airavata-admin-user-docs> > β Admin-focused documentation > π§ͺ Research > airavata-sandbox <https://github.com/apache/airavata-sandbox> β Prototypes > and early-stage work > airavata-cerebrum <https://github.com/apache/airavata-cerebrum> β Airavata > for Neuroscience > Empty > airavata-jupyter-kernel <https://github.com/apache/airavata-jupyter-kernel> β > Jupyter integration > airavata-labs <https://github.com/apache/airavata-labs> β Experimental > projects > airavata-custos-docs <https://github.com/apache/airavata-custos-docs> β > Custos documentation > > Iβm proposing to consolidate these (and archive others), so that itβs easier > to discover, contribute, and maintain. > > Proposed repo structure (5 repositories): > apache/airavata β central place for job/experiment orchestration and resource > management code > airavata > airavata-data-catalog > [airavata-portal] β will be superseded by the new react portal in future > airavata-django-portal > airavata-django-portal-sdk > airavata-django-portal-commons > airavata-cookiecutter-django-app > airavata-cookiecutter-django-output-view > airavata-php-gateway > apache/airavata-custos β central place for authentication and authorization > related code > airavata-custos > airavata-custos-portal > apache/airavata-mft β central place for data transfer related code > airavata-mft > airavata-mft-portal > airavata-data-lake > apache/airavata-docs β central place for the landing page and docs (possibly > deployed in one location) > airavata-site > airavata-docs > airavata-user-docs > airavata-admin-user-docs > apache/airavata-cerebrum β airavata-backed sdks and utilities for neuroscience > airavata-cerebrum > > Empty repos to archive/drop: > airavata-labs > airavata-sandbox > airavata-jupyter-kernel > airavata-custos-docs > > I believe this consolidation would help maintain the project in the long term > and looking forward to your feedback. > > Best Regards, > Yasith > > -- > Yasith Jayawardana <yas...@gatech.edu> > Research Scientist, ARTISAN > Georgia Institute of Technology, Atlanta GA
