evegufy
commented
2 months ago Regarding product-portal-swagger isn't needed anymore according to @oyo .
Regarding forks: "Dev flow: change from forks in catenax-ng to own forks" introduction meeting with team was held on July 11, 2024. In essence, we’ll follow the usual way how to contribute after the catenax-ng are gone: https://github.com/eclipse-tractusx/portal-assets/blob/main/docs/developer/Technical%20Documentation/Dev%20Process/How%20to%20contribute.md
Regarding product-portal-tools: pgadmin4 has been move to https://github.com/catenax-eV/infrastructure-tools tdb: reportportal and jira tranfer scipt
Phil91
We need to to move out of the catenax-ng GH org:
Schedule: 14.06.2024 (EOB): Catena-X ng set to READ-ONLY 26.07.2024 (EOB): Catena-X ng will be DELETED
The READ-ONLY deadline doesn't apply to our team as a roadmap with the PCWM team to move out until the deletion deadline was defined.
Forks
https://github.com/catenax-ng/tx-portal-backend https://github.com/catenax-ng/tx-portal-shared-components https://github.com/catenax-ng/tx-portal-cd https://github.com/catenax-ng/tx-portal-assets https://github.com/catenax-ng/tx-portal-frontend https://github.com/catenax-ng/tx-portal-frontend-registration https://github.com/catenax-ng/tx-policy-hub https://github.com/catenax-ng/tx-ssi-credential-issuer https://github.com/catenax-ng/tx-ssi-authority-schema-registry
One option would be to replicate our current fork setup, which are mainly relevant for the contributors in our teams, in the CX Association GH Org, which would mean coordination work with the association at the same time it's also not the preferred solution by the them as is means administration efforts.
Other option: The question is also if we really need to replicate the current fork setup somewhere else of if it'd be an option that contributors in our team are working in personal forks, as normal contributors do.
Helper repositories
Regardless of the forks, we still need to find a solution for our helper repos: https://github.com/catenax-ng/product-portal-tools https://github.com/catenax-ng/product-portal-swagger
if we switch to personal forks, we should check if the documentation may should be enhanced and we should move the CI sonarcloud scan for the portal-backend to Tractus-X.