repository doc example

[lapentad]

examples to register repositories for the example series.

NOTE: I did not add any sync information

[netlify]

✅ Deploy Preview for nephio ready!

Name	Link
🔨 Latest commit	67481cc
🔍 Latest deploy log	https://app.netlify.com/projects/nephio/deploys/691ef615dced780008fe5640
😎 Deploy Preview	https://deploy-preview-278--nephio.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[efiacor]

We use the term "packages" a lot in the docs. Do we need to point to a "kpt package" definition somewhere just to be clear?
Also, having this as a prerequisite would suffice for me.

• A Git repository containing your KPT packages

Or do we have a tutorial to "Set up a Git repo with dummy KPT package".

[Catalin-Stratulat-Ericsson]

no i want to veer away from this if possible. we make it extremely clear in the concepts section here

docs/content/en/docs/neo-porch/2_concepts/fundamentals.md

Lines 13 to 19 in 1b63aab

	* ***Package***: A package, in Porch, is specifically a [kpt package](https://kpt.dev/) - a collection of related YAML
	files including one or more **[KRM resources][krm]** and a [Kptfile](https://kpt.dev/book/02-concepts/#packages).
	{{% alert title="N.B." color="warning" %}}
	There is no such thing as a "Porch Package" - rather, **Porch stores and orchestrates kpt packages**.
	{{% /alert %}}

and soon in the overview also that there is no such thing as porch packages and from that point on packages means kpt packages

[Catalin-Stratulat-Ericsson]

i don't think we should foster this. i see it the same way as mentioning configuration as data. having its acronym stated as CaD and from that point on you refer to it as CaD and if someone does not know what that means they should go to its definition rather than carrying the explanation throughout the entire documentation for those who did not read that section. same with stating oci as experimental. we state that once clearly and explain why it is etc and then from that point on we only really mention git repositories.

[Catalin-Stratulat-Ericsson]

but thats just my opinion. if people disagree we can have a discussion and change it

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[lovesprung]

/approve

[Catalin-Stratulat-Ericsson]

/approve this looks ready to go in for me.

[Catalin-Stratulat-Ericsson]

now that i think of it this shows input and no output.
we should include the response of a repo get command and show a successfully registered repo and an unsuccessful registration

[Catalin-Stratulat-Ericsson]

maybe even a FAQ of common registration issues reason for repo not being ready e.g. invalid password/username combo etc

[efiacor]

/approve
/lgtm

[nephio-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Catalin-Stratulat-Ericsson, efiacor, lovesprung

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [Catalin-Stratulat-Ericsson,efiacor,lovesprung]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment