Add Standards/scs-0102-v2-image-metadata.md

[mbuechse]

No description provided.

[fzakfeld]

@depressiveRobot we (ScaleUp) have implemented this and should be ready

[depressiveRobot]

We have two further responses:

• one can implement it by mid-February 2026
• one is against mandatory as they see no customer demand for it

[depressiveRobot]

I think the replaces metadata field to the old document needs to be added.

[depressiveRobot]

Thanks for adding the missing field. Looks good now.

[garloff]

Looks good to me, thanks!

[mbuechse]

Note to self: check whether we have a testcase for that (I guess not)

[depressiveRobot]

As we should have a testcase for that before merge, I changed the PR to draft for now.

[mbuechse]

note to self: add testcase scs-0102-os_purpose-uniqueness

[garloff]

We have two further responses:

* one can implement it by mid-February 2026

* one is against mandatory as they see no customer demand for it

Well, the os_purpose field is the price to be paid for the freedom to have different image names.
So I would ask that operator whether they prefer the fixed image names.
The other thing to know is that there is no world in which this change -- adding another metadata field os_purpose -- would be in any way tedious or risky to break anything. Is is a no-brainer and just a question of whether you are willing to have some SCS best-practise metadata fields on all public images or not.

[mbuechse]

@garloff I think we know the arguments. I propose you talk to the operators directly. There is a decent chance this will be possible duing the workshop on February 24th.