Date
1 - 2 of 2
Concise guides appear to be completed - if there's an important issue, please raise it ASAP
|
All: I believe we've completed the first versions of our two "concise guides":
1. 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#readme 2. 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#readme The Best Practices WG approved both of them, except that one item needed to be resolved. My special thanks to Daniel Appelquist (Snyk) for helping us resolve that issue: https://github.com/ossf/wg-best-practices-os-developers/pull/84 In addition, we added some header text to make especially clear that any tools/services mentioned are merely examples: https://github.com/ossf/wg-best-practices-os-developers/pull/86 There have been a few minor formatting tweaks to them both that don't change content. In particular, it turns out that if you modify the URLs on Markdown files hosted on GitHub to add the "#readme" fragment, users' browsers will skip directly to the beginning of the document, which is nice. So we're using that trick. If you have any significant issues, please raise them ASAP! Otherwise I think we'll soon start trying to get the word out about them. --- David A. Wheeler |
|
|
|
VM (Vicky) Brasseur
HUZZAH! Wonderful work, folks!
toggle quoted message
Show quoted text
--V -- VM (Vicky) Brasseur Director, Senior Strategy Advisor Open Source Program Office Wipro Limited ⏰ Time Zone: Pacific/West Coast US -----Original Message-----
From: <openssf-wg-best-practices@...> on behalf of "David A. Wheeler via lists.openssf.org" <dwheeler=linuxfoundation.org@...> Reply to: "dwheeler@..." <dwheeler@...> Date: Monday, September 5, 2022 at 06:14 To: "openssf-wg-best-practices@..." <openssf-wg-best-practices@...> Cc: Brian Behlendorf <bbehlendorf@...>, Jennifer Bly <jbly@...> Subject: [openssf-wg-best-practices] Concise guides appear to be completed - if there's an important issue, please raise it ASAP CAUTION:This email is received from an external domain. Open the hyperlink(s) & attachment(s) with caution. . All: I believe we've completed the first versions of our two "concise guides": 1. Concise Guide for Developing More Secure Software https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fossf%2Fwg-best-practices-os-developers%2Fblob%2Fmain%2Fdocs%2FConcise-Guide-for-Developing-More-Secure-Software.md%23readme&;data=05%7C01%7Cvm.brasseur%40wipro.com%7C0562817a77204e27ebf608da8f409e8d%7C258ac4e4146a411e9dc879a9e12fd6da%7C1%7C0%7C637979804983287884%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=07Aw3NgRK%2F26JgaM7BDAIKYEVFpYbjWgpnaVnIBOZHk%3D&reserved=0 2. Concise Guide for Evaluating Open Source Software https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fossf%2Fwg-best-practices-os-developers%2Fblob%2Fmain%2Fdocs%2FConcise-Guide-for-Evaluating-Open-Source-Software.md%23readme&;data=05%7C01%7Cvm.brasseur%40wipro.com%7C0562817a77204e27ebf608da8f409e8d%7C258ac4e4146a411e9dc879a9e12fd6da%7C1%7C0%7C637979804983287884%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=zE1pH4eTebPWnrB8fFATYZYZJRX1X6Htwi8ar6qvy0s%3D&reserved=0 The Best Practices WG approved both of them, except that one item needed to be resolved. My special thanks to Daniel Appelquist (Snyk) for helping us resolve that issue: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fossf%2Fwg-best-practices-os-developers%2Fpull%2F84&;data=05%7C01%7Cvm.brasseur%40wipro.com%7C0562817a77204e27ebf608da8f409e8d%7C258ac4e4146a411e9dc879a9e12fd6da%7C1%7C0%7C637979804983287884%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=0S9hV39zVgvvZdBZK1yeSZ9Wo7XyHJ8TbzGsFmmp3HM%3D&reserved=0 In addition, we added some header text to make especially clear that any tools/services mentioned are merely examples: https://apc01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fossf%2Fwg-best-practices-os-developers%2Fpull%2F86&;data=05%7C01%7Cvm.brasseur%40wipro.com%7C0562817a77204e27ebf608da8f409e8d%7C258ac4e4146a411e9dc879a9e12fd6da%7C1%7C0%7C637979804983287884%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=OduKC00V5OWq7hplEhZgQRUtI%2FwaN6RMLX98%2BE8Nric%3D&reserved=0 There have been a few minor formatting tweaks to them both that don't change content. In particular, it turns out that if you modify the URLs on Markdown files hosted on GitHub to add the "#readme" fragment, users' browsers will skip directly to the beginning of the document, which is nice. So we're using that trick. If you have any significant issues, please raise them ASAP! Otherwise I think we'll soon start trying to get the word out about them. --- David A. Wheeler 'The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. www.wipro.com' Internal to Wipro |
|
|