Rishi Verma

> One of the soft requirements was to have a tool that could record code coverage during execution in the cases where a defined test suite had not yet been...

@jl-0 - I'm not quite following - what's the format for the "documented test procedure"? Code coverage tools look at function / method references and follow the execution stack to...

+1’d by @MJJoyce, @galenatjpl, @jeffreypon, @sujen1412, @hookhua

Hi @ewferg - thanks for your support and reference to your governance model! It's excellent. I see it was based on some governance approaches for popular OSS projects. I particularly...

Actually open question to all here (@MJJoyce, @galenatjpl, @jeffreypon, @sujen1412, @hookhua, @ewferg etc.): which information do you feel is important in describing your open source project management approach and personnel...

Hi @ewferg - thanks for the responses! Definitely agree with you that the verbosity of governance recommendations can often scale against the size of the team considered. Also - excited...

> @riverma, years ago, we conducted an open source path forward study that resulted in a document. There is a section in this document that provides some description of a...

Closing as work has been completed. Thanks again to @ewferg .

This is a really important topic @tariqksoliman - thank you for bringing it up. CC'ing @hookhua who's been thinking about this problem with respect to [HySDS](https://github.com/hysds). CC'ing @NASA-AMMOS/slim-tsc and @NASA-AMMOS/slim-psc...

Nice - looking forward to it 👍