docs/choosealicense.com
docs/choosealicense.com
1
0
Fork 0
mirror of https://github.com/github/choosealicense.com synced 2024-11-05 03:08:51 +01:00
Code Issues Releases Wiki Activity
5 Commits 2 Branches 0 Tags 5.1 MiB
Ruby 33.3%
HTML 26.4%
SCSS 20.4%
CoffeeScript 12.1%
CSS 7%
Other 0.8%
a0682d2b99
Go to file
Haacked a0682d2b99 Adding proper gitignore and gitattributes file
2012-06-12 20:04:45 -07:00
css Adding some mock-up pages 2012-06-12 16:59:32 -07:00
images First cut at a landing page 2012-06-08 17:19:25 +02:00
licenses Adding some mock-up pages 2012-06-12 16:59:32 -07:00
.gitattributes Adding proper gitignore and gitattributes file 2012-06-12 20:04:45 -07:00
.gitignore Adding proper gitignore and gitattributes file 2012-06-12 20:04:45 -07:00
favicon.ico First cut at a landing page 2012-06-08 17:19:25 +02:00
index.html Adding some mock-up pages 2012-06-12 16:59:32 -07:00
README.md Added a goal of _not_ being comprehensive. 2012-04-18 13:41:21 -07:00

README.md

Choose a License Web Site

Like a Choose Your Own Adventure site, but only much less interesting.

Intro

A lot of repositories on GitHub.com don't have a license. GitHub could slap on a license chooser, but if you don't know anything about licenses, how are you supposed to make an informed decision.

ChooseALicense.com is designed to help people make an informed decision about licenses.

Immediate Goals

  • Politics Free - Let's just not get into it.
  • Well designed, but that goes without saying.
  • The homepage should have just enough to help 99% of folks make a decision.
  • For the 1%, the site will contain a license chooser similar to the creative commons license chooser
  • Not comprehensive. Seems like an odd goal, but there are a bajillion (I counted) licenses out there. We're going to have to filter that down to a small list of those that matter.

Design

I think v1 of the site could be a completely static JavaScript site. No need for a back end until we actually need it.

Community

We plan to build out the skeleton of the site privately first, but then open it up to accept contributions.

Phil will look into whether various open source foundations and lawyers would be interested in being involved. Probably makes good sense to have a lawyer review the content before we post it live.