Skip to content

Include in permissions if reimplementation possible in other license #1247

Open
@tyoc213

Description

@tyoc213

I could be wrong, but you cant reimplement in other license code that needs to be Same license.

But not sure that means the same, I remember listening a lot of time a go that you cant read linux kernel and then reimplement it what you learned from there (ie in windows kernel for a person working there and taking linux as example of similar thing) like for example microsoft/WSL#178 (comment)

I think it is important to highlight this issue with certain things, also this kind of license for books and documentation will make your implementation a derivate of what you learned from the docs.

Also, stressing my memory... I remember listening that there was a guy that worked on x company with A language but at night went to home and reimplemented all in B and later on it was the competition of the other company (I could be wrong) but it seems this was possible, but not if the license was Same license and not sure how applies copyright, license, copyleft, intellectual property.

So I can't stress how much is important if on permissions can you learn/reimplement/take ideas/see how others have done something.

If same license implies by exclusion reimplementable it would be nice to include that in the description of "same license".

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions