Giters

greghendershott / frog

Frog is a static blog generator implemented in Racket, targeting Bootstrap and able to use Pygments.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

License status question

andybp85 opened this issue · comments

commented

I saw the MIT button, but just realized the license says "All rights reserved". So, wondering if forking Frog is okay?

Full disclosure, I've already forked it and did a bunch of work for how I'd like my blog and workflow set up: GFrog. This is a learning project for me (first-ever Racket/Lisp project!) and I'm not looking for credit or even planning on uploading to the Racket Package Index or anything. I'm happy as long as I can use it to make my own blog, and will gladly take down the public repo if you want.

Either way, thanks so much for making this in the first place, and for Cakewalk - fellow musician here :)

commented

@andybp85 I'm sorry to be slow to reply. I saw this but I was too swamped to find time to think about it. Also it has been this way for something like 5 years, so it seemed important but not urgent.

@sivark Thank you for the link.

My current thinking is to:

  1. Switch to Apache 2.0 License. (Why: Racket is switching to that. It's clearer about various issues.)

  2. Update the source files themselves with the preamble:

Copyright [yyyy] [name of copyright owner]

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

On the other hand:

  1. I'm in no rush.
  2. I don't know what's involved in changing a license.