Skip to content

[WIP] TRG - #3

Open
kss682 wants to merge 3 commits into
sde-bugfixfrom
trg
Open

[WIP] TRG#3
kss682 wants to merge 3 commits into
sde-bugfixfrom
trg

Conversation

@kss682

@kss682 kss682 commented Dec 9, 2025

Copy link
Copy Markdown

TRG 1.0: Documentation

Checklist: (Need support for the points mentioned below from @devajipatil or @saudkhan116 )

  • README.md
  • INSTALL.md
  • Missing backend charts folder
  • CHANGELOG.md
  • List of changes that have been made
  • What version do we release this current working version ? 2.5.0 is the next minor version or 3.0.0 (major update)
  • Diagrams as code / Editable static files
  • Need to create architecture diagram for the backend
  • Architecture Documentation
  • Corresponding documentation for the architecture
  • Administrator's Guide
  • End User Manual (Not needed as backend doesn't have a UI the user interacts with)
  • Interface documentation (APIs)
  • API specification
  • Migration Guide
  • Have added a default instruction, detailed instructions regarding how the database needs to be migrated during version changes needs to be added

TRG 2.0: GIT

Checklist:

  • Default branch must be main
  • Structure Repo according to guidelines
  • Leading product repository (NA, have to follow this on the parent repo of managed-simple-data-exchange)
  • Repository metafile

TRG 7.0: Open Source Governance

Checklist:

  • Recurring activity for each PR
  • Legal doc
  • License headers

TRG 8.0: Security

Checklist:

  • CodeQL
  • KICS
  • TruffleHog
  • Trivy
  • Dependabot

@kss682 kss682 changed the title [WIP] TRG 1.0 & 2.0 [WIP] TRG Dec 9, 2025

@saudkhan116 saudkhan116 left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@kss682 please coordinate with @devajipatil to conclude this PR

@saudkhan116

Copy link
Copy Markdown
Collaborator

@kss682 please coordinate with @devajipatil to conclude this PR

@devajipatil, whats the current status of this PR, should we merge it or is there still some work to be done?

@devajipatil devajipatil left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Changes looks good to me and can be merged

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants