Coder Social home page Coder Social logo

Comments (9)

kt3k avatar kt3k commented on May 19, 2024 2

I'm now thinking about the config structure like the below for allowing multiple year patterns.

{
  "**/*.js": "// Copyright {YEAR} My Name. All rights reserved. MIT license.",
  "params": {
    "YEAR": "some regexp?"
  }
}

from deno_license_checker.

bmarwell avatar bmarwell commented on May 19, 2024 1

Personally I often see people updating all years in headers around the new years day.

Yikes. I am a java developer and contribute to apache projects. As far as I can tell, there is usually one year only, which is updated when the file is being modified. I do not think updating projects at new year is a good thing. It is not a functional change, and if forgotten will fail PRs and future builds.

from deno_license_checker.

kt3k avatar kt3k commented on May 19, 2024

Currently there is no support of mixed years in copyright headers.

Is mixing years in copyright header common or good thing? Personally I often see people updating all years in headers around the new years day.

from deno_license_checker.

bmarwell avatar bmarwell commented on May 19, 2024

Also mentioned in the GPL FAQ: https://www.gnu.org/licenses/gpl-howto.html

from deno_license_checker.

kt3k avatar kt3k commented on May 19, 2024

If mixture of different years is allowed, do you have any idea of the design of the config file?

from deno_license_checker.

bmarwell avatar bmarwell commented on May 19, 2024

I basically would allow regex to be included. Sadly this would not be downwards compatible.

from deno_license_checker.

ni4 avatar ni4 commented on May 19, 2024

Got to this repository via search, to automate latest year inclusion. I.e. just to check whether pushed files contains current year in copyright string. It could be done as dealing with copyright as regexp, adding some placeholders like ${YEAR}, ${FILENAME}, maybe something else could be useful as well.

from deno_license_checker.

mars-risc0 avatar mars-risc0 commented on May 19, 2024

Is mixing years in copyright header common or good thing?

I don't think I have ever seen a codebase older than one year which did not include mixed years in copyright headers. It is common to see a range, for example "Copyright (c) 2003-2009 Foo, Inc.".

Personally I often see people updating all years in headers around the new years day.

Several of the places I have worked would have absolutely forbidden such a large, non-functional change across the entire codebase.

from deno_license_checker.

ladislas avatar ladislas commented on May 19, 2024

@kt3k this would be amazing!

from deno_license_checker.

Related Issues (15)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.