Cook should strip jQuery plugins' license

[FND]

Including the license text of TiddlyWiki's own jQuery plugins seems redundant.

[JeremyRuston]

I guess we could do this rather straightforwardly by preceding the license text with //#?

I suspect that if these are separately licensed components, then it is clearer if they each to separately carry license information.

[FND]

Replying to JeremyRuston:

I guess we could do this rather straightforwardly by preceding the license text with //#?

While that would work for us (i.e. when using Cook), it would look rather odd to someone not familiar with TiddlyiWiki? idiosyncrasies (i.e. developers just interested in the individual jQuery plugin).

However, if we could teach Cook to understand multi-line blocks (/*# ... #*/), that would be decidedly less confusing (and also useful for code documentation).

Replying to JeremyRuston:

I suspect that if these are separately licensed components, then it is clearer if they each to separately carry license information.

Well, when integrated into TiddlyWiki, they become part of that distribution and thus carry its license. So separate licensing (and thus license information) should only be required when used outside of TiddlyWiki.

We could, however, make a note to highlight that these are generic, reusable components.

[MartinBudden]

Milestone 2.6.2 deleted

[cdent]

This doesn't seem very important in any immediate sense.