search

KhronosGroup / Vulkan-Ecosystem

Public repository for Vulkan Ecosystem issues
Apache License 2.0
132 stars 15 forks source link

Minimal-process approach to ecosystem map #12

Closed natduca closed 6 years ago

natduca commented 6 years ago

Lets just paste stuff into the readme.md that is useful. Where projects have quirks, we can write what exists. Once we have the map, people can bring up individual issues like "gee, can we talk about eg spirv-tools having a code-of-conduct, or have its dependencies spelled out."

nsubtil commented 6 years ago

I incorporated most of the feedback and reorganized the info a bit. Unfortunately I had to move this to a new PR since GitHub won't allow another author to take over an existing PR (or maybe I just don't know how to do that?).

Moved to #14. Please add further feedback there.

oddhack commented 6 years ago

@nsubtil probably because the PR is proposed from their personal github space? If you both had commit access to that repository then you presumably could push updates to the branch backing the PR - at least it works that way in our internal gitlab repos.

nsubtil commented 6 years ago

Yeah, that's my understanding. I'm not sure if there's some process to hand over a PR between authors though.