Hello! According to the Appendix of Apache License 2.0, if you want to license your so

Copyright notices have been updated for consistency and a NOTICE file added. Thanks fo

<a class="user-mention notranslate" data-hovercard-type="user" data-hovercard-url="/us

Change of Copyright notice about quiver-dart HOT 6 CLOSED

julia410m commented on May 27, 2024

Change of Copyright notice

from quiver-dart.

Comments (6)

cbracken commented on May 27, 2024 2

from quiver-dart.

jtmcdole commented on May 27, 2024

Yep; this should be <whatever year quiver was released / updated> and Google Inc

from quiver-dart.

cbracken commented on May 27, 2024

@julia410m can you elaborate where you think the change should be made? If you mean this section of the LICENSE file, it's an appendix that appears after the end of the terms and conditions, that describes how to apply the Apache licence to your own work:

quiver-dart/LICENSE

Lines 179 to 202 in a045123

 APPENDIX: How to apply the Apache License to your work. 

 To apply the Apache License to your work, attach the following 

 boilerplate notice, with the fields enclosed by brackets "[]" 

 replaced with your own identifying information. (Don't include 

 the brackets!) The text should be enclosed in the appropriate 

 comment syntax for the file format. We also recommend that a 

 file or class name and description of purpose be included on the 

 same "printed page" as the copyright notice for easier 

 identification within third-party archives. 

 Copyright [yyyy] [name of copyright owner] 

 Licensed under the Apache License, Version 2.0 (the "License"); 

 you may not use this file except in compliance with the License. 

 You may obtain a copy of the License at 

 http://www.apache.org/licenses/LICENSE-2.0 

 Unless required by applicable law or agreed to in writing, software 

 distributed under the License is distributed on an "AS IS" BASIS, 

 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 

 See the License for the specific language governing permissions and 

 limitations under the License.

We do that in every source file in Quiver. For example:

quiver-dart/lib/async.dart

Lines 1 to 13 in a045123

 // Copyright 2013 Google Inc. All Rights Reserved. 

 // 

 // Licensed under the Apache License, Version 2.0 (the "License"); 

 // you may not use this file except in compliance with the License. 

 // You may obtain a copy of the License at 

 // 

 // http://www.apache.org/licenses/LICENSE-2.0 

 // 

 // Unless required by applicable law or agreed to in writing, software 

 // distributed under the License is distributed on an "AS IS" BASIS, 

 // WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. 

 // See the License for the specific language governing permissions and 

 // limitations under the License.

This also matches how all other Google projects apply the licence, and in fact how the Apache web server itself does it.

If there's a specific file where we're missing a copyright notice, please let us know.

from quiver-dart.

julia410m commented on May 27, 2024

@cbracken thank you for your comment, I agree with you that the LICENSE file shouldn't be changed. I also have checked all your files of this software, they have the required copyright notice.

At the same time, we use your software and would like to assemble a file like this one that requires the component name, version, and copyright.

The copyright notices are somewhat different (the development year can be 2013, 2014, or 2018) in the files. Maybe it is worth to assemble the NOTICE file, according to the APPENDIX "and consider also including a NOTICE file that references the License". The instruction for the NOTICE file assembling is here. It seems that it will be possible to add in this file the common copyright notice which will cover all files of this software.

from quiver-dart.

cbracken commented on May 27, 2024

Historically we've always set the copyright notice in each file to that file's creation year. We can make the copyright date consistent and go with the earliest date like we do with Dart, Flutter, etc.

from quiver-dart.

cbracken commented on May 27, 2024

I'll also add a NOTICE file.

from quiver-dart.

Change of Copyright notice about quiver-dart HOT 6 CLOSED

Comments (6)

Related Issues (20)

Recommend Projects

React

Vue.js

Typescript

TensorFlow

Django

Laravel

D3

Recommend Topics

javascript

web

server

Machine learning

Visualization

Game

Recommend Org

Facebook

Microsoft

Google

Alibaba

D3

Tencent

	APPENDIX: How to apply the Apache License to your work.

	To apply the Apache License to your work, attach the following
	boilerplate notice, with the fields enclosed by brackets "[]"
	replaced with your own identifying information. (Don't include
	the brackets!) The text should be enclosed in the appropriate
	comment syntax for the file format. We also recommend that a
	file or class name and description of purpose be included on the
	same "printed page" as the copyright notice for easier
	identification within third-party archives.

	Copyright [yyyy] [name of copyright owner]

	Licensed under the Apache License, Version 2.0 (the "License");
	you may not use this file except in compliance with the License.
	You may obtain a copy of the License at

	http://www.apache.org/licenses/LICENSE-2.0

	Unless required by applicable law or agreed to in writing, software
	distributed under the License is distributed on an "AS IS" BASIS,
	WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	See the License for the specific language governing permissions and
	limitations under the License.

	// Copyright 2013 Google Inc. All Rights Reserved.
	//
	// Licensed under the Apache License, Version 2.0 (the "License");
	// you may not use this file except in compliance with the License.
	// You may obtain a copy of the License at
	//
	// http://www.apache.org/licenses/LICENSE-2.0
	//
	// Unless required by applicable law or agreed to in writing, software
	// distributed under the License is distributed on an "AS IS" BASIS,
	// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
	// See the License for the specific language governing permissions and
	// limitations under the License.