A lot of people just forget to put up a license. I file a polite bug with the project, and they generally fix it within a day or so.
My point goes further than people forgetting to add a license, though. Some people think that just adding it as an open repo to GitHub is enough, which, depending on the country, it clearly isn’t.
In my opinion, GitHub should educate people a bit more about this. A simple feature like this could just be enough.
I know that personally, I've relicensed code to be more permissive on request. Of course, you have to ask, but sending an email might be less work than writing your own version.
On the other hand, I have asked several developers who released code without a license if they would mind licensing their code under a permissive license, and each time they have been glad to do so.
Just some anecdotal data...
The downside is, of course, that you probably need it at the time you come across it, so time wise I often have to roll my own in these cases. That’s why I hope this would make that more clear.
On that note, we need this for gists as well (maybe even more). Could be on an account-wide basis in my case.
If it's a ilbrary that fetches RSS feeds as part of a larger system, I'm guessing no.
Of course, it also depends significantly on the author. If it's a public git repository, one assumes that it's something people wish to be forked.
Though I suppose an interesting experiment would be to publicly post closed source code with a closed source license attached as honeypots and sue everyone that forks / modifies your code base.
I suppose you could write a license that allows others to view and copy your code, but not make any modifications, as fork doesn't seem to be defined to include modification.