Skip to content

License #1

Open
Open
License#1

Description

@flatrocks
flatrocks
opened on Aug 10, 2013

Please consider adding a license for this project so the community can explicitly know the terms regarding use, modification, redistribution, etc.
(For example, the c++ compiler referenced in the readme is licensed under GPLv3.)

Thanks

Activity

  1. Paulware commented on Aug 10, 2013

    @Paulware
    Paulware
    on Aug 10, 2013
    Owner

    Hello,
    What is the most open and least restrictive license. I don't know anything about this.
    Paul

    Date: Sat, 10 Aug 2013 09:07:13 -0700
    From: notifications@github.com
    To: ArduinoDebugger@noreply.github.com
    Subject: [ArduinoDebugger] License (#1)

    Please consider adding a license for this project so the community can explicitly know the terms regarding use, modification, redistribution, etc.

    (For example, the c++ compiler referenced in the readme is licensed under GPLv3.)

    Thanks

    —
    Reply to this email directly or view it on GitHub.

  2. flatrocks commented on Aug 11, 2013

    @flatrocks
    flatrocks
    on Aug 11, 2013
    Author
    Paul,
I'm afraid it's a little more complicated than I think we all would
like.  There are a bunch of different licenses, even in the Open
Source arena.  github's created a whole page/site to help simplify
the choice:
    http://choosealicense.com/
You don't have to choose a license but in my opinion, picking an
appropriate license will attract more project support from users and
developers.
  -t
On 8/10/13 4:34 PM, Paulware wrote:

  Hello,

  What is the most open and least restrictive license. I don't know
  anything about this.

  Paul

  Date: Sat, 10 Aug 2013 09:07:13 -0700

  From: notifications@github.com

  To: ArduinoDebugger@noreply.github.com

  Subject: [ArduinoDebugger] License (#1)

  Please consider adding a license for this project so the community
  can explicitly know the terms regarding use, modification,
  redistribution, etc.

  (For example, the c++ compiler referenced in the readme is
  licensed under GPLv3.)

  Thanks

  —

  Reply to this email directly or view it on GitHub.
  —
    Reply to this email directly or view
      it on GitHub.

  3. hasufell commented on Apr 23, 2014

    @hasufell
    hasufell
    on Apr 23, 2014

    No license in the tarballs and source repository means "all rights reserved" in fact. So we currently have no rights.

    What is the most open and least restrictive license. I don't know anything about this.

    You probably want MIT or BSD-3. Whatever you do, please choose a license that is at least compatible with GPL, see the green ones (BSD-4 is not compatible).

  4. Paulware commented on Oct 19, 2014

    @Paulware
    Paulware
    on Oct 19, 2014
    Owner

    BSD-3 sounds good. As long is you place this comment as the first line of every file:
    Paul Richards is awesome

  5. hasufell commented on Oct 19, 2014

    @hasufell
    hasufell
    on Oct 19, 2014

    BSD-3 sounds good. As long is you place this comment as the first line of every file:
    Paul Richards is awesome

    • that's a new clause, so it's a new license
    • you have to do it yourself in this repository

  6. runvnc commented on Jun 5, 2017

    @runvnc
    runvnc
    on Jun 5, 2017

    LOL. Just to clarify, it needs to say "Paul Richards is awesome" at the top of every file in this project, but not my own code files, right?

  7. Paulware commented on Jun 5, 2017

    @Paulware
    Paulware
    on Jun 5, 2017 via email
    Owner

  8. erm3nda commented on May 29, 2018

    @erm3nda
    erm3nda
    on May 29, 2018

    @Paulware If you wan't contribution credits plus "no endorsement" BSD-3 license is good.
    I think that is good to be cited in software if you contributed. A "stupid" mention in your code may open big doors to you in the future. ( I didnt say ur young, just that doors will not be open in the past :D )

    If you don't care, there's a "joke" license at http://www.wtfpl.net/txt/copying/. I think that IDC (I don't care) is a better name but meh :-) who cares.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions