Is it legal to have the “// (c) 2019 John Smith” header in all files when there are hundreds of contributors?License header for dual-licensed (AGPL or “non-free”) source codeHow do I properly specify the year(s) of copyright?When to list contributorsWe worked with BSD-license software and modified it and now want to allow others to help usHow do I make GPL “or later” contributions to a GPL “only” project?License file organization when moving from one permissive license to another?Can I remove some copyright holders from headers and replace them by a generic “and contributors”?Does a central copyright and license notice cover all the files in a software program?If there is no copyright notice, is the license applied?Copyright notices and multiple developers

Can't get 5V 3A DC constant

"Whatever a Russian does, they end up making the Kalashnikov gun"? Are there any similar proverbs in English?

Initiative: Do I lose my attack/action if my target moves or dies before my turn in combat?

Extension of 2-adic valuation to the real numbers

On The Origin of Dissonant Chords

What causes platform events to fail to be published and should I cater for failed platform event creations?

I preordered a game on my Xbox while on the home screen of my friend's account. Which of us owns the game?

How could Tony Stark make this in Endgame?

How to not starve gigantic beasts

Was there a Viking Exchange as well as a Columbian one?

How do I reattach a shelf to the wall when it ripped out of the wall?

How exactly does Hawking radiation decrease the mass of black holes?

Retract an already submitted recommendation letter (written for an undergrad student)

Apparently, my CLR assembly function is causing deadlocks?

Does a large simulator bay have standard public address announcements?

Is the claim "Employers won't employ people with no 'social media presence'" realistic?

What happens in the secondary winding if there's no spark plug connected?

What does the integral of a function times a function of a random variable represent, conceptually?

Why was the Spitfire's elliptical wing almost uncopied by other aircraft of World War 2?

How can Republicans who favour free markets, consistently express anger when they don't like the outcome of that choice?

What is the optimal strategy for the Dictionary Game?

How to have a sharp product image?

Minor Revision with suggestion of an alternative proof by reviewer

Like totally amazing interchangeable sister outfits II: The Revenge



Is it legal to have the “// (c) 2019 John Smith” header in all files when there are hundreds of contributors?


License header for dual-licensed (AGPL or “non-free”) source codeHow do I properly specify the year(s) of copyright?When to list contributorsWe worked with BSD-license software and modified it and now want to allow others to help usHow do I make GPL “or later” contributions to a GPL “only” project?License file organization when moving from one permissive license to another?Can I remove some copyright holders from headers and replace them by a generic “and contributors”?Does a central copyright and license notice cover all the files in a software program?If there is no copyright notice, is the license applied?Copyright notices and multiple developers













27















Companies use headers like



// Copyright 2011 The Go Authors.


But countless projects with a single maintainer have



// Copyright 2011 John Smith


even though they have hundreds of contributors, all of whom own their contributions.



Is this ok to only include the owner in the header?










share|improve this question



















  • 2





    Not a project that require a CLA / other form of copyright assignment?

    – Gert van den Berg
    Apr 8 at 14:33






  • 1





    If you're the author of this project, I would highly discourage adding such headers. Modern version control system have much better ways to attribute authorship than copyright header. If you found this in an existing project though, I would highly recommend against removing it without the consent of the listed party. In any case, such notices are not legally necessary to own copyright of the project/file.

    – Lie Ryan
    Apr 9 at 8:17












  • It can be legal if you strictly define for which part of software is this copyright notice. For example - specific file or subsystem/library.

    – i486
    Apr 9 at 9:31







  • 1





    @LieRyan : Note that especially within fields where people are not all software engineers, it's not that unusual for people to download stuff from open source websites, then keep and modify files in a non-VCS environment, keeping a header with a source in every file might be a good practice not to let these people forget where it came from.

    – Mefitico
    Apr 9 at 11:35















27















Companies use headers like



// Copyright 2011 The Go Authors.


But countless projects with a single maintainer have



// Copyright 2011 John Smith


even though they have hundreds of contributors, all of whom own their contributions.



Is this ok to only include the owner in the header?










share|improve this question



















  • 2





    Not a project that require a CLA / other form of copyright assignment?

    – Gert van den Berg
    Apr 8 at 14:33






  • 1





    If you're the author of this project, I would highly discourage adding such headers. Modern version control system have much better ways to attribute authorship than copyright header. If you found this in an existing project though, I would highly recommend against removing it without the consent of the listed party. In any case, such notices are not legally necessary to own copyright of the project/file.

    – Lie Ryan
    Apr 9 at 8:17












  • It can be legal if you strictly define for which part of software is this copyright notice. For example - specific file or subsystem/library.

    – i486
    Apr 9 at 9:31







  • 1





    @LieRyan : Note that especially within fields where people are not all software engineers, it's not that unusual for people to download stuff from open source websites, then keep and modify files in a non-VCS environment, keeping a header with a source in every file might be a good practice not to let these people forget where it came from.

    – Mefitico
    Apr 9 at 11:35













27












27








27


6






Companies use headers like



// Copyright 2011 The Go Authors.


But countless projects with a single maintainer have



// Copyright 2011 John Smith


even though they have hundreds of contributors, all of whom own their contributions.



Is this ok to only include the owner in the header?










share|improve this question
















Companies use headers like



// Copyright 2011 The Go Authors.


But countless projects with a single maintainer have



// Copyright 2011 John Smith


even though they have hundreds of contributors, all of whom own their contributions.



Is this ok to only include the owner in the header?







copyright license-notice software contributor






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited Apr 9 at 11:30









unor

3,8341443




3,8341443










asked Apr 7 at 22:58









AlexAlex

26726




26726







  • 2





    Not a project that require a CLA / other form of copyright assignment?

    – Gert van den Berg
    Apr 8 at 14:33






  • 1





    If you're the author of this project, I would highly discourage adding such headers. Modern version control system have much better ways to attribute authorship than copyright header. If you found this in an existing project though, I would highly recommend against removing it without the consent of the listed party. In any case, such notices are not legally necessary to own copyright of the project/file.

    – Lie Ryan
    Apr 9 at 8:17












  • It can be legal if you strictly define for which part of software is this copyright notice. For example - specific file or subsystem/library.

    – i486
    Apr 9 at 9:31







  • 1





    @LieRyan : Note that especially within fields where people are not all software engineers, it's not that unusual for people to download stuff from open source websites, then keep and modify files in a non-VCS environment, keeping a header with a source in every file might be a good practice not to let these people forget where it came from.

    – Mefitico
    Apr 9 at 11:35












  • 2





    Not a project that require a CLA / other form of copyright assignment?

    – Gert van den Berg
    Apr 8 at 14:33






  • 1





    If you're the author of this project, I would highly discourage adding such headers. Modern version control system have much better ways to attribute authorship than copyright header. If you found this in an existing project though, I would highly recommend against removing it without the consent of the listed party. In any case, such notices are not legally necessary to own copyright of the project/file.

    – Lie Ryan
    Apr 9 at 8:17












  • It can be legal if you strictly define for which part of software is this copyright notice. For example - specific file or subsystem/library.

    – i486
    Apr 9 at 9:31







  • 1





    @LieRyan : Note that especially within fields where people are not all software engineers, it's not that unusual for people to download stuff from open source websites, then keep and modify files in a non-VCS environment, keeping a header with a source in every file might be a good practice not to let these people forget where it came from.

    – Mefitico
    Apr 9 at 11:35







2




2





Not a project that require a CLA / other form of copyright assignment?

– Gert van den Berg
Apr 8 at 14:33





Not a project that require a CLA / other form of copyright assignment?

– Gert van den Berg
Apr 8 at 14:33




1




1





If you're the author of this project, I would highly discourage adding such headers. Modern version control system have much better ways to attribute authorship than copyright header. If you found this in an existing project though, I would highly recommend against removing it without the consent of the listed party. In any case, such notices are not legally necessary to own copyright of the project/file.

– Lie Ryan
Apr 9 at 8:17






If you're the author of this project, I would highly discourage adding such headers. Modern version control system have much better ways to attribute authorship than copyright header. If you found this in an existing project though, I would highly recommend against removing it without the consent of the listed party. In any case, such notices are not legally necessary to own copyright of the project/file.

– Lie Ryan
Apr 9 at 8:17














It can be legal if you strictly define for which part of software is this copyright notice. For example - specific file or subsystem/library.

– i486
Apr 9 at 9:31






It can be legal if you strictly define for which part of software is this copyright notice. For example - specific file or subsystem/library.

– i486
Apr 9 at 9:31





1




1





@LieRyan : Note that especially within fields where people are not all software engineers, it's not that unusual for people to download stuff from open source websites, then keep and modify files in a non-VCS environment, keeping a header with a source in every file might be a good practice not to let these people forget where it came from.

– Mefitico
Apr 9 at 11:35





@LieRyan : Note that especially within fields where people are not all software engineers, it's not that unusual for people to download stuff from open source websites, then keep and modify files in a non-VCS environment, keeping a header with a source in every file might be a good practice not to let these people forget where it came from.

– Mefitico
Apr 9 at 11:35










3 Answers
3






active

oldest

votes


















38














As far as I am aware, all FLOSS licenses that deal with copyright notices only require the preservation of notices that exist. Each author had the opportunity to add their own name to header when they made their contribution. If they chose not to do so, there is no existing notice from that author to preserve. There is never (as far as I know) any requirement to proactively add a notice that an author chose not to include.



Not having a copyright notice for some copyright holder is not inherently legally problematic, either, since copyright notices have virtually no legal function. An overwhelming majority of nations have ratified the Berne Convention, which requires that copyright rights are automatically granted at the time of a work's creation, irrespective of any copyright notice on the work.



If someone removes existing copyright notices by another author (whose copyrighted material is still contained in the work), then that's obviously not allowed by the license.






share|improve this answer

























  • Why is removing a copyright notice "typically illegal in general"? For example if a work is in the public domain, or its copyright has expired, I don't see how removing the copyright notice would be "illegal in general" in that case.

    – Brandin
    Apr 8 at 5:49











  • @Brandin You're right that "in general" was too broad. My intent was "illegal independent of whether the license explicitly disallows it or not" and I have edited to clarify.

    – apsillers
    Apr 8 at 10:15







  • 3





    @Brandin you do have a point, but consider moral rights: the right to be recognized as the author. Copyright notices are one way to do that recognition. Of course the duration of moral rights is extremely jurisdiction-dependent. In some places authorship needs to be asserted in order for these rights to apply. In others, moral rights never expire, even if the economic rights on the work have entered the public domain.

    – amon
    Apr 8 at 12:34











  • I think the question here is regarding, or may involve, a component of honesty: in particular, by putting such a notice at the beginning of a file when it was not (majorly?) written by the person indicated, even if it may be required by a license (e.g. that requires reproduction of notices), is that a lie, and if so, how does that jive with the requirements from said license?

    – The_Sympathizer
    Apr 8 at 15:51











  • @amon I always interpreted the "right to be recognized as author" to mean that you can state "I wrote/draw/created X". Not that any depiction in any form of X should state explicitly that you are the author.

    – Bakuriu
    Apr 8 at 21:26


















2














Legal? Who knows? If you work for a place that has an open-source compliance lawyer, ask them.



Still: open source licenses often suggest what to do with existing copyright notices. For example, the MIT license says, emphasis mine.




Copyright year copyright holder



Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files (the
"Software"), to deal in the Software without restriction, including
without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to
permit persons to whom the Software is furnished to do so, subject to
the following conditions:



The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.




It's clear, under this license, that the copyright notice on the FOSS you used should be included unchanged on the copies you distribute. If you did a substantial amount of work you could add another copyright line.



Other licenses offer similar requirements.






share|improve this answer


















  • 1





    Your statement contradicts the license. The license specifically says that you may make whatever modifications you want with the one exception that you may not modify the license file. So it would permit you to modify one-line copyright notices with author identification inside other files as you wish.

    – David Schwartz
    Apr 9 at 3:06



















1














Regardless of whether it's legal (it should be, but ask a lawyer), as a maintainer I find it inappropriate. For software that has a single primary author and many contributors of small patches, an appropriate copyright notice looks like:




Copyright ©2019 [author's name], et. al.




for et alia, literally "and others".



For a work with multiple major authors (and it's not clear to me the point at which this should change), but with no formal organization holding copyright, a more appropriate version might be:




Copyright ©2019 the authors of [project name]




However, you might want to run this by a lawyer, since it's not entirely traditional/conventional.



If you do end up with a formal organization that will hold copyright to most of the work, but don't want to impose FSF-style copyright assignment, an appropriate notice would be:




Copyright ©2019 [The Organization], et. al.







share|improve this answer























    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "619"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    noCode: true, onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8168%2fis-it-legal-to-have-the-c-2019-john-smith-header-in-all-files-when-there%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    3 Answers
    3






    active

    oldest

    votes








    3 Answers
    3






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    38














    As far as I am aware, all FLOSS licenses that deal with copyright notices only require the preservation of notices that exist. Each author had the opportunity to add their own name to header when they made their contribution. If they chose not to do so, there is no existing notice from that author to preserve. There is never (as far as I know) any requirement to proactively add a notice that an author chose not to include.



    Not having a copyright notice for some copyright holder is not inherently legally problematic, either, since copyright notices have virtually no legal function. An overwhelming majority of nations have ratified the Berne Convention, which requires that copyright rights are automatically granted at the time of a work's creation, irrespective of any copyright notice on the work.



    If someone removes existing copyright notices by another author (whose copyrighted material is still contained in the work), then that's obviously not allowed by the license.






    share|improve this answer

























    • Why is removing a copyright notice "typically illegal in general"? For example if a work is in the public domain, or its copyright has expired, I don't see how removing the copyright notice would be "illegal in general" in that case.

      – Brandin
      Apr 8 at 5:49











    • @Brandin You're right that "in general" was too broad. My intent was "illegal independent of whether the license explicitly disallows it or not" and I have edited to clarify.

      – apsillers
      Apr 8 at 10:15







    • 3





      @Brandin you do have a point, but consider moral rights: the right to be recognized as the author. Copyright notices are one way to do that recognition. Of course the duration of moral rights is extremely jurisdiction-dependent. In some places authorship needs to be asserted in order for these rights to apply. In others, moral rights never expire, even if the economic rights on the work have entered the public domain.

      – amon
      Apr 8 at 12:34











    • I think the question here is regarding, or may involve, a component of honesty: in particular, by putting such a notice at the beginning of a file when it was not (majorly?) written by the person indicated, even if it may be required by a license (e.g. that requires reproduction of notices), is that a lie, and if so, how does that jive with the requirements from said license?

      – The_Sympathizer
      Apr 8 at 15:51











    • @amon I always interpreted the "right to be recognized as author" to mean that you can state "I wrote/draw/created X". Not that any depiction in any form of X should state explicitly that you are the author.

      – Bakuriu
      Apr 8 at 21:26















    38














    As far as I am aware, all FLOSS licenses that deal with copyright notices only require the preservation of notices that exist. Each author had the opportunity to add their own name to header when they made their contribution. If they chose not to do so, there is no existing notice from that author to preserve. There is never (as far as I know) any requirement to proactively add a notice that an author chose not to include.



    Not having a copyright notice for some copyright holder is not inherently legally problematic, either, since copyright notices have virtually no legal function. An overwhelming majority of nations have ratified the Berne Convention, which requires that copyright rights are automatically granted at the time of a work's creation, irrespective of any copyright notice on the work.



    If someone removes existing copyright notices by another author (whose copyrighted material is still contained in the work), then that's obviously not allowed by the license.






    share|improve this answer

























    • Why is removing a copyright notice "typically illegal in general"? For example if a work is in the public domain, or its copyright has expired, I don't see how removing the copyright notice would be "illegal in general" in that case.

      – Brandin
      Apr 8 at 5:49











    • @Brandin You're right that "in general" was too broad. My intent was "illegal independent of whether the license explicitly disallows it or not" and I have edited to clarify.

      – apsillers
      Apr 8 at 10:15







    • 3





      @Brandin you do have a point, but consider moral rights: the right to be recognized as the author. Copyright notices are one way to do that recognition. Of course the duration of moral rights is extremely jurisdiction-dependent. In some places authorship needs to be asserted in order for these rights to apply. In others, moral rights never expire, even if the economic rights on the work have entered the public domain.

      – amon
      Apr 8 at 12:34











    • I think the question here is regarding, or may involve, a component of honesty: in particular, by putting such a notice at the beginning of a file when it was not (majorly?) written by the person indicated, even if it may be required by a license (e.g. that requires reproduction of notices), is that a lie, and if so, how does that jive with the requirements from said license?

      – The_Sympathizer
      Apr 8 at 15:51











    • @amon I always interpreted the "right to be recognized as author" to mean that you can state "I wrote/draw/created X". Not that any depiction in any form of X should state explicitly that you are the author.

      – Bakuriu
      Apr 8 at 21:26













    38












    38








    38







    As far as I am aware, all FLOSS licenses that deal with copyright notices only require the preservation of notices that exist. Each author had the opportunity to add their own name to header when they made their contribution. If they chose not to do so, there is no existing notice from that author to preserve. There is never (as far as I know) any requirement to proactively add a notice that an author chose not to include.



    Not having a copyright notice for some copyright holder is not inherently legally problematic, either, since copyright notices have virtually no legal function. An overwhelming majority of nations have ratified the Berne Convention, which requires that copyright rights are automatically granted at the time of a work's creation, irrespective of any copyright notice on the work.



    If someone removes existing copyright notices by another author (whose copyrighted material is still contained in the work), then that's obviously not allowed by the license.






    share|improve this answer















    As far as I am aware, all FLOSS licenses that deal with copyright notices only require the preservation of notices that exist. Each author had the opportunity to add their own name to header when they made their contribution. If they chose not to do so, there is no existing notice from that author to preserve. There is never (as far as I know) any requirement to proactively add a notice that an author chose not to include.



    Not having a copyright notice for some copyright holder is not inherently legally problematic, either, since copyright notices have virtually no legal function. An overwhelming majority of nations have ratified the Berne Convention, which requires that copyright rights are automatically granted at the time of a work's creation, irrespective of any copyright notice on the work.



    If someone removes existing copyright notices by another author (whose copyrighted material is still contained in the work), then that's obviously not allowed by the license.







    share|improve this answer














    share|improve this answer



    share|improve this answer








    edited Apr 9 at 3:36

























    answered Apr 7 at 23:27









    apsillersapsillers

    16.6k12954




    16.6k12954












    • Why is removing a copyright notice "typically illegal in general"? For example if a work is in the public domain, or its copyright has expired, I don't see how removing the copyright notice would be "illegal in general" in that case.

      – Brandin
      Apr 8 at 5:49











    • @Brandin You're right that "in general" was too broad. My intent was "illegal independent of whether the license explicitly disallows it or not" and I have edited to clarify.

      – apsillers
      Apr 8 at 10:15







    • 3





      @Brandin you do have a point, but consider moral rights: the right to be recognized as the author. Copyright notices are one way to do that recognition. Of course the duration of moral rights is extremely jurisdiction-dependent. In some places authorship needs to be asserted in order for these rights to apply. In others, moral rights never expire, even if the economic rights on the work have entered the public domain.

      – amon
      Apr 8 at 12:34











    • I think the question here is regarding, or may involve, a component of honesty: in particular, by putting such a notice at the beginning of a file when it was not (majorly?) written by the person indicated, even if it may be required by a license (e.g. that requires reproduction of notices), is that a lie, and if so, how does that jive with the requirements from said license?

      – The_Sympathizer
      Apr 8 at 15:51











    • @amon I always interpreted the "right to be recognized as author" to mean that you can state "I wrote/draw/created X". Not that any depiction in any form of X should state explicitly that you are the author.

      – Bakuriu
      Apr 8 at 21:26

















    • Why is removing a copyright notice "typically illegal in general"? For example if a work is in the public domain, or its copyright has expired, I don't see how removing the copyright notice would be "illegal in general" in that case.

      – Brandin
      Apr 8 at 5:49











    • @Brandin You're right that "in general" was too broad. My intent was "illegal independent of whether the license explicitly disallows it or not" and I have edited to clarify.

      – apsillers
      Apr 8 at 10:15







    • 3





      @Brandin you do have a point, but consider moral rights: the right to be recognized as the author. Copyright notices are one way to do that recognition. Of course the duration of moral rights is extremely jurisdiction-dependent. In some places authorship needs to be asserted in order for these rights to apply. In others, moral rights never expire, even if the economic rights on the work have entered the public domain.

      – amon
      Apr 8 at 12:34











    • I think the question here is regarding, or may involve, a component of honesty: in particular, by putting such a notice at the beginning of a file when it was not (majorly?) written by the person indicated, even if it may be required by a license (e.g. that requires reproduction of notices), is that a lie, and if so, how does that jive with the requirements from said license?

      – The_Sympathizer
      Apr 8 at 15:51











    • @amon I always interpreted the "right to be recognized as author" to mean that you can state "I wrote/draw/created X". Not that any depiction in any form of X should state explicitly that you are the author.

      – Bakuriu
      Apr 8 at 21:26
















    Why is removing a copyright notice "typically illegal in general"? For example if a work is in the public domain, or its copyright has expired, I don't see how removing the copyright notice would be "illegal in general" in that case.

    – Brandin
    Apr 8 at 5:49





    Why is removing a copyright notice "typically illegal in general"? For example if a work is in the public domain, or its copyright has expired, I don't see how removing the copyright notice would be "illegal in general" in that case.

    – Brandin
    Apr 8 at 5:49













    @Brandin You're right that "in general" was too broad. My intent was "illegal independent of whether the license explicitly disallows it or not" and I have edited to clarify.

    – apsillers
    Apr 8 at 10:15






    @Brandin You're right that "in general" was too broad. My intent was "illegal independent of whether the license explicitly disallows it or not" and I have edited to clarify.

    – apsillers
    Apr 8 at 10:15





    3




    3





    @Brandin you do have a point, but consider moral rights: the right to be recognized as the author. Copyright notices are one way to do that recognition. Of course the duration of moral rights is extremely jurisdiction-dependent. In some places authorship needs to be asserted in order for these rights to apply. In others, moral rights never expire, even if the economic rights on the work have entered the public domain.

    – amon
    Apr 8 at 12:34





    @Brandin you do have a point, but consider moral rights: the right to be recognized as the author. Copyright notices are one way to do that recognition. Of course the duration of moral rights is extremely jurisdiction-dependent. In some places authorship needs to be asserted in order for these rights to apply. In others, moral rights never expire, even if the economic rights on the work have entered the public domain.

    – amon
    Apr 8 at 12:34













    I think the question here is regarding, or may involve, a component of honesty: in particular, by putting such a notice at the beginning of a file when it was not (majorly?) written by the person indicated, even if it may be required by a license (e.g. that requires reproduction of notices), is that a lie, and if so, how does that jive with the requirements from said license?

    – The_Sympathizer
    Apr 8 at 15:51





    I think the question here is regarding, or may involve, a component of honesty: in particular, by putting such a notice at the beginning of a file when it was not (majorly?) written by the person indicated, even if it may be required by a license (e.g. that requires reproduction of notices), is that a lie, and if so, how does that jive with the requirements from said license?

    – The_Sympathizer
    Apr 8 at 15:51













    @amon I always interpreted the "right to be recognized as author" to mean that you can state "I wrote/draw/created X". Not that any depiction in any form of X should state explicitly that you are the author.

    – Bakuriu
    Apr 8 at 21:26





    @amon I always interpreted the "right to be recognized as author" to mean that you can state "I wrote/draw/created X". Not that any depiction in any form of X should state explicitly that you are the author.

    – Bakuriu
    Apr 8 at 21:26











    2














    Legal? Who knows? If you work for a place that has an open-source compliance lawyer, ask them.



    Still: open source licenses often suggest what to do with existing copyright notices. For example, the MIT license says, emphasis mine.




    Copyright year copyright holder



    Permission is hereby granted, free of charge, to any person obtaining
    a copy of this software and associated documentation files (the
    "Software"), to deal in the Software without restriction, including
    without limitation the rights to use, copy, modify, merge, publish,
    distribute, sublicense, and/or sell copies of the Software, and to
    permit persons to whom the Software is furnished to do so, subject to
    the following conditions:



    The above copyright notice and this permission notice shall be
    included in all copies or substantial portions of the Software.




    It's clear, under this license, that the copyright notice on the FOSS you used should be included unchanged on the copies you distribute. If you did a substantial amount of work you could add another copyright line.



    Other licenses offer similar requirements.






    share|improve this answer


















    • 1





      Your statement contradicts the license. The license specifically says that you may make whatever modifications you want with the one exception that you may not modify the license file. So it would permit you to modify one-line copyright notices with author identification inside other files as you wish.

      – David Schwartz
      Apr 9 at 3:06
















    2














    Legal? Who knows? If you work for a place that has an open-source compliance lawyer, ask them.



    Still: open source licenses often suggest what to do with existing copyright notices. For example, the MIT license says, emphasis mine.




    Copyright year copyright holder



    Permission is hereby granted, free of charge, to any person obtaining
    a copy of this software and associated documentation files (the
    "Software"), to deal in the Software without restriction, including
    without limitation the rights to use, copy, modify, merge, publish,
    distribute, sublicense, and/or sell copies of the Software, and to
    permit persons to whom the Software is furnished to do so, subject to
    the following conditions:



    The above copyright notice and this permission notice shall be
    included in all copies or substantial portions of the Software.




    It's clear, under this license, that the copyright notice on the FOSS you used should be included unchanged on the copies you distribute. If you did a substantial amount of work you could add another copyright line.



    Other licenses offer similar requirements.






    share|improve this answer


















    • 1





      Your statement contradicts the license. The license specifically says that you may make whatever modifications you want with the one exception that you may not modify the license file. So it would permit you to modify one-line copyright notices with author identification inside other files as you wish.

      – David Schwartz
      Apr 9 at 3:06














    2












    2








    2







    Legal? Who knows? If you work for a place that has an open-source compliance lawyer, ask them.



    Still: open source licenses often suggest what to do with existing copyright notices. For example, the MIT license says, emphasis mine.




    Copyright year copyright holder



    Permission is hereby granted, free of charge, to any person obtaining
    a copy of this software and associated documentation files (the
    "Software"), to deal in the Software without restriction, including
    without limitation the rights to use, copy, modify, merge, publish,
    distribute, sublicense, and/or sell copies of the Software, and to
    permit persons to whom the Software is furnished to do so, subject to
    the following conditions:



    The above copyright notice and this permission notice shall be
    included in all copies or substantial portions of the Software.




    It's clear, under this license, that the copyright notice on the FOSS you used should be included unchanged on the copies you distribute. If you did a substantial amount of work you could add another copyright line.



    Other licenses offer similar requirements.






    share|improve this answer













    Legal? Who knows? If you work for a place that has an open-source compliance lawyer, ask them.



    Still: open source licenses often suggest what to do with existing copyright notices. For example, the MIT license says, emphasis mine.




    Copyright year copyright holder



    Permission is hereby granted, free of charge, to any person obtaining
    a copy of this software and associated documentation files (the
    "Software"), to deal in the Software without restriction, including
    without limitation the rights to use, copy, modify, merge, publish,
    distribute, sublicense, and/or sell copies of the Software, and to
    permit persons to whom the Software is furnished to do so, subject to
    the following conditions:



    The above copyright notice and this permission notice shall be
    included in all copies or substantial portions of the Software.




    It's clear, under this license, that the copyright notice on the FOSS you used should be included unchanged on the copies you distribute. If you did a substantial amount of work you could add another copyright line.



    Other licenses offer similar requirements.







    share|improve this answer












    share|improve this answer



    share|improve this answer










    answered Apr 8 at 16:06









    O. JonesO. Jones

    1293




    1293







    • 1





      Your statement contradicts the license. The license specifically says that you may make whatever modifications you want with the one exception that you may not modify the license file. So it would permit you to modify one-line copyright notices with author identification inside other files as you wish.

      – David Schwartz
      Apr 9 at 3:06













    • 1





      Your statement contradicts the license. The license specifically says that you may make whatever modifications you want with the one exception that you may not modify the license file. So it would permit you to modify one-line copyright notices with author identification inside other files as you wish.

      – David Schwartz
      Apr 9 at 3:06








    1




    1





    Your statement contradicts the license. The license specifically says that you may make whatever modifications you want with the one exception that you may not modify the license file. So it would permit you to modify one-line copyright notices with author identification inside other files as you wish.

    – David Schwartz
    Apr 9 at 3:06






    Your statement contradicts the license. The license specifically says that you may make whatever modifications you want with the one exception that you may not modify the license file. So it would permit you to modify one-line copyright notices with author identification inside other files as you wish.

    – David Schwartz
    Apr 9 at 3:06












    1














    Regardless of whether it's legal (it should be, but ask a lawyer), as a maintainer I find it inappropriate. For software that has a single primary author and many contributors of small patches, an appropriate copyright notice looks like:




    Copyright ©2019 [author's name], et. al.




    for et alia, literally "and others".



    For a work with multiple major authors (and it's not clear to me the point at which this should change), but with no formal organization holding copyright, a more appropriate version might be:




    Copyright ©2019 the authors of [project name]




    However, you might want to run this by a lawyer, since it's not entirely traditional/conventional.



    If you do end up with a formal organization that will hold copyright to most of the work, but don't want to impose FSF-style copyright assignment, an appropriate notice would be:




    Copyright ©2019 [The Organization], et. al.







    share|improve this answer



























      1














      Regardless of whether it's legal (it should be, but ask a lawyer), as a maintainer I find it inappropriate. For software that has a single primary author and many contributors of small patches, an appropriate copyright notice looks like:




      Copyright ©2019 [author's name], et. al.




      for et alia, literally "and others".



      For a work with multiple major authors (and it's not clear to me the point at which this should change), but with no formal organization holding copyright, a more appropriate version might be:




      Copyright ©2019 the authors of [project name]




      However, you might want to run this by a lawyer, since it's not entirely traditional/conventional.



      If you do end up with a formal organization that will hold copyright to most of the work, but don't want to impose FSF-style copyright assignment, an appropriate notice would be:




      Copyright ©2019 [The Organization], et. al.







      share|improve this answer

























        1












        1








        1







        Regardless of whether it's legal (it should be, but ask a lawyer), as a maintainer I find it inappropriate. For software that has a single primary author and many contributors of small patches, an appropriate copyright notice looks like:




        Copyright ©2019 [author's name], et. al.




        for et alia, literally "and others".



        For a work with multiple major authors (and it's not clear to me the point at which this should change), but with no formal organization holding copyright, a more appropriate version might be:




        Copyright ©2019 the authors of [project name]




        However, you might want to run this by a lawyer, since it's not entirely traditional/conventional.



        If you do end up with a formal organization that will hold copyright to most of the work, but don't want to impose FSF-style copyright assignment, an appropriate notice would be:




        Copyright ©2019 [The Organization], et. al.







        share|improve this answer













        Regardless of whether it's legal (it should be, but ask a lawyer), as a maintainer I find it inappropriate. For software that has a single primary author and many contributors of small patches, an appropriate copyright notice looks like:




        Copyright ©2019 [author's name], et. al.




        for et alia, literally "and others".



        For a work with multiple major authors (and it's not clear to me the point at which this should change), but with no formal organization holding copyright, a more appropriate version might be:




        Copyright ©2019 the authors of [project name]




        However, you might want to run this by a lawyer, since it's not entirely traditional/conventional.



        If you do end up with a formal organization that will hold copyright to most of the work, but don't want to impose FSF-style copyright assignment, an appropriate notice would be:




        Copyright ©2019 [The Organization], et. al.








        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered Apr 8 at 15:16









        R..R..

        1,604155




        1,604155



























            draft saved

            draft discarded
















































            Thanks for contributing an answer to Open Source Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8168%2fis-it-legal-to-have-the-c-2019-john-smith-header-in-all-files-when-there%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            Adding axes to figuresAdding axes labels to LaTeX figuresLaTeX equivalent of ConTeXt buffersRotate a node but not its content: the case of the ellipse decorationHow to define the default vertical distance between nodes?TikZ scaling graphic and adjust node position and keep font sizeNumerical conditional within tikz keys?adding axes to shapesAlign axes across subfiguresAdding figures with a certain orderLine up nested tikz enviroments or how to get rid of themAdding axes labels to LaTeX figures

            Luettelo Yhdysvaltain laivaston lentotukialuksista Lähteet | Navigointivalikko

            Gary (muusikko) Sisällysluettelo Historia | Rockin' High | Lähteet | Aiheesta muualla | NavigointivalikkoInfobox OKTuomas "Gary" Keskinen Ancaran kitaristiksiProjekti Rockin' High