Changeset - 932b6a051504
[Not reviewed]
0 1 0
Denver Gingerich - 2 months ago 2024-02-02 06:06:57
denver@ossguy.com
usethesource: add AoE abbr's to CCIRT process page
1 file changed with 2 insertions and 2 deletions:
0 comments (0 inline, 0 general)
conservancy/usethesource/templates/usethesource/ccirt_process.html
Show inline comments
...
 
@@ -13,10 +13,10 @@
 

	
 
  <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 AoE FIMXE: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 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>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>For the avoidance of doubt, and to hopefully prevent a wave of last-minute CCIRT submissions on the final day of this 30-day window, SFC is providing for 7 calendar days after the 30-day window ends (so 37 days from February 3, or until 23:59 AoE FIMXE:abbr on March 11, 2024), to any company that provides the email address of their CCIRT at any time during this 30-day window, the option to correct its source candidates before we publish them.  So it is beneficial for companies to inform us of their CCIRT sooner rather than later, so they have as much of that 37 days as possible to correct all copyleft compliance issues.  SFC looks forward to working with all the CCIRTs who register with us.</p>
 
  <p>For the avoidance of doubt, and to hopefully prevent a wave of last-minute CCIRT submissions on the final day of this 30-day window, SFC is providing for 7 calendar days after the 30-day window ends (so 37 days from February 3, or until 23:59 <abbr title="Anywhere on Earth">AoE</abbr> on March 11, 2024), to any company that provides the email address of their CCIRT at any time during this 30-day window, the option to correct its source candidates before we publish them.  So it is beneficial for companies to inform us of their CCIRT sooner rather than later, so they have as much of that 37 days as possible to correct all copyleft compliance issues.  SFC looks forward to working with all the CCIRTs who register with us.</p>
 

	
 
{% endblock content %}
0 comments (0 inline, 0 general)