RE: CVE Automation Working Group Charter

Hi Chris, I pulled the following principle from the charter:

•Use free and open source solutions where possible. Avoid solutions that require propriety, closed systems, or are not compatible with CVE terms of use

I agree with this principle but think it is incomplete. Efficiency of use and management, and scalability are important considerations when considering any potential solution. Effectiveness is dealt with by another principle, but it is possible to have a non-scalable and inefficient solution that is effective. In other words, it works but it is too expensive in terms of labor hours to manage. The statement could say:

•Use free and open source solutions where possible. Avoid solutions that require propriety, closed systems, are not plausibly scalable to support program growth, are labor intensive to manage, or are not compatible with CVE terms  of use.

I also recommend numbering the bullets under each of the sections so that we can refer to them by number instead of having to state the bullet each time we need to reference it in written or verbal discussion.

C

CVE Board Members,

I am recommending the attached CVE Automation Working Group charter for approval by the board.  Please review the charter and submit your vote to this email list  by Noon EDT on Thursday, May 31.  The results of the vote will be announced at the June 13^th board meeting.

The charter is also available from the GitHub repository:

https://github.com/CVEProject/automation-working-group/blob/master/CAWG_Charter_DRAFT.md

Thank you,

Chris Johnson

CVE Automation Working Group