Conservancy/website
6
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

usethesource: linkify email addr in CCIRT process

Browse source
This commit is contained in:
Denver Gingerich 2024-02-01 22:12:42 -08:00
parent 932b6a0515
commit 1493bafa85
1 changed files with 1 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
conservancy/usethesource/templates/usethesource/ccirt_process.html
View file

@ -13,7 +13,7 @@
<p>Based on our decades of GPL compliance experience, we expect that many of the source code candidates we receive from the public will be incomplete. SFC cannot immediately validate nor invalidate any of those claims due to the vast number of devices on the market. But we are willing to engage with companies' CCIRTs so they have a chance to (re-)review these candidates if they wish, before SFC publishes them.</p> <p>Based on our decades of GPL compliance experience, we expect that many of the source code candidates we receive from the public will be incomplete. SFC cannot immediately validate nor invalidate any of those claims due to the vast number of devices on the market. But we are willing to engage with companies' CCIRTs so they have a chance to (re-)review these candidates if they wish, before SFC publishes them.</p>
<p>We are providing a 30-day window, starting on February 3, 2024 (and ending at 23:59 <abbr title="Anywhere on Earth">AoE</abbr> on March 4, 2024), in which companies can send us the email address of their CCIRT (to compliance@sfconservancy.org with Subject "CCIRT contact") so we can contact this team about any source candidates we receive, giving them 7 calendar days to confirm all potential copyleft licenses issues are resolved. At the end of these 7 days, we will publish the updated source candidate (if we receive one), or the original (if no update is received). If we have no contact registered, the source candidate will be published without any grace period following the initial 30-day window.</p> <p>We are providing a 30-day window, starting on February 3, 2024 (and ending at 23:59 <abbr title="Anywhere on Earth">AoE</abbr> on March 4, 2024), in which companies can send us the email address of their CCIRT (to <a href="mailto:compliance@sfconservancy.org">compliance@sfconservancy.org</a> with Subject "CCIRT contact") so we can contact this team about any source candidates we receive, giving them 7 calendar days to confirm all potential copyleft licenses issues are resolved. At the end of these 7 days, we will publish the updated source candidate (if we receive one), or the original (if no update is received). If we have no contact registered, the source candidate will be published without any grace period following the initial 30-day window.</p>
<p>After this initial 30-day window, companies can still send us the email address of their CCIRT and, after we receive this email address, we will give them 7 calendar days from the first notification of an incomplete source candidate to resolve the issue. However, it is best for companies to let us know about their CCIRT before this 30-day window ends in case there are any pending source candidates to publish when that 30-day window ends.</p> <p>After this initial 30-day window, companies can still send us the email address of their CCIRT and, after we receive this email address, we will give them 7 calendar days from the first notification of an incomplete source candidate to resolve the issue. However, it is best for companies to let us know about their CCIRT before this 30-day window ends in case there are any pending source candidates to publish when that 30-day window ends.</p>