Logo54.144.21.195 
  News  Recent  Stats  Forums  Contact
  Menu
 Username

 Password


   Register here

 Main menu
   BBCode test
 
 Content
   About OpenAmiga
   Guidelines
   Definitions
   SVN Access
   Licenses
   IRC channel
   Links
   ToDo List
   List Content
 
 Projects
   Suggested (0)
   Open (11)
   Assigned (28)
   Pending (0)
   Finished (7)
   Closed (4)
 
 Categories
   Cli (2)
   Datatype (9)
   Drivers (3)
   System (16)
   Workbench (16)
  View comments
Title  
  Forums
    Open Amiga Forums
      Open Amiga
        Definitions  
          Discuss Open Amiga definitions
orginLicense discussion20080717 23:42
Post your ideas about licensing here.
Navigate: 1-3 
orginRe: License discussion20080718 00:33
We had a discussion on IRC tonight and Rigo had these comments:

    
Why use a license at all? The requirement could be that all code submitted to Open Amiga be fully transfered to it. And once code is transfered from OA to Hyperion the rights also are.

Open Amiga is under the risk of people using, unwillingly or illicitly, code that is GPL'ed or originally use some other license that could potentially end up putting Hyperion in a legally difficult situation.
orginRe: License discussion20080718 00:57
And my reply to Rigo.

If choosing the no license way then:

I'd much rather prefer that source submitted to oa is forked so that the original author retains control of his/her fork and oa gains full control of its fork. (only code fork, not project fork, the project is transfered to OA)

Hyperion is then permitted to use the OA code as it pleases but OA will still be able to continue to develop the OA code regardless of what Hyperion does with whatever it decides to copy.

In other words, the code isn't moved into a black hole called "Hyperion" to never be seen again.

Just as AO would still have the code if the original author drops interest or 'dies' it also would have it if Hyperion goes out of business. AO should also have the option to extend the list of companies/entities that would be able to use the OA code. Something that would not be possible if it was to be black holed by Hyperion.
TSKRe: License discussion20090118 19:22
@orgin

I'd much rather prefer that source submitted to oa is forked so that the original author retains control of his/her fork and oa gains full control of its fork. (only code fork, not project fork, the project is transfered to OA)

Just as AO would still have the code if the original author drops interest or 'dies' it also would have it if Hyperion goes out of business. AO should also have the option to extend the list of companies/entities that would be able to use the OA code. Something that would not be possible if it was to be black holed by Hyperion.

I like your ideas.
Navigate: 1-3 
Open Amiga project website, Created in 2008 by Björn Hagström