[REPOSITORY] New UI Repositories

[sarbull]

Name

egeria-ui-core, egeria-ui-components

Owner

sarbull

Deliverable

• common functionalities of egeria-ui and egeria-react-ui during the migration and integration

Build, test and CI-CD process

• github dependant as in terms of release and github hooks for NPM builds

Dependencies

• egeria-js-commons
• happi-graph

Justification

• extraction and having a bit of more modularity in the UI components

Assumptions

Yes

Additional Information

I also created a Project under ODPI Organization called "Egeria UI Platform" which will tag items and issues for egeria-ui, egeria-react-ui, happi-graph, egeria-js-commons, egeria-ui-core, egeria-ui-components.

Work Plan

Before creating the repo

• review overall request & get clarifications
• get approval on developer/TSC call from maintainers

Creating the repo

• Create the repo under the odpi organization (default gitignore, license, readme)
• Setup branch protection rules
• Set pull request options (allow merge, squash, rebase, suggest updating, allow automerge, do not delete head)
• Update security settings in repo (policy, advisories, alerts)
• set up permissions

First steps

• Initial code-drop (author)

Getting CI/CD started & refining settings

• Add initial build script for PR (including gradle wrapper if required)
• Add initial build script for merge

Further Refinement

• Add link in egeria docs to new repo describing purpose ( https://github.com/odpi/egeria-docs/blob/main/site/docs/education/tutorials/git-and-git-hub-tutorial/egeria-git-repositories.md )
• Add to connector catalog, if new repo is for connector ( https://github.com/odpi/egeria-docs/blob/main/site/docs/connectors/index.md )
• Add to release process docs ( https://github.com/odpi/egeria-docs/blob/main/site/docs/guides/contributor/release-process/index.md )
• Add required credentials for publishing to container repos, maven central etc
• Add artifact signing if needed
• Add dependabot config
• Add CodeQL
• Add to LFX ( https://projectadmin.lfx.linuxfoundation.org/project/a092M00001IV4JtQAL ) for
  • LFXSecurity
  • LFAnalytics
• Add check for stale defects
• Add any required issue tags

Release

• Add release pipeline

[planetf1]

This was agreed in the face2face meeting w/c 23 May 2022.

[planetf1]

@sarbull I've done the initial steps. We'll keep this issue open to track some of the remaining setup/cataloguing steps.

Should be fine for you to start using for code now.

I've not done anything build/pipeline related - but once you have some code building, we should return to that to make sure we verify PRs, publish artifacts etc.

[planetf1]

Further work on the process/scans/build really needs some initial code.

I will continue once there's something to work with checked in.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 20 days if no further activity occurs. Thank you for your contributions.

[planetf1]

I need to ensure docs are updated - moving