Proper use of Wikipedia code sample in open source projectsUsing code from WikipediaCan I open source my music which includes copyrighted sound effects?Practical implications of using bsd licensed codeChoosing a license based on conditions or an extensible licenseAGPL v3 licensing: How does external party determine if modifications were made?What is defined as trivial code when licensing a projectUsing GPL resource (with separate installation) with “commercial” productWhat's the usual procedure when using MIT or BSD-2-Clause licensed source code with something like `<script src="…`, `require(…` or `import …`?Commercial print (shirt) of GitHub repositoryThird-party component licensing obligations, usage and obligations scaleLicense Selection for An Open Document Project with Codes

How to make a not so good looking person more appealing?

Assembly writer vs compiler

Can my Serbian girlfriend apply for a UK Standard Visitor visa and stay for the whole 6 months?

Why doesn't Iron Man's action affect this person in Endgame?

Single word that parallels "Recent" when discussing the near future

How to rename multiple files in a directory at the same time

Why are goodwill impairments on the statement of cash-flows of GE?

Was the dragon prowess intentionally downplayed in S08E04?

Is there an academic word that means "to split hairs over"?

What do the "optional" resistor and capacitor do in this circuit?

My bread in my bread maker rises and then falls down just after cooking starts

Should generated documentation be stored in a Git repository?

Holding rent money for my friend which amounts to over $10k?

Can I say: "When was your train leaving?" if the train leaves in the future?

Would life always name the light from their sun "white"

Capital gains on stocks sold to take initial investment off the table

How to redirect stdout to a file, and stdout+stderr to another one?

What is the effect of the Feeblemind spell on Ability Score Improvements?

Proper way to use apply_filters() with class functions?

Does this "yield your space to an ally" rule my 3.5 group uses appear anywhere in the official rules?

Windows 10 lock screen - display my own random images

Can a tourist shoot a gun in the USA?

Why can't I share a one use code with anyone else?

Why did Varys remove his rings?



Proper use of Wikipedia code sample in open source projects


Using code from WikipediaCan I open source my music which includes copyrighted sound effects?Practical implications of using bsd licensed codeChoosing a license based on conditions or an extensible licenseAGPL v3 licensing: How does external party determine if modifications were made?What is defined as trivial code when licensing a projectUsing GPL resource (with separate installation) with “commercial” productWhat's the usual procedure when using MIT or BSD-2-Clause licensed source code with something like `<script src="…`, `require(…` or `import …`?Commercial print (shirt) of GitHub repositoryThird-party component licensing obligations, usage and obligations scaleLicense Selection for An Open Document Project with Codes













3















Many Wikipedia articles contain code or pseudocode samples. I implemented a pseudocode snippet in a concrete language and am planning to use it in one of my projects. There's another question on here asking about the usage of such code in commercial projects. In contrast to that question, my project will be non-commercial and open source and I was wondering how to properly include such code snippets without violating reuse terms.



In particular, one of the licences recommended by Wikipedia is the GNU Free Documentation Licence. The very last section describes how to use this license, but this seems to apply to more traditional "documents" instead of source code. There's also a recommentation to publish any code separately under the GPL but most code snippets published on Wikipedia don't seem to abide by this. So my question is whether (and how) I can still use those snippets (or reimplementations thereof) in open source projects.










share|improve this question
























  • It's worth looking at the references to see where Wikipedia got the algorithms you're interested in. A quick search reveals that many algorithms on Wikipedia appear to be copied straight from programming books such as Programming Pearls and Cormen et al's Introduction to Algorithms.

    – Brandin
    May 4 at 4:41















3















Many Wikipedia articles contain code or pseudocode samples. I implemented a pseudocode snippet in a concrete language and am planning to use it in one of my projects. There's another question on here asking about the usage of such code in commercial projects. In contrast to that question, my project will be non-commercial and open source and I was wondering how to properly include such code snippets without violating reuse terms.



In particular, one of the licences recommended by Wikipedia is the GNU Free Documentation Licence. The very last section describes how to use this license, but this seems to apply to more traditional "documents" instead of source code. There's also a recommentation to publish any code separately under the GPL but most code snippets published on Wikipedia don't seem to abide by this. So my question is whether (and how) I can still use those snippets (or reimplementations thereof) in open source projects.










share|improve this question
























  • It's worth looking at the references to see where Wikipedia got the algorithms you're interested in. A quick search reveals that many algorithms on Wikipedia appear to be copied straight from programming books such as Programming Pearls and Cormen et al's Introduction to Algorithms.

    – Brandin
    May 4 at 4:41













3












3








3








Many Wikipedia articles contain code or pseudocode samples. I implemented a pseudocode snippet in a concrete language and am planning to use it in one of my projects. There's another question on here asking about the usage of such code in commercial projects. In contrast to that question, my project will be non-commercial and open source and I was wondering how to properly include such code snippets without violating reuse terms.



In particular, one of the licences recommended by Wikipedia is the GNU Free Documentation Licence. The very last section describes how to use this license, but this seems to apply to more traditional "documents" instead of source code. There's also a recommentation to publish any code separately under the GPL but most code snippets published on Wikipedia don't seem to abide by this. So my question is whether (and how) I can still use those snippets (or reimplementations thereof) in open source projects.










share|improve this question
















Many Wikipedia articles contain code or pseudocode samples. I implemented a pseudocode snippet in a concrete language and am planning to use it in one of my projects. There's another question on here asking about the usage of such code in commercial projects. In contrast to that question, my project will be non-commercial and open source and I was wondering how to properly include such code snippets without violating reuse terms.



In particular, one of the licences recommended by Wikipedia is the GNU Free Documentation Licence. The very last section describes how to use this license, but this seems to apply to more traditional "documents" instead of source code. There's also a recommentation to publish any code separately under the GPL but most code snippets published on Wikipedia don't seem to abide by this. So my question is whether (and how) I can still use those snippets (or reimplementations thereof) in open source projects.







licensing gpl wikipedia






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited May 3 at 19:39









MadHatter

10.5k12042




10.5k12042










asked May 3 at 17:54









PeterPeter

1333




1333












  • It's worth looking at the references to see where Wikipedia got the algorithms you're interested in. A quick search reveals that many algorithms on Wikipedia appear to be copied straight from programming books such as Programming Pearls and Cormen et al's Introduction to Algorithms.

    – Brandin
    May 4 at 4:41

















  • It's worth looking at the references to see where Wikipedia got the algorithms you're interested in. A quick search reveals that many algorithms on Wikipedia appear to be copied straight from programming books such as Programming Pearls and Cormen et al's Introduction to Algorithms.

    – Brandin
    May 4 at 4:41
















It's worth looking at the references to see where Wikipedia got the algorithms you're interested in. A quick search reveals that many algorithms on Wikipedia appear to be copied straight from programming books such as Programming Pearls and Cormen et al's Introduction to Algorithms.

– Brandin
May 4 at 4:41





It's worth looking at the references to see where Wikipedia got the algorithms you're interested in. A quick search reveals that many algorithms on Wikipedia appear to be copied straight from programming books such as Programming Pearls and Cormen et al's Introduction to Algorithms.

– Brandin
May 4 at 4:41










2 Answers
2






active

oldest

votes


















3














When merely copying small snippets of code, it may be worth considering whether the use could be covered by a copyright exception, such as fair use in the US. Because if some exception applies you won't have to consider the licensing. You would still have to properly attribute the snippet, of course. Note also that while pseudocode is copyrightable, the underlying algorithm cannot be copyrighted.



If no exception applies, you would have to follow the license under which you acquired the snippet.



Wikipedia is generally dual-licensed under the GFDL and CC-BY-SA 3.0, though individual pages may differ (that should be noted on the page, though).



The GFDL can be understood as a historical artefact. Wikipedia originally used this license. However, the GFDL is highly incompatible with other licenses, and is geared towards books rather than websites. Compliance can be rather cumbersome. It is not compatible with any licenses that are used for source code.



A later version of the GFDL added a relicensing clause that made it possible for Wikipedia (but no one else) to relicense to CC-BY-SA 3.0. Wikipedia exercised that clause, and has been using dual-licensing with GFDL/CC-BY-SA 3.0 for roughly a decade now.



The CC-BY-SA 3.0 license has a much better compatibility story. In particular, you can choose to license adaptions a later license version, CC-BY-SA 4.0 allows you to use a compatible license, and Creative Commons has named the GPLv3 as a compatible license.



That means the full list of licenses that you can use code snippets from Wikipedia under include:




  • GFDL (unversioned)


  • CC-BY-SA 3.0 (explicit dual-license, and compatible licenses per GFDL 1.3 section 11)

    • compatible licenses per section 4(b) (adaptations only!)

      • jurisdiction-ported versions of CC-BY-SA 3.0

      • compatible licenses at https://creativecommons.org/compatiblelicenses (none)

      • later CC-BY-SA versions


        • CC-BY-SA 4.0

          • compatible licenses per section 3(b)(1) (adaptations only!)

            • later CC-BY-SA versions (none)

            • compatible licenses at https://creativecommons.org/compatiblelicenses


              • Free Art License 1.3

                • compatible licenses under section 5 (unclear)



              • GPLv3


                • AGPLv3 per GPLv3 section 13








So an open source project really only has the option to copy code snippets from Wikipedia if the project uses GPLv3 or AGPLv3 licenses. Note this excludes many popular licenses such as MIT, LGPL, GPLv2, GPLv2+, GPLv3+, and so on.






share|improve this answer






























    4














    IANAL/IANYL, but provided you're happy with making your content available under GPLv3, you should be fine.



    You're planning on implementing the Wikipedia-provided pseudocode in other languages, which means you're creating a derivative work (or, as CC refers to it, Adapted Material). Content in Wikipedia may be reused under CC-BY-SA 3.0 or later. The next such later version, CC-BY-SA 4.0, says that




    if You Share Adapted Material You produce, the following conditions also apply



    ...



    The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.




    and one such compatible licence is GPLv3. So by passing through CC-BY-SA 4.0 you can get permission to license your derivative under GPLv3, at which point it becomes absolutely standard free software.






    share|improve this answer























    • Great answer, I ended up accepting amons because it contains additional information.

      – Peter
      May 4 at 7:23











    • @Peter thank you for that! I entirely agree, and upvoted Amon's answer myself, for the same reason :)

      – MadHatter
      May 4 at 12:45











    Your Answer








    StackExchange.ready(function()
    var channelOptions =
    tags: "".split(" "),
    id: "619"
    ;
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function()
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled)
    StackExchange.using("snippets", function()
    createEditor();
    );

    else
    createEditor();

    );

    function createEditor()
    StackExchange.prepareEditor(
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader:
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    ,
    noCode: true, onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    );



    );













    draft saved

    draft discarded


















    StackExchange.ready(
    function ()
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8262%2fproper-use-of-wikipedia-code-sample-in-open-source-projects%23new-answer', 'question_page');

    );

    Post as a guest















    Required, but never shown

























    2 Answers
    2






    active

    oldest

    votes








    2 Answers
    2






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    3














    When merely copying small snippets of code, it may be worth considering whether the use could be covered by a copyright exception, such as fair use in the US. Because if some exception applies you won't have to consider the licensing. You would still have to properly attribute the snippet, of course. Note also that while pseudocode is copyrightable, the underlying algorithm cannot be copyrighted.



    If no exception applies, you would have to follow the license under which you acquired the snippet.



    Wikipedia is generally dual-licensed under the GFDL and CC-BY-SA 3.0, though individual pages may differ (that should be noted on the page, though).



    The GFDL can be understood as a historical artefact. Wikipedia originally used this license. However, the GFDL is highly incompatible with other licenses, and is geared towards books rather than websites. Compliance can be rather cumbersome. It is not compatible with any licenses that are used for source code.



    A later version of the GFDL added a relicensing clause that made it possible for Wikipedia (but no one else) to relicense to CC-BY-SA 3.0. Wikipedia exercised that clause, and has been using dual-licensing with GFDL/CC-BY-SA 3.0 for roughly a decade now.



    The CC-BY-SA 3.0 license has a much better compatibility story. In particular, you can choose to license adaptions a later license version, CC-BY-SA 4.0 allows you to use a compatible license, and Creative Commons has named the GPLv3 as a compatible license.



    That means the full list of licenses that you can use code snippets from Wikipedia under include:




    • GFDL (unversioned)


    • CC-BY-SA 3.0 (explicit dual-license, and compatible licenses per GFDL 1.3 section 11)

      • compatible licenses per section 4(b) (adaptations only!)

        • jurisdiction-ported versions of CC-BY-SA 3.0

        • compatible licenses at https://creativecommons.org/compatiblelicenses (none)

        • later CC-BY-SA versions


          • CC-BY-SA 4.0

            • compatible licenses per section 3(b)(1) (adaptations only!)

              • later CC-BY-SA versions (none)

              • compatible licenses at https://creativecommons.org/compatiblelicenses


                • Free Art License 1.3

                  • compatible licenses under section 5 (unclear)



                • GPLv3


                  • AGPLv3 per GPLv3 section 13








    So an open source project really only has the option to copy code snippets from Wikipedia if the project uses GPLv3 or AGPLv3 licenses. Note this excludes many popular licenses such as MIT, LGPL, GPLv2, GPLv2+, GPLv3+, and so on.






    share|improve this answer



























      3














      When merely copying small snippets of code, it may be worth considering whether the use could be covered by a copyright exception, such as fair use in the US. Because if some exception applies you won't have to consider the licensing. You would still have to properly attribute the snippet, of course. Note also that while pseudocode is copyrightable, the underlying algorithm cannot be copyrighted.



      If no exception applies, you would have to follow the license under which you acquired the snippet.



      Wikipedia is generally dual-licensed under the GFDL and CC-BY-SA 3.0, though individual pages may differ (that should be noted on the page, though).



      The GFDL can be understood as a historical artefact. Wikipedia originally used this license. However, the GFDL is highly incompatible with other licenses, and is geared towards books rather than websites. Compliance can be rather cumbersome. It is not compatible with any licenses that are used for source code.



      A later version of the GFDL added a relicensing clause that made it possible for Wikipedia (but no one else) to relicense to CC-BY-SA 3.0. Wikipedia exercised that clause, and has been using dual-licensing with GFDL/CC-BY-SA 3.0 for roughly a decade now.



      The CC-BY-SA 3.0 license has a much better compatibility story. In particular, you can choose to license adaptions a later license version, CC-BY-SA 4.0 allows you to use a compatible license, and Creative Commons has named the GPLv3 as a compatible license.



      That means the full list of licenses that you can use code snippets from Wikipedia under include:




      • GFDL (unversioned)


      • CC-BY-SA 3.0 (explicit dual-license, and compatible licenses per GFDL 1.3 section 11)

        • compatible licenses per section 4(b) (adaptations only!)

          • jurisdiction-ported versions of CC-BY-SA 3.0

          • compatible licenses at https://creativecommons.org/compatiblelicenses (none)

          • later CC-BY-SA versions


            • CC-BY-SA 4.0

              • compatible licenses per section 3(b)(1) (adaptations only!)

                • later CC-BY-SA versions (none)

                • compatible licenses at https://creativecommons.org/compatiblelicenses


                  • Free Art License 1.3

                    • compatible licenses under section 5 (unclear)



                  • GPLv3


                    • AGPLv3 per GPLv3 section 13








      So an open source project really only has the option to copy code snippets from Wikipedia if the project uses GPLv3 or AGPLv3 licenses. Note this excludes many popular licenses such as MIT, LGPL, GPLv2, GPLv2+, GPLv3+, and so on.






      share|improve this answer

























        3












        3








        3







        When merely copying small snippets of code, it may be worth considering whether the use could be covered by a copyright exception, such as fair use in the US. Because if some exception applies you won't have to consider the licensing. You would still have to properly attribute the snippet, of course. Note also that while pseudocode is copyrightable, the underlying algorithm cannot be copyrighted.



        If no exception applies, you would have to follow the license under which you acquired the snippet.



        Wikipedia is generally dual-licensed under the GFDL and CC-BY-SA 3.0, though individual pages may differ (that should be noted on the page, though).



        The GFDL can be understood as a historical artefact. Wikipedia originally used this license. However, the GFDL is highly incompatible with other licenses, and is geared towards books rather than websites. Compliance can be rather cumbersome. It is not compatible with any licenses that are used for source code.



        A later version of the GFDL added a relicensing clause that made it possible for Wikipedia (but no one else) to relicense to CC-BY-SA 3.0. Wikipedia exercised that clause, and has been using dual-licensing with GFDL/CC-BY-SA 3.0 for roughly a decade now.



        The CC-BY-SA 3.0 license has a much better compatibility story. In particular, you can choose to license adaptions a later license version, CC-BY-SA 4.0 allows you to use a compatible license, and Creative Commons has named the GPLv3 as a compatible license.



        That means the full list of licenses that you can use code snippets from Wikipedia under include:




        • GFDL (unversioned)


        • CC-BY-SA 3.0 (explicit dual-license, and compatible licenses per GFDL 1.3 section 11)

          • compatible licenses per section 4(b) (adaptations only!)

            • jurisdiction-ported versions of CC-BY-SA 3.0

            • compatible licenses at https://creativecommons.org/compatiblelicenses (none)

            • later CC-BY-SA versions


              • CC-BY-SA 4.0

                • compatible licenses per section 3(b)(1) (adaptations only!)

                  • later CC-BY-SA versions (none)

                  • compatible licenses at https://creativecommons.org/compatiblelicenses


                    • Free Art License 1.3

                      • compatible licenses under section 5 (unclear)



                    • GPLv3


                      • AGPLv3 per GPLv3 section 13








        So an open source project really only has the option to copy code snippets from Wikipedia if the project uses GPLv3 or AGPLv3 licenses. Note this excludes many popular licenses such as MIT, LGPL, GPLv2, GPLv2+, GPLv3+, and so on.






        share|improve this answer













        When merely copying small snippets of code, it may be worth considering whether the use could be covered by a copyright exception, such as fair use in the US. Because if some exception applies you won't have to consider the licensing. You would still have to properly attribute the snippet, of course. Note also that while pseudocode is copyrightable, the underlying algorithm cannot be copyrighted.



        If no exception applies, you would have to follow the license under which you acquired the snippet.



        Wikipedia is generally dual-licensed under the GFDL and CC-BY-SA 3.0, though individual pages may differ (that should be noted on the page, though).



        The GFDL can be understood as a historical artefact. Wikipedia originally used this license. However, the GFDL is highly incompatible with other licenses, and is geared towards books rather than websites. Compliance can be rather cumbersome. It is not compatible with any licenses that are used for source code.



        A later version of the GFDL added a relicensing clause that made it possible for Wikipedia (but no one else) to relicense to CC-BY-SA 3.0. Wikipedia exercised that clause, and has been using dual-licensing with GFDL/CC-BY-SA 3.0 for roughly a decade now.



        The CC-BY-SA 3.0 license has a much better compatibility story. In particular, you can choose to license adaptions a later license version, CC-BY-SA 4.0 allows you to use a compatible license, and Creative Commons has named the GPLv3 as a compatible license.



        That means the full list of licenses that you can use code snippets from Wikipedia under include:




        • GFDL (unversioned)


        • CC-BY-SA 3.0 (explicit dual-license, and compatible licenses per GFDL 1.3 section 11)

          • compatible licenses per section 4(b) (adaptations only!)

            • jurisdiction-ported versions of CC-BY-SA 3.0

            • compatible licenses at https://creativecommons.org/compatiblelicenses (none)

            • later CC-BY-SA versions


              • CC-BY-SA 4.0

                • compatible licenses per section 3(b)(1) (adaptations only!)

                  • later CC-BY-SA versions (none)

                  • compatible licenses at https://creativecommons.org/compatiblelicenses


                    • Free Art License 1.3

                      • compatible licenses under section 5 (unclear)



                    • GPLv3


                      • AGPLv3 per GPLv3 section 13








        So an open source project really only has the option to copy code snippets from Wikipedia if the project uses GPLv3 or AGPLv3 licenses. Note this excludes many popular licenses such as MIT, LGPL, GPLv2, GPLv2+, GPLv3+, and so on.







        share|improve this answer












        share|improve this answer



        share|improve this answer










        answered May 3 at 19:59









        amonamon

        13.9k11536




        13.9k11536





















            4














            IANAL/IANYL, but provided you're happy with making your content available under GPLv3, you should be fine.



            You're planning on implementing the Wikipedia-provided pseudocode in other languages, which means you're creating a derivative work (or, as CC refers to it, Adapted Material). Content in Wikipedia may be reused under CC-BY-SA 3.0 or later. The next such later version, CC-BY-SA 4.0, says that




            if You Share Adapted Material You produce, the following conditions also apply



            ...



            The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.




            and one such compatible licence is GPLv3. So by passing through CC-BY-SA 4.0 you can get permission to license your derivative under GPLv3, at which point it becomes absolutely standard free software.






            share|improve this answer























            • Great answer, I ended up accepting amons because it contains additional information.

              – Peter
              May 4 at 7:23











            • @Peter thank you for that! I entirely agree, and upvoted Amon's answer myself, for the same reason :)

              – MadHatter
              May 4 at 12:45















            4














            IANAL/IANYL, but provided you're happy with making your content available under GPLv3, you should be fine.



            You're planning on implementing the Wikipedia-provided pseudocode in other languages, which means you're creating a derivative work (or, as CC refers to it, Adapted Material). Content in Wikipedia may be reused under CC-BY-SA 3.0 or later. The next such later version, CC-BY-SA 4.0, says that




            if You Share Adapted Material You produce, the following conditions also apply



            ...



            The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.




            and one such compatible licence is GPLv3. So by passing through CC-BY-SA 4.0 you can get permission to license your derivative under GPLv3, at which point it becomes absolutely standard free software.






            share|improve this answer























            • Great answer, I ended up accepting amons because it contains additional information.

              – Peter
              May 4 at 7:23











            • @Peter thank you for that! I entirely agree, and upvoted Amon's answer myself, for the same reason :)

              – MadHatter
              May 4 at 12:45













            4












            4








            4







            IANAL/IANYL, but provided you're happy with making your content available under GPLv3, you should be fine.



            You're planning on implementing the Wikipedia-provided pseudocode in other languages, which means you're creating a derivative work (or, as CC refers to it, Adapted Material). Content in Wikipedia may be reused under CC-BY-SA 3.0 or later. The next such later version, CC-BY-SA 4.0, says that




            if You Share Adapted Material You produce, the following conditions also apply



            ...



            The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.




            and one such compatible licence is GPLv3. So by passing through CC-BY-SA 4.0 you can get permission to license your derivative under GPLv3, at which point it becomes absolutely standard free software.






            share|improve this answer













            IANAL/IANYL, but provided you're happy with making your content available under GPLv3, you should be fine.



            You're planning on implementing the Wikipedia-provided pseudocode in other languages, which means you're creating a derivative work (or, as CC refers to it, Adapted Material). Content in Wikipedia may be reused under CC-BY-SA 3.0 or later. The next such later version, CC-BY-SA 4.0, says that




            if You Share Adapted Material You produce, the following conditions also apply



            ...



            The Adapter’s License You apply must be a Creative Commons license with the same License Elements, this version or later, or a BY-SA Compatible License.




            and one such compatible licence is GPLv3. So by passing through CC-BY-SA 4.0 you can get permission to license your derivative under GPLv3, at which point it becomes absolutely standard free software.







            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered May 3 at 19:51









            MadHatterMadHatter

            10.5k12042




            10.5k12042












            • Great answer, I ended up accepting amons because it contains additional information.

              – Peter
              May 4 at 7:23











            • @Peter thank you for that! I entirely agree, and upvoted Amon's answer myself, for the same reason :)

              – MadHatter
              May 4 at 12:45

















            • Great answer, I ended up accepting amons because it contains additional information.

              – Peter
              May 4 at 7:23











            • @Peter thank you for that! I entirely agree, and upvoted Amon's answer myself, for the same reason :)

              – MadHatter
              May 4 at 12:45
















            Great answer, I ended up accepting amons because it contains additional information.

            – Peter
            May 4 at 7:23





            Great answer, I ended up accepting amons because it contains additional information.

            – Peter
            May 4 at 7:23













            @Peter thank you for that! I entirely agree, and upvoted Amon's answer myself, for the same reason :)

            – MadHatter
            May 4 at 12:45





            @Peter thank you for that! I entirely agree, and upvoted Amon's answer myself, for the same reason :)

            – MadHatter
            May 4 at 12:45

















            draft saved

            draft discarded
















































            Thanks for contributing an answer to Open Source Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid


            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.

            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function ()
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fopensource.stackexchange.com%2fquestions%2f8262%2fproper-use-of-wikipedia-code-sample-in-open-source-projects%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            How to write a 12-bar blues melodyI-IV-V blues progressionHow to play the bridges in a standard blues progressionHow does Gdim7 fit in C# minor?question on a certain chord progressionMusicology of Melody12 bar blues, spread rhythm: alternative to 6th chord to avoid finger stretchChord progressions/ Root key/ MelodiesHow to put chords (POP-EDM) under a given lead vocal melody (starting from a good knowledge in music theory)Are there “rules” for improvising with the minor pentatonic scale over 12-bar shuffle?Confusion about blues scale and chords

            What if the end-user didn't have the required library?What is setup.py?What is a clean, pythonic way to have multiple constructors in Python?What does Ruby have that Python doesn't, and vice versa?What is the reason for having '//' in Python?How do I create a namespace package in Python?How to package shared objects that python modules depend on?setuptools vs. distutils: why is distutils still a thing?Navigation in Windows 10 vs code not going to virtualenv library when the same library is installed at user levelPython create package for local usePackaging a project that uses multiple python versionsWhy is permission denied on pip install except for when “--user” is included at end of command?

            Why did Thanos need his ship to help him in the battle scene?Which actor plays Thanos in the Avengers mid-credits scene?Are there economic implications portrayed in comics where the buildings and cities are ruined almost daily?Old X-Men comic where team travels to alien world with a ring-like sun that needs recharging?Why does Ego need help sleeping?Is there an objective answer to who “the strongest Avenger” is?How did Banner get unstuck?Why did Thanos get hit?How did Thanos (or anyone) know the Infinity Stones would give him this power?Did Thanos leave Eitri alive for his after-sales service?In Avengers 1, why does Thanos need Loki?