Inconsistent module path about about-api HOT 4 CLOSED

Thanks @lauralorenz for the clarification. I guess I can help with it.
/assign

from about-api.

sorry, I missed the issue #6, it's probably a duplicate of it

from about-api.

@lauralorenz
It is the issue I mentioned at the community meeting(2022-06-14).
I think the API should be put directly in the module, just like what we did at work-api, which will make it easy to import the API.

If you agree with that, I can help make a change for that. What do you say?

from about-api.

I am also not a go package expert but cross checking with Work API repo, the MCS API repo and the Gateway API repo too I think overall we want go get sigs.k8s.io/about-api to be the target.

Today I see go get sigs.k8s.io/about-api does work from a proper redirect perspective but doesn't get all the required files because they are all in clusterproperty which is a subdirectory.

So to achieve parity with these other properly configured repos I agree with @RainbowMango that everything should be put directly in the module (aka everything in the whole about-api/clusterproperty dir should be unravelled up to the root of the github repo) and then ALSO as OP mentioned the package should be renamed, but to sigs.k8s.io/about-api.

from about-api.