Closed paullatzelsperger closed 5 months ago
LGTM, can someone else give an approval?
Hi @paullatzelsperger,
is there a reason why naming it "tx-profiles" ?
Yes because it'll contain resources such as verifiable credentials, json-ld contexts and policies for tractus-x. However, they will have to be namespaced to a particular dataspace (eg catena x). And we plan to represent that as profiles.
Yes because it'll contain resources such as verifiable credentials, json-led contexts and policies for tractus-x. However, they will have to be namespaced to a particular dataspace (eg catena x). And we plan to represent that as profiles.
seems legit, but to prevent missunderstanding with our fork naming patterns within catena-x i guess prefix "tx-" should be improved
seems legit, but to prevent missunderstanding with our fork naming patterns within catena-x i guess prefix "tx-" should be improved
calling it just "profiles" seems a bit too generic. where can I find those fork naming patterns?
seems legit, but to prevent missunderstanding with our fork naming patterns within catena-x i guess prefix "tx-" should be improved
calling it just "profiles" seems a bit too generic. where can I find those fork naming patterns?
https://github.com/catenax-ng?q=tx-&type=all&language=&sort= and some internal system team instruction https://catenax-ng.github.io/docs/internal/how-to-setup-forked-repo
seems legit, but to prevent missunderstanding with our fork naming patterns within catena-x i guess prefix "tx-" should be improved
calling it just "profiles" seems a bit too generic. where can I find those fork naming patterns?
https://github.com/catenax-ng?q=tx-&type=all&language=&sort= and some internal system team instruction https://catenax-ng.github.io/docs/internal/how-to-setup-forked-repo
I honestly don't know how it would be possible for anyone to confuse an upstream repo with a fork, and I don't see how (formally) the catenax-ng
repo has any influence on tractusx. but
ok, then "tractusx-profiles" will be better.
seems legit, but to prevent missunderstanding with our fork naming patterns within catena-x i guess prefix "tx-" should be improved
calling it just "profiles" seems a bit too generic. where can I find those fork naming patterns?
https://github.com/catenax-ng?q=tx-&type=all&language=&sort= and some internal system team instruction https://catenax-ng.github.io/docs/internal/how-to-setup-forked-repo
I honestly don't know how it would be possible for anyone to confuse an upstream repo with a fork, and I don't see how (formally) the
catenax-ng
repo has any influence on tractusx. but ok, then "tractusx-profiles" will be better.
where also my suggestions:
changes are live.
@netomi pls aks for project lead verification for repository creation
Description
This PR requests a new repository named 'tx-profiles'.
Pre-review checks
Please ensure to do as many of the following checks as possible, before asking for committer review: