Skip to content
This repository has been archived by the owner on Feb 24, 2021. It is now read-only.

Remove maintainer repeating task for LICENSE file #460

Open
johlju opened this issue Sep 27, 2018 · 7 comments
Open

Remove maintainer repeating task for LICENSE file #460

johlju opened this issue Sep 27, 2018 · 7 comments
Labels
documentation The issue is related to documentation only. help wanted The issue is up for grabs for anyone in the community.

Comments

@johlju
Copy link
Contributor

johlju commented Sep 27, 2018

In new repositories that are created by the Microsoft Open Source Team, the LICENSE file does not contain the year in the copyright "header".
I suggest we remove it from the repeating task, and all repositories can remove the year.

https://github.com/PowerShell/DscResources/blob/master/Maintainers.md#license

This is how the MIT license look like in a newly created repository (indentation and all).

    MIT License

    Copyright (c) Microsoft Corporation. All rights reserved.

    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.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
    IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
    FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
    AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
    LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
    OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
    SOFTWARE
@johlju johlju added help wanted The issue is up for grabs for anyone in the community. documentation The issue is related to documentation only. labels Sep 27, 2018
@PlagueHO
Copy link
Contributor

That would be good! No more updating the License every year. I've started to use this new format in my personal resources now.

@timhaintz
Copy link
Contributor

timhaintz commented Oct 24, 2018

@johlju @PlagueHO sign me up for this one if you like. 👍
Do you just want the repeating tasks section done and/or each LICENSE file updated in the resources too?
Thanks, Tim.

@PlagueHO
Copy link
Contributor

Awesome! Thanks @timhaintz . We want to add an issue to each resource repo to update the license and then submit a PR to update it. I've done some of the ones I maintain already (cant recall which ones) but many others haven't been done.

@timhaintz
Copy link
Contributor

timhaintz commented Oct 25, 2018

Looking at Maintainers.md, do you want:

  • Change copyright information
  • Module manifest
  • License

removed? Did you want to store the contents of the MIT License in the Maintainers.md file?

PR incoming with what I think you're looking for.

Thanks, Tim.

@timhaintz
Copy link
Contributor

Going through my issues history, do I need to do anything else with this on @PlagueHO @johlju ?
Thanks, Tim.

@johlju
Copy link
Contributor Author

johlju commented Jan 30, 2019

@timhaintz Looking at this PR now, sorry I have missed this one!

@timhaintz
Copy link
Contributor

No worries @johlju . Was doing some housekeeping on past issues.
Thanks, Tim.

kwirkykat pushed a commit that referenced this issue Feb 13, 2019
* Updated LICENSE with updating as per [Issue 460](#460).

* Updated Repeating tasks section to include new Copyright wording. As per [Issue 460](#460).

* Updated Maintainers.md License File contents section to refeence this repo's LICENSE file.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
documentation The issue is related to documentation only. help wanted The issue is up for grabs for anyone in the community.
Projects
None yet
Development

No branches or pull requests

3 participants