-
Notifications
You must be signed in to change notification settings - Fork 30.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syntax Highlighting license #27397
Comments
#22831 replaces the file but that PR appears to have stalled. |
This is currently discussed in a more generic fashion in #30241. |
SHJS was removed from this repository in #33442 (@DerekNonGeneric 🎉), but I am not sure if it can/should be removed from nodejs/nodejs.org too? |
@BethGriggs, the website appears to be using Prism. Please see the comment below.
Were you thinking to use highlight.js everywhere? |
The old docs, e.g. https://nodejs.org/docs/latest-v0.10.x/api/, reference https://nodejs.org/sh_main.js and https://nodejs.org/sh_javascript.min.js (also see the README in https://github.com/nodejs/nodejs.org/tree/master/static/legacy). |
What action is needed here then? |
Ping @BethGriggs |
As SHJS is still used for the legacy documentation I do not see what we can do about this. Perhaps we can just close as we've now moved away from it in Node.js core. |
Yes, we would not want to have old versions' docs un-syntax-highlighted. That would be barbaric. |
This might not be an issue, but one of our scanning tools picked up on it so thought I'd post it for discussion anyway.
Syntax Highlighting JS (https://github.com/nodejs/node/blob/master/doc/api_assets/sh_main.js) has a GPLv3 license. It is only used in the docs, but I don't know if this could have implications if anyone was to redistribute the docs (perhaps unlikely?).
Should the license potentially be listed/mentioned somewhere else in addition to the file itself?
I notice that SHJS is also over in nodejs/nodejs.org. Do we still need it in nodejs/node, could it be pulled in from nodejs.org? (refs: nodejs/nodejs.org#2150 (comment)).
Admittedly I do not know the history of this file/docs. /cc @nodejs/documentation
The text was updated successfully, but these errors were encountered: