[Pkg-javascript-devel] Update node-vue-style-loader package

Jonas Smedegaard jonas at jones.dk
Fri Apr 1 13:14:35 BST 2022


Quoting Pirate Praveen (2022-04-01 13:18:11)
> 
> 
> On വ്യാ, മാർ 31 2022 at 11:22:22 രാവിലെ +0100 
> +0100, Michael Ikwuegbu <michaelikwuegbu1 at gmail.com> wrote:
> >  I have updated the package node-vue-style-loader from version 
> > (4.1.2 —> 4.1.3).
> > 
> >  I am requesting for sponsorship. I have made sure the package is 
> > Lintian clean and built it in a clean chroot with sbuild.
> >  I have pushed the current changes to my salsa repository: 
> > https://salsa.debian.org/mikemando/node-vue-style-loader
> > 
> > The package is available at: 
> > https://salsa.debian.org/js-team/node-vue-style-loader
> > 
> 
> We should follow the years mentioned in license files
> 
> https://salsa.debian.org/mikemando/node-vue-style-loader/-/commit/4384975bd7f875a4312104d61ae0f885664f3602
> 
> We don't need to update year if upstream has not updated it. So just 
> keep it 2017 or if you really wanted, you could say 2017-2022. Year in 
> copyright indicates the time when it was created or modified.
> 
> For files in debian directry we may update it, but not really 
> required. If at all you wanted to update, you can add your name for 
> 2022 and keep the previous line the same.

I agree with the final suggestion, but feel that the previous remarks are misleading:

Copyright notices are messages from the copyright holders to users, and 
we should only communicate that message, not alter it!

When you write or update the debian/copyright file, then you act as 
"secretary" for the owners of the project - only for files in the 
debian/ directory that you created or changed yourself should you decide 
on your own which years are correct. For all other notices (also those 
of fellow Debian maintainers) you should only update to mirror facts 
already stated elsewhere in the project.

If you feel the need to extend or correct some statements, then add a 
Comment: field describing how/why your information is different - e.g. 
"No license was stated in the project, but is assumed to be the same as 
https://example.com/foobar that is licensed as blabla-2.0".


Please also note that copyright years reflect when [original] change is 
introduced (i.e. time of innovation, not time of every change, and not 
time of release).

[original]: https://en.wikipedia.org/wiki/Copyright#Originality

Generally the copyright holder decides which changes should be 
considered "original".  Because nowadays copyright [registration] is 
automatic and main purpose of copyright [notices] have shifted to be a 
reminder to users that "I made something here, so if you want to 
negotiate licensing you should get in touch with me".

[registration]: https://en.wikipedia.org/wiki/Copyright#Registration

[notices]: 
https://en.wikipedia.org/wiki/Copyright_notice#Reasons_to_include_an_optional_copyright_notice


 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-javascript-devel/attachments/20220401/be66cd6f/attachment.sig>


More information about the Pkg-javascript-devel mailing list