Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Add an Apache v2 License to cChoco #70

Closed
ferventcoder opened this issue Apr 18, 2017 · 34 comments
Closed

Add an Apache v2 License to cChoco #70

ferventcoder opened this issue Apr 18, 2017 · 34 comments
Assignees
@ferventcoder
Labels
2 - Working Documentation
Milestone
2.4.0

Comments

@ferventcoder
Copy link
Member

Howdy @chocolatey/powershelldsc - What was the original intent for licensing here?
@ferventcoder
Copy link
Member Author

ferventcoder commented Apr 18, 2017 •
edited
Loading

I'd love to set an Apache v2 License on this code, however to move from no license to a license requires a thumbs up from contributors.

For every person identified, you must create a comment on this issue so that the licensing can be added. The apache v2 license is super business friendly and can be found at https://www.apache.org/licenses/LICENSE-2.0.html (it's the same license that Chocolatey uses for all of its open source repositories).

If your name has been identified, please add a comment that says "I agree with a move to Apache v2 licensing for my contributions to this repository." A simple thumbs up will not be enough.

@ferventcoder
Copy link
Member Author

I agree with a move to Apache v2 licensing for my contributions to this repository.

@ferventcoder ferventcoder changed the title LICENSE? Add an Apache v2 License to cChoco Apr 18, 2017
@ferventcoder ferventcoder self-assigned this Apr 18, 2017
@smurawski
Copy link
Contributor

I agree with the move to Apache v2 for licensing my contributions to this repository

@javydekoning
Copy link
Contributor

I agree with a move to Apache v2 licensing for my contributions to this repository.

1 similar comment
@ptoonen
Copy link
Contributor

ptoonen commented Apr 19, 2017

I agree with a move to Apache v2 licensing for my contributions to this repository.

@lawrencegripper
Copy link
Contributor

I agree with a move to Apache v2 licensing for my contributions to this repository

History

When I first wrote the resource it was submitted to the powershellorg as a PR to a repo which grouped together lots of community dsc resources and already had a license. @smurawski pulled out the code and committed it to a new repo to make it easier to manage for me and likely that's when we missed the licensing going missing.

@bgelens
Copy link
Contributor

bgelens commented Apr 19, 2017

I agree with the move to Apache v2 for licensing my contributions to this repository

@bozho
Copy link
Contributor

bozho commented Apr 19, 2017

I agree with a move to Apache v2 licensing for my contributions to this repository.

@ferventcoder
Copy link
Member Author

Still waiting on a few more, especially @ebekker, @mrpullen, and @RobFaie

@ferventcoder
Copy link
Member Author

If we can't get all folks to sign off on this, we will need to rewrite the sections of code that were contributed so we can move forward with the licensing. I'm not keen on that, so hopefully folks are able to agree with the change.

@ebekker
Copy link
Contributor

ebekker commented Apr 21, 2017

I agree with a move to Apache v2 licensing for my contributions to this repository.

@ferventcoder
Copy link
Member Author

Ping @mrpullen @RobFaie @kcighon @dlwyatt @sebastus @absolutejam

@dlwyatt
Copy link
Contributor

dlwyatt commented Apr 28, 2017

I agree with a move to Apache v2 licensing for my contributions to this repository.

1 similar comment
@sebastus
Copy link
Contributor

I agree with a move to Apache v2 licensing for my contributions to this repository.

@ferventcoder
Copy link
Member Author

And then there were four @mrpullen @RobFaie @kcighon @absolutejam. If anyone knows these folks, can you help me reach out to them?

@ferventcoder
Copy link
Member Author

I sent an email to @absolutejam as that was listed in James' GitHub profile.

@mrpullen
Copy link
Contributor

mrpullen commented May 16, 2017 via email •
edited by ferventcoder
Loading

@ferventcoder
Copy link
Member Author

Ones we would not necessarily need to rewrite to change the licensing:

However I would really like to get @RobFaie 's signoff - https://github.com/chocolatey/cChoco/commits?author=RobFaie

@ferventcoder
Copy link
Member Author

@ITGuyOU your commit came after, but would you mind also responding here?

@ferventcoder
Copy link
Member Author

ferventcoder commented May 16, 2017 •
edited
Loading

@mrpullen Thank you!

@ferventcoder
Copy link
Member Author

I may have found @RobFaie through LinkedIn and have reached out.

@absolutejam
Copy link
Contributor

Sorry for the inconvenience, I saw this issue had some activity but I didn't realising you were waiting for me! I think it's a great idea to move to the Apache 2 license.

'I agree with a move to Apache v2 licensing for my contributions to this repository.'

@ferventcoder
Copy link
Member Author

@absolutejam thanks!

@RobFaie
Copy link
Contributor

RobFaie commented May 17, 2017

All good with me.

@ferventcoder
Copy link
Member Author

@RobFaie thanks for that. Is there a chance you could provide the official wording requested?

@variableresistor
Copy link
Contributor

I agree with the move to Apache v2 for licensing my contributions to this repository

@ferventcoder
Copy link
Member Author

Thanks @ITGuyOU !

@variableresistor
Copy link
Contributor

Sorry for the delay, @ferventcoder . I've been hunting for a new employer, which has kept me tied up.

@ferventcoder
Copy link
Member Author

No worries sir, I did not include your name on this until recently.

@RobFaie
Copy link
Contributor

RobFaie commented May 22, 2017

I agree with a move to Apache v2 licensing for my contributions to this repository.

1 similar comment
@Jark
Copy link
Contributor

Jark commented Jun 21, 2017

I agree with a move to Apache v2 licensing for my contributions to this repository.

@Jark Jark mentioned this issue Jun 21, 2017
Merged
@kcighon
Copy link
Contributor

kcighon commented Jun 21, 2017

Apologies for delayed response - I agree with a move to Apache v2 licensing for my contributions to this repository.

@variableresistor
Copy link
Contributor

variableresistor commented Jun 28, 2017 via email

ferventcoder added a commit that referenced this issue Jul 14, 2017
@ferventcoder
(GH-70) Apply Apache v2 Licensing
1161e86 
Apply Apache v2 licensing to the repository - received sign off from all
current contributors.
@ferventcoder
Copy link
Member Author

Apache v2 licensing has been applied. Thanks all!!

ferventcoder added a commit that referenced this issue Aug 29, 2017
@ferventcoder
Merge branch 'development'
aeb501f 
* development:
  (GH-71) Implemented cChocoFeature
  (GH-87) Moved to using reduced output
  (maint) formatting
  (GH-70) Apply Apache v2 Licensing
  (GH-85) Pass the source to cChocoPackageInstallerSet correctly
  (GH-44) Pass the Source to choco correctly
  Added version to example
  (GH-77) Push to gallery on new tags
  (maint) formatting
  (GH-72) PowerShell scripts in format for signing
jrdnr added a commit to jrdnr/cChoco that referenced this issue Sep 1, 2017
@jrdnr
Merge branch 'development' into (chocolateyGH-90)_Cache_InstalledPack…
624a8fb 
…ages_for_faster_run

* development:
  (chocolateyGH-87) Moved to using reduced output
  (maint) formatting
  (chocolateyGH-70) Apply Apache v2 Licensing
  (chocolateyGH-85) Pass the source to cChocoPackageInstallerSet correctly
  (chocolateyGH-44) Pass the Source to choco correctly
  Added version to example
  (chocolateyGH-77) Push to gallery on new tags
  (maint) formatting
  (chocolateyGH-72) PowerShell scripts in format for signing

# Conflicts:
#	DSCResources/cChocoPackageInstall/cChocoPackageInstall.psm1
@pauby pauby added this to the 2.4.0 milestone Nov 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ferventcoder ferventcoder

Labels
2 - Working Documentation
Projects
None yet
Milestone
2.4.0
Development

No branches or pull requests