Re: RFC: Project Due Diligence Backlog
Wouldn’t it be preferable to do the preparation of the proposal in a Google Doc, and then commence the actual due diligence exercise with a PR (the way most of the other proposals have worked)? That way it would be clear when exactly the proposal is submitted, and the proper record of due diligence comments/feedback would be available in GitHub for all to see.
As opposed to in this case where the document has been through various revisions in multiple documents, and it’s not been clear when the transition from document preparation to technical due diligence occurred?
Technical Vice President
America Research Center
2330 Central Expressway, Santa Clara, CA 95050
Tel: 408-330-4721 Cell: 408-320-8917 Office # E2-9
Email: quinton.hoole@... ID#Q00403160
From: Alexis Richardson <alexis@...>
Date: Tuesday, January 9, 2018 at 10:09
To: Quinton Hoole <quinton.hoole@...>
Cc: Chris Aniszczyk <caniszczyk@...>, Benjamin Hindman <benh@...>, CNCF TOC <cncf-toc@...>
Subject: Re: [cncf-toc] RFC: Project Due Diligence Backlog