Bob Ippolito wrote:
I think this patch is against an older version; I updated the
Javascript recently to do better highlighting. But I haven't
actually tried applying it. Ryan can give you commit access too if
you want it.
It was definitely against the trunk when I wrote it about a week ago
:) Commit access would be fine, not promising I'd use it much but it'd
make things a little easier for me if I find an issue.
That's basically how things happen to pudge ;) Such is the life of
project support code.
I was actually thinking that simplejson might have a better home under
the lesscode umbrella too.
I don't know how Ryan has lesscode set up...?
In the future, it would be nice if more license templates were in
there. Personally I'd like to use either a public domain or CC
attribution license. No patch on this one:
http://lesscode.org/projects/pudge/ticket/6
Do we need to include the text of the license on the site itself? Is
a link to the original license sufficient? If so, I'd like to make
the license field at least optionally a link.
I don't know, I was just following the convention of the two included
licenses. Seems strange to only provide two choices, both of which
kinda have the same implications.
It includes the license(s) that Ryan used, I think that's all. For a
lax license, a casual link to a license seems more than suffcient to me.
--
Ian Bicking | [EMAIL PROTECTED] | http://blog.ianbicking.org
_______________________________________________
Pudge mailing list
[email protected]
http://lesscode.org/mailman/listinfo/pudge
