I have some source code for which I am the copyright holder. I want to release it under the GPL, but when it was closed source, I copied a bunch of a stuff from Wikipedia for a couple of classes and used it strictly for comments. This was just a matter of convenience, I have classes that allow you to manipulate HTTP headers and didn't feel like writing out explanations for each header when it was right there in front of me.
/// <summary> /// CGI header field specifying the status of the HTTP response. Normal HTTP /// responses use a separate "Status-Line" instead, defined by RFC 7230. /// Example: Status: 200 OK /// </summary> const std::string& Status(void);
All of the lines proceeded by a
/// are the comments. When the source code is compiled, these comments are not included in the final produced product, so I never considered it an issue as closed source software. However, I'd now be publishing all of this, comments intact.
The comments originate from this wikipedia page, where the footer includes a link to this license, which is the Creative Commons Attribution-ShareAlike 3.0 Unported License.
I've tried to search manually for anything about dual-licensing or licensing the comments separately from the code itself, but my searches have yielded nothing. Is it possible to fulfill the creative commons license by licensing the comments, aka "documentation", separately from the source code implementation?