Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • World
  • Users
  • Groups
Skins
  • Light
  • Cerulean
  • Cosmo
  • Flatly
  • Journal
  • Litera
  • Lumen
  • Lux
  • Materia
  • Minty
  • Morph
  • Pulse
  • Sandstone
  • Simplex
  • Sketchy
  • Spacelab
  • United
  • Yeti
  • Zephyr
  • Dark
  • Cyborg
  • Darkly
  • Quartz
  • Slate
  • Solar
  • Superhero
  • Vapor

  • Default (No Skin)
  • No Skin
Collapse
Code Project
  1. Home
  2. Other Discussions
  3. IT & Infrastructure
  4. Proper way to release source of my program?

Proper way to release source of my program?

Scheduled Pinned Locked Moved IT & Infrastructure
questionannouncement
5 Posts 2 Posters 0 Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • I Offline
    I Offline
    IGx89
    wrote on last edited by
    #1

    I'm thinking about releasing the source code to a WMP9 plugin I've been working on, but since I've never publicly released the source of any of my programs, I'm not sure the proper way to do it. Do I need to use an existing license, like the GPL? Do I need to copyright my code? If so, how? Does it cost? Thanks!

    M 1 Reply Last reply
    0
    • I IGx89

      I'm thinking about releasing the source code to a WMP9 plugin I've been working on, but since I've never publicly released the source of any of my programs, I'm not sure the proper way to do it. Do I need to use an existing license, like the GPL? Do I need to copyright my code? If so, how? Does it cost? Thanks!

      M Offline
      M Offline
      markkuk
      wrote on last edited by
      #2

      If you don't want to hire a lawyer to write your license it's better to use an existing one. Pick one of the OSI approved licenses if you want to release your code as open source. You own the copyright to any code you have written automatically, even without any copyright notices or registrations.

      I 1 Reply Last reply
      0
      • M markkuk

        If you don't want to hire a lawyer to write your license it's better to use an existing one. Pick one of the OSI approved licenses if you want to release your code as open source. You own the copyright to any code you have written automatically, even without any copyright notices or registrations.

        I Offline
        I Offline
        IGx89
        wrote on last edited by
        #3

        Since my code is copyrighted automatically, does that mean I can put a copyright notice in my code if I want? Do I need a license, since my code is already copyrighted? If I still do, which one do you recommend? I'm certainly not going to read through all of them :). I'm just wanting to releas the code for private, instructional use, not for creating directly derived programs.

        M 1 Reply Last reply
        0
        • I IGx89

          Since my code is copyrighted automatically, does that mean I can put a copyright notice in my code if I want? Do I need a license, since my code is already copyrighted? If I still do, which one do you recommend? I'm certainly not going to read through all of them :). I'm just wanting to releas the code for private, instructional use, not for creating directly derived programs.

          M Offline
          M Offline
          markkuk
          wrote on last edited by
          #4

          Of course you can put your copyright notice to any code you have written, but it isn't necessary to do so. If you don't specify licensing conditions, nobody is allowed to do anything with your code! You must use a license that tells what you allow people to do with your code. If you are going to release your code on CodeProject you can't use a "look, don't touch" license. You must use a license that allows creating derived works (see the submission guidelines).

          I 1 Reply Last reply
          0
          • M markkuk

            Of course you can put your copyright notice to any code you have written, but it isn't necessary to do so. If you don't specify licensing conditions, nobody is allowed to do anything with your code! You must use a license that tells what you allow people to do with your code. If you are going to release your code on CodeProject you can't use a "look, don't touch" license. You must use a license that allows creating derived works (see the submission guidelines).

            I Offline
            I Offline
            IGx89
            wrote on last edited by
            #5

            I'm not planning on putting my code on CodeProject (unless specifically requested), so that doesn't matter too much. Which license would you recommend for my guidelines, and which license would you recommend for CodeProject guidelines?

            1 Reply Last reply
            0
            Reply
            • Reply as topic
            Log in to reply
            • Oldest to Newest
            • Newest to Oldest
            • Most Votes


            • Login

            • Don't have an account? Register

            • Login or register to search.
            • First post
              Last post
            0
            • Categories
            • Recent
            • Tags
            • Popular
            • World
            • Users
            • Groups