Move TAP 8 to accepted

[mnm678]

No description provided.

[jkjell]

Looks good. I'm not sure if an optional/conditional client workflow is typically documented but, I asked for my own knowledge at least. 😅

[lukpueh]

Looks good.

I must say though that I don't quite understand the sections about TAP 4 and TAP 3: Half of the TAP 4 section talks about mirrors, which are not related to TAP 4, and the other half is a bit vague ("repository manager must ensure that they have the same set of trusted keys after all rotations" ... who are they and why?). And the section about TAP 3 seems to describe the same rotation process as without TAP 3. Or am I missing something?

Either way, I don't think these two sections should block the TAP. The basic idea sounds reasonable to me.

Unfortunately, the POC seems outdated, but IIUC the official (and lived) TAP process does not required a full implementation before the final status.

[mnm678]

Thanks for the reviews @lukpueh @jkjell! I pushed a suggested change, which dismissed the reviews. If you could re-approve this should be good to go.

@lukpueh The TAP 3 process is basically the same, that section is just describing the compatibility.

[trishankatdatadog]

Thanks all for moving this long-outstanding TAP fwd.

I can't speak for @jku, but we have some reservations about the complexity this TAP adds, although we understand the value it could add to OSS package registries like PyPI, so we probably weren't the best people to review it.

Thanks again!