Date
1 - 3 of 3
Concise guides - final drafts ready!
|
In reference to our discussion on today's call, I made a PR for point 7 as requested. However I don't think I did the DCO correctly. https://github.com/ossf/wg-best-practices-os-developers/pull/82
Dan Appelquist |
|
|
|
They ended up looking pretty good. Thanks Randall & David. I'll do a closer review later today.
toggle quoted message
Show quoted text
Cheers, CRob Director of Security Communications Intel Product Assurance and Security -----Original Message-----
From: openssf-wg-best-practices@... <openssf-wg-best-practices@...> On Behalf Of David A. Wheeler Sent: Saturday, August 27, 2022 10:06 PM To: openssf-wg-best-practices@... Subject: [openssf-wg-best-practices] Concise guides - final drafts ready! All: We now have two new final-draft documents produced by the OpenSSF Best Practices Working Group. I propose that we vote for their approval at our next meeting. Details & links below. --- David A. Wheeler ========================= Yesterday (Friday) many of us went through the various proposed changes in the drafts for our "concise" documents that were in Google docs. The changes were resolved, along with proposals from the tool Grammarly. Randall T. Vasquez then graciously converted the Google docs files into Markdown (thank you!). The final-draft versions are now on GitHub: * "Concise Guide for Developing More Secure Software" - https://github.com/ossf/wg-best-practices-os-developers/blob/main/docs/Concise-Guide-for-Developing-More-Secure-Software.md * "Concise Guide for Evaluating Open Source Software" - https://github.com/ossf/wg-best-practices-os-developers/blob/main/docs/Concise-Guide-for-Evaluating-Open-Source-Software.md I was going to leave them as PRs *to* be merged, but there were various weird problems, so I merged the PRs so we could more easily fix things. They're in the "docs/" area but nothing (yet) links to them, so you have to know they exist to find them :-). I hope that's okay. The documents are intentionally short, but even so, I expect that these are the kind of documents that will keep getting updated over time. So the question isn't "will they never be changed", but instead, "are they currently helpful to others?". Presuming that people are happy with the results, the plan is to create PDFs from them & point people to these materials. |
|
|
|
All:
We now have two new final-draft documents produced by the OpenSSF Best Practices Working Group. I propose that we vote for their approval at our next meeting. Details & links below. --- David A. Wheeler ========================= Yesterday (Friday) many of us went through the various proposed changes in the drafts for our "concise" documents that were in Google docs. The changes were resolved, along with proposals from the tool Grammarly. Randall T. Vasquez then graciously converted the Google docs files into Markdown (thank you!). The final-draft versions are now on GitHub: * "Concise Guide for Developing More Secure Software" - https://github.com/ossf/wg-best-practices-os-developers/blob/main/docs/Concise-Guide-for-Developing-More-Secure-Software.md * "Concise Guide for Evaluating Open Source Software" - https://github.com/ossf/wg-best-practices-os-developers/blob/main/docs/Concise-Guide-for-Evaluating-Open-Source-Software.md I was going to leave them as PRs *to* be merged, but there were various weird problems, so I merged the PRs so we could more easily fix things. They're in the "docs/" area but nothing (yet) links to them, so you have to know they exist to find them :-). I hope that's okay. The documents are intentionally short, but even so, I expect that these are the kind of documents that will keep getting updated over time. So the question isn't "will they never be changed", but instead, "are they currently helpful to others?". Presuming that people are happy with the results, the plan is to create PDFs from them & point people to these materials. |
|
|