4 ms·

I and a friend wrote a tool to check your repositories with this API: http://put-a-license-on.it/ http://put-a-license-on.it/

shared4you 12y ago
Thanks, cool tool ! A suggestion: Making the first column to have URL linking to the repo's homepage would be useful.
tracker1 12y ago
Cool.. though it only seems to return 6 repositories...
olig15 12y ago
It doesn't seem to do anything after it gets a 404 back from the github API on an incorrect username.
ImJasonH 12y ago
This is great, I was considering making something like this myself. A few suggestions: - It seems to run out of quota very quickly, I get 403s after listing the repos of just a few users. - The "Click here" for adding a license just plops me into a page to add a file to the repo. With some work, this could be replaced with a dropdown to choose the license, and it could send a Pull Request to add it (or ask for the user's permission to add it directly!) - I don't see any links to the code for this, in case I want to check it out or send a Pull Request (to fix the issues listed above, for example). But, great job so far, this should make it just a bit easier to add a license to your repos.
- joshschreuder 12y ago
  If you type LICENSE into the filename box, Github provides a dropdown of licenses to choose from. https://i.imgur.com/opCBKHT.png https://i.imgur.com/opCBKHT.png With that in mind, it would be nice if the Put A License On It site could open to the create screen with the filename filled in with LICENSE. This can be done using the following URL pattern: https://github.com/[user]/[repo]/new/master?filename=LICENSE https://github.com/[user]/[repo]/new/master?filename=LICENSE
cheald 12y ago
This is super handy, but it only returned 8 repos out of scores for me!
jfroma 12y ago
it will be nice if I can choose the license on the tool and the tool make a PR automatically
erikano 12y ago
For one of my repositories which I created in 2013 and then pretty much forgot about without having written any code, the license file is called COPYRIGHT instead of LICENSE because back then I thought back then that COPYRIGHT was a good name for the license file. Anyway, getting to the point: 1. While I personally have switched to naming my license files LICENSE rather than COPYRIGHT, I think others still do name their license file COPYRIGHT, so you might want to check for such a file as well (or is it github who should detect that?) 2. The link "Click here!" you provide leads me to https://github.com/erikano/pgviz/new/master https://github.com/erikano/pgviz/new/master where I am given a 404 by github. The reason being that I do not have a master branch in that repository but instead I have one called "devel". 3. I think you should change the link text from "Click here!" to "Put a license on it". With that being said, I think the tool you wrote is nice and I also got a warm and fuzzy feeling from seeing that all the repositories it checked on my github returned "ISC" (aside from the one mentioned above and aside from the github pages repository which I have intentionally left without a license due to its special nature). Off topic sidenote to anyone reading this: Most of my repositories are old I ideas I had but never executed on so they are mostly empty and almost none of them have any code. During late 2014 and most of this year, I have been working actively on two projects. None of those two are ready for use yet but there is code. One is saas-by-erik/timelog (written in C) and the other is erikano/django-timelog (Python/Django), both licensed under ISC. So if, for whatever reason, you are going to look at anything on my githubs, please look at those two. And if you feel like it, read the code and tell me where you think I'm doing something you think there is a better way to do, though note that the one I'm writing in C, I want to emphasize speed whereas for the one written in Python using Django, I currently do not worry about performance and will leave optimization of the latter (including queries eventually executed by PostgreSQL through Django) until a later point of the development. That being said, since I will optimize django-timelog at some point, if you do notice something in my code which is obviously killing performance, I will be happy for any issues reported where you tell me what you see. Sorry for this long off topic note but I felt I should add it, hope nobody is too bothered about it.
TazeTSchnitzel 12y ago
Doesn't spot that a few of my older repos have a license within the README. Surprisingly doesn't recognise GPLv3.

shared4you 12y ago

Thanks, cool tool ! A suggestion: Making the first column to have URL linking to the repo's homepage would be useful.

tracker1 12y ago

Cool.. though it only seems to return 6 repositories...

olig15 12y ago

It doesn't seem to do anything after it gets a 404 back from the github API on an incorrect username.

ImJasonH 12y ago

This is great, I was considering making something like this myself. A few suggestions: - It seems to run out of quota very quickly, I get 403s after listing the repos of just a few users. - The "Click here" for adding a license just plops me into a page to add a file to the repo. With some work, this could be replaced with a dropdown to choose the license, and it could send a Pull Request to add it (or ask for the user's permission to add it directly!) - I don't see any links to the code for this, in case I want to check it out or send a Pull Request (to fix the issues listed above, for example). But, great job so far, this should make it just a bit easier to add a license to your repos.

joshschreuder 12y ago
If you type LICENSE into the filename box, Github provides a dropdown of licenses to choose from. https://i.imgur.com/opCBKHT.png https://i.imgur.com/opCBKHT.png With that in mind, it would be nice if the Put A License On It site could open to the create screen with the filename filled in with LICENSE. This can be done using the following URL pattern: https://github.com/[user]/[repo]/new/master?filename=LICENSE https://github.com/[user]/[repo]/new/master?filename=LICENSE

cheald 12y ago

This is super handy, but it only returned 8 repos out of scores for me!

jfroma 12y ago

it will be nice if I can choose the license on the tool and the tool make a PR automatically

erikano 12y ago

For one of my repositories which I created in 2013 and then pretty much forgot about without having written any code, the license file is called COPYRIGHT instead of LICENSE because back then I thought back then that COPYRIGHT was a good name for the license file. Anyway, getting to the point: 1. While I personally have switched to naming my license files LICENSE rather than COPYRIGHT, I think others still do name their license file COPYRIGHT, so you might want to check for such a file as well (or is it github who should detect that?) 2. The link "Click here!" you provide leads me to https://github.com/erikano/pgviz/new/master https://github.com/erikano/pgviz/new/master where I am given a 404 by github. The reason being that I do not have a master branch in that repository but instead I have one called "devel". 3. I think you should change the link text from "Click here!" to "Put a license on it". With that being said, I think the tool you wrote is nice and I also got a warm and fuzzy feeling from seeing that all the repositories it checked on my github returned "ISC" (aside from the one mentioned above and aside from the github pages repository which I have intentionally left without a license due to its special nature). Off topic sidenote to anyone reading this: Most of my repositories are old I ideas I had but never executed on so they are mostly empty and almost none of them have any code. During late 2014 and most of this year, I have been working actively on two projects. None of those two are ready for use yet but there is code. One is saas-by-erik/timelog (written in C) and the other is erikano/django-timelog (Python/Django), both licensed under ISC. So if, for whatever reason, you are going to look at anything on my githubs, please look at those two. And if you feel like it, read the code and tell me where you think I'm doing something you think there is a better way to do, though note that the one I'm writing in C, I want to emphasize speed whereas for the one written in Python using Django, I currently do not worry about performance and will leave optimization of the latter (including queries eventually executed by PostgreSQL through Django) until a later point of the development. That being said, since I will optimize django-timelog at some point, if you do notice something in my code which is obviously killing performance, I will be happy for any issues reported where you tell me what you see. Sorry for this long off topic note but I felt I should add it, hope nobody is too bothered about it.

TazeTSchnitzel 12y ago

Doesn't spot that a few of my older repos have a license within the README. Surprisingly doesn't recognise GPLv3.