Adam Kaplan

Refinement - this is likely a limitation of how Tekton creates containers in a TaskRun. A guide for build strategy authors should call this out.

> The step could check the existing sub-directories and if there are any, clone into a temporary directory and then move content. This feels like a lot of extra work,...

This feature should be discussed and formalized via a [SHIP](https://github.com/shipwright-io/community/tree/main/ships#readme). A potential concern is leaking our abstraction of Tekton. Tight coupling of Shipwright to Tekton is already a concern -...

Note - we should consider this bug obsolete when we stop supporting the `v1alpha1` API.

I don't think this issue is completely obsolete. We are still serving the `v1alpha1` API and thus users may still run into this bug. However, with the CLI update landing...

This approach warrants further discussion, and the API update would be significant enough that it should be formally described in a [SHIP](https://github.com/shipwright-io/community/tree/main/ships#readme).

From refinement - adding to backlog as having a community standard on import ordering would be beneficial. Enforcing a standard on import namings is a lot more challenging - per...

We have a release branch set up for z-streams, but we have not actively tagged a z-stream release for a security fix. I think we can call this "done" because...

SHIP-0038 covers the process for backporting bug fixes and security patches. It doesn't cover active scanning.

/kind feature