Skip to content

Define new "Made for UDS" guidelines #566

@nywilken

Description

@nywilken

The Made For UDS document was largely created around the internal Bounty program in late 2024. This guideline was largely centered around internal Engineers creating UDS Packages, and less-so enabling outside entities to create UDS Packages.

A new "Made for UDS" guideline should be created. This guideline should be more agnostic, in enabling any engineer to create a UDS Package, not just internal Unicorns.

These new guidelines / guides should be everything encompassed under the uds-packages directory here in uds-common: https://github.com/defenseunicorns/uds-common/tree/main/docs/uds-packages

Alongside making the guidelines more available to everyone, we also need to ensure we agree upon the current guidelines. UDS Core has gone through many iterations since these guidelines were created, we have also since deployed Registry, and deprecated App Store.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentation

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions