Announcement

Collapse
No announcement yet.

Fedora 20 Moves Ahead With Wayland Tech Preview

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • #81
    Originally posted by RahulSundaram View Post
    Forks can choose a different license since MIT license allows sub-licensing. Nothing stops a fork from choosing GPL + CLA or even a proprietary license.
    Nothing but the MIT license itself:
    Copyright (C) <year> <copyright holders>

    Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

    The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

    THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

    Comment


    • #82
      Originally posted by Vim_User View Post
      Nothing but the MIT license itself:
      That is just not true. The license provides you the right to sublicense explicitly. Sublicensing allows you to choose any license you want since MIT is an extremely permissive license. You cannot change the copyright notice for the code that was originally in the project but nothing restricts you to retain the MIT license on forks. Several very popular proprietary projects including MIT licensed code.

      Comment


      • #83
        Originally posted by RahulSundaram View Post
        Forks can choose a different license since MIT license allows sub-licensing. Nothing stops a fork from choosing GPL + CLA or even a proprietary license.
        Then I misunderstood you before, and my assumption about it was right.

        Comment


        • #84
          The license explicitly says that sublicensing is allowed under the following terms:
          The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
          Or do you want to tell me that a fork is not a copy? Of course proprietary projects can incorporate MIT licensed code, but that doesn't change the license at all.

          Comment


          • #85
            Originally posted by Vim_User View Post
            The license explicitly says that sublicensing is allowed under the following terms:Or do you want to tell me that a fork is not a copy? Of course proprietary projects can incorporate MIT licensed code, but that doesn't change the license at all.
            One cannot change the license of the ORIGINAL code but a fork of say Wayland can be under ANY license. The ORIGINAL parts of the fork will have to retain the copyright notice as required by the license. That is it. This is the primary difference between a permissive and copyleft license. GPL, LGPL etc require forks to retain the same license. MIT, revised 2 clause BSD etc don't require that.

            Comment


            • #86
              Originally posted by finalzone View Post
              Hold on a second. Apple made launchd which is the inspiration for systemd breaking the so-called UNIX way (init, rc, init.rc scripts, cron, xinetd) and was ported to FreeBSD.
              Upstart was made due to the licensing issue related to Apple launchd at that time (resolved too late) while retained the so-called UNIX way. It was the logical choice because it was better than the buggy SysV until the emergence of systemd.
              launchd may have been ported to FreeBSD, but it never recieved substantial use. Why? Because it's not the UNIX way and it would likely break something.
              If anything, they should be shifting towards OpenRC which is both cross platform and liberally licensed.

              Comment


              • #87
                Originally posted by mrugiero View Post
                You mean Azure or Azura, something like that? If you mean that, IIRC it's a replacement for Gecko.
                Azure is the old name for Mozilla's new 2d drawing library. They created it b/c they wanted a drawing pipeline that mapped more cleanly to direct2d (or directdraw, or whatever it's called), and they said that cairo had too many context-switches due to it being immediate-mode (which should map well to something like canvas but apparently doesn't). On Linux it basically ends up using cairo.
                Gecko-next (maybe) is called Servo written using Rust, IIRC.

                Comment


                • #88
                  Originally posted by intellivision View Post
                  launchd may have been ported to FreeBSD, but it never recieved substantial use. Why? Because it's not the UNIX way and it would likely break something.
                  If anything, they should be shifting towards OpenRC which is both cross platform and liberally licensed.
                  ZFS certainly isn't "the UNIX-way" but it seems to have found significent usage in BSD-land.

                  Comment


                  • #89
                    Originally posted by liam View Post
                    ZFS certainly isn't "the UNIX-way" but it seems to have found significent usage in BSD-land.
                    The file system is usually not included in 'the UNIX way', the init system is very central to that idea however.
                    Do you like comparing apples to oranges for a living?

                    Comment


                    • #90
                      Originally posted by intellivision View Post
                      launchd may have been ported to FreeBSD, but it never recieved substantial use. Why? Because it's not the UNIX way and it would likely break something.
                      If anything, they should be shifting towards OpenRC which is both cross platform and liberally licensed.
                      What is exactly the UNIX way?

                      Comment

                      Working...
                      X