Discussion Round: Kokkos Community Growth and HPSF

[crtrott]

No description provided.

[dalg24]

Notes

Kokkos ecosystem

• Adding a new third-party library might be a hassle
• Could kokkos offer a single meta-package that includes all the ecosystem
• This sounds a bit like re-implementing spack
• The choices that would be made in such a meta package could not be the right ones for everyone
• The experience in Trilinos is that it is quite difficult to handle
  • Having too many packages in the "ecosystem" does not scale
  • Should all packages follow the release cycle, what are the rules for the ecosystem?
  • Too tight coupling can be difficult to manage if there are too many packages
• Having a package being part of the kokkos organization discourages others from proposing alternatives
  • Christian: This can be useful to get collaboration instead of everyone re-doing the work
• There is a hierarchy of tightly coupled projects and more loosely coupled ones
• Is there a list of external libraries that are based on Kokkos
  • Could there be a way to acknowledge them, offer them a "sticker" that says "this is a kokkos supported lib"
  • This could be somewhat automatized with a pull request template that add the info to the website