Support from Acquia helps fund testing for Drupal Acquia logo

Comments

bserem created an issue. See original summary.

bserem’s picture

I'd like to submit this for the TPOTM award too!

thpoul’s picture

Status: Needs review » Needs work

Symfony2 - Copyright (c) 2004 - 2012 Fabien Potencier needs to change to Symfony2 - Copyright (c) 2004 - 2015 Fabien Potencier Source: http://symfony.com/doc/current/contributing/code/license.html

Twig - Copyright (c) 2009 Twig Team also needs to change to Twig - Copyright (c) 2009 - 2014 by the Twig Team Source: http://twig.sensiolabs.org/license

cilefen’s picture

Status: Needs work » Reviewed & tested by the community

@thpoul This makes me wonder how many other libraries ship with Drupal that are not mentioned in this file. And, why we would need to mention them at all because most, if not, all should ship with their own copyright notices.

Based on (emphasis mine)...

Drupal includes works under other copyright notices and distributed
according to the terms of the GNU General Public License or a compatible
license, including:

...it is a partial list. But what is the standard for including a given library's copyright in this file?

I wonder if the Licensing Working Group could help.

cilefen’s picture

Issue tags: +copyright
cilefen’s picture

Issue tags: +Documentation

Ok, one more tag, sorry about the noise.

cilefen’s picture

Status: Reviewed & tested by the community » Needs work

Sorry!

bserem’s picture

Status: Needs work » Needs review

I don't see how the rest of the years in the copyright file should be targeted all together in one issue.
We know for sure that the Drupal year need to be updated.

I'll bump this up again, so that it might catch some attention and we get more feedback.
I could do a research and update the information on all/most projects used in D8, if thats what we decide to do.

cilefen’s picture

@bserem From what I read via Google and my very limited understanding of copyright, it may be that only the first year need be listed. But, take that with a grain of salt.

Version: 8.0.x-dev » 8.1.x-dev

Drupal 8.0.6 was released on April 6 and is the final bugfix release for the Drupal 8.0.x series. Drupal 8.0.x will not receive any further development aside from security fixes. Drupal 8.1.0-rc1 is now available and sites should prepare to update to 8.1.0.

Bug reports should be targeted against the 8.1.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.2.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

frankfarm’s picture

From #4:

I wonder if the Licensing Working Group could help.

I agree that one or more lawyers familiar with copyright law (international or U.S.) ought to weigh in. Is there a recommended way to bring this issue to that group's attention?

Regarding #9, it might also be the case that no start and no end year is required; I'm just not sure.

cilefen’s picture

I opened #2725083: Are the years necessary in a copyright declaration?, but how about as per #8 we just mark this RTBC and get it fixed?

John Cook’s picture

Status: Needs review » Reviewed & tested by the community

I'm putting this back to RTBC.

I do not believe that we should be changing the copyright messages in third party software (Symphony, Twig, etc). There may be a reason for that specific year / range that we are unaware of.

Therefore, we should only change the copyright messages for Drupal itself and leave all other copyright notices as is.

cilefen’s picture

@John Cook: It turns out that is the future, but it isn't the current policy. See the discussion on #2725083: Are the years necessary in a copyright declaration?

In light of the actual policy, I think we have got missing a few 3rd-party licenses in COPYRIGHT.txt.

John Cook’s picture

Status: Reviewed & tested by the community » Needs work

Set to Needs work because of the comment from cilefen and the contents of COPYRIGHT.txt.

On 8.2.x before running composer install, so it's just the drupal repo, I have run the following command:
grep -irn "Copyright .*\-.*20[01][0-9]" * | grep -v "\-.*2016"
This should get any copyright notices not ending with 2016.

The results are as follows:

core/COPYRIGHT.txt:1:All Drupal code is Copyright 2001 - 2013 by the original authors.
core/COPYRIGHT.txt:57:  ArchiveTar - Copyright (c) 1997 - 2008 Vincent Blavet
core/COPYRIGHT.txt:59:  Doctrine Common - Copyright (c) 2006 - 2012 Alexander Mols, Benjamin Eberlei,
core/COPYRIGHT.txt:63:  Symfony2 - Copyright (c) 2004 - 2012 Fabien Potencier
core/COPYRIGHT.txt:65:    - Zend Framework (1.10dev - 2010-01-24) - Copyright (c) 2005-2010 Zend
core/lib/Drupal/Component/Bridge/ZfExtensionManagerSfContainer.php:19:   * @copyright Copyright (c) 2005-2013 Zend Technologies USA Inc. (http://www.zend.com)
core/lib/Drupal/Component/Bridge/ZfExtensionManagerSfContainer.php:79:   * @copyright Copyright (c) 2005-2013 Zend Technologies USA Inc. (http://www.zend.com)
core/lib/Drupal/Core/Archiver/ArchiveTar.php:10: * Copyright (c) 1997-2008,
core/lib/Drupal/Core/Archiver/ArchiveTar.php:37: * @copyright 1997-2010 The Authors

Just to note this is without the patch applied.

rajeshwari10’s picture

Assigned: bserem » rajeshwari10
rajeshwari10’s picture

Status: Needs work » Needs review
FileSize
1.21 KB

Updated years in the copyright.
Please review.

Thanks!!

rajeshwari10’s picture

FileSize
947 bytes

Adding interdiff.

Status: Needs review » Needs work

The last submitted patch, 17: update_year_in_copyright-2624024-17.patch, failed testing.

John Cook’s picture

Status: Needs work » Needs review

Test bot being silly.

Status: Needs review » Needs work

The last submitted patch, 17: update_year_in_copyright-2624024-17.patch, failed testing.

rajeshwari10’s picture

Status: Needs work » Needs review

Hi John Cook,

I don't know why the bot is saying failed testing.

Please review it.

Thanks!!

Version: 8.1.x-dev » 8.2.x-dev

Drupal 8.1.9 was released on September 7 and is the final bugfix release for the Drupal 8.1.x series. Drupal 8.1.x will not receive any further development aside from security fixes. Drupal 8.2.0-rc1 is now available and sites should prepare to upgrade to 8.2.0.

Bug reports should be targeted against the 8.2.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.3.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

wturrell’s picture

wturrell’s picture

FileSize
674 bytes

Interdiff.

wturrell’s picture

Assigned: rajeshwari10 » Unassigned

Version: 8.2.x-dev » 8.3.x-dev

Drupal 8.2.6 was released on February 1, 2017 and is the final full bugfix release for the Drupal 8.2.x series. Drupal 8.2.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.3.0 on April 5, 2017. (Drupal 8.3.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.3.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.4.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.3.x-dev » 8.4.x-dev

Drupal 8.3.6 was released on August 2, 2017 and is the final full bugfix release for the Drupal 8.3.x series. Drupal 8.3.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.4.0 on October 4, 2017. (Drupal 8.4.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.4.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.5.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.4.x-dev » 8.5.x-dev

Drupal 8.4.4 was released on January 3, 2018 and is the final full bugfix release for the Drupal 8.4.x series. Drupal 8.4.x will not receive any further development aside from critical and security fixes. Sites should prepare to update to 8.5.0 on March 7, 2018. (Drupal 8.5.0-alpha1 is available for testing.)

Bug reports should be targeted against the 8.5.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.6.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.5.x-dev » 8.6.x-dev

Drupal 8.5.6 was released on August 1, 2018 and is the final bugfix release for the Drupal 8.5.x series. Drupal 8.5.x will not receive any further development aside from security fixes. Sites should prepare to update to 8.6.0 on September 5, 2018. (Drupal 8.6.0-rc1 is available for testing.)

Bug reports should be targeted against the 8.6.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.7.x-dev branch. For more information see the Drupal 8 minor version schedule and the Allowed changes during the Drupal 8 release cycle.

Version: 8.6.x-dev » 8.8.x-dev

Drupal 8.6.x will not receive any further development aside from security fixes. Bug reports should be targeted against the 8.8.x-dev branch from now on, and new development or disruptive changes should be targeted against the 8.9.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

Version: 8.8.x-dev » 8.9.x-dev

Drupal 8.8.7 was released on June 3, 2020 and is the final full bugfix release for the Drupal 8.8.x series. Drupal 8.8.x will not receive any further development aside from security fixes. Sites should prepare to update to Drupal 8.9.0 or Drupal 9.0.0 for ongoing support.

Bug reports should be targeted against the 8.9.x-dev branch from now on, and new development or disruptive changes should be targeted against the 9.1.x-dev branch. For more information see the Drupal 8 and 9 minor version schedule and the Allowed changes during the Drupal 8 and 9 release cycles.

quietone’s picture

Status: Needs review » Closed (duplicate)

Thank you all for working on bringing the copyright file up to date.

The copyright file was updated on 15 May 2020 in #3119733: COPYRIGHT.txt outdated.