https://www.gnu.org/philosophy/open-source-misses-the-point....
Arguing about "the point" misses the point. There's plenty of room for both free software and open source software.
Swift is Open Source
231–240 of 458 posts
Re: Swift is Open Source
#232So let's guess, will Microsoft create a Windows-supporting fork, just like Redis?
Re: Swift is Open Source
#233Github repo is live now. https://github.com/apple/swift First ever commit found here https://github.com/apple/swift/commit/afc81c1855bf711315b8e5...
It's cool to see that it was basically all Lattner at the beginning and his decisions about the license/exception still stand. EDIT: License/Header in each of files were apparently retroactively added.
Re: Swift is Open Source
#234A lot of folks to thank at Apple right now, can't wait until all of this propagates so we can take a look at what's new in Swift 3. Two thoughts: - VERY happy to see the open sourcing of much of the Foundation libraries (which includes strings, dates, networking primitives, concurrency/task queues, I/O, etc). It'll provide a very strong start and make working with Swift immediately productive. - Holy crap, there's a…
so we can take a look at what's new in Swift 3 Are new versions backwards compatible?
Re: Swift is Open Source
#235There is one more very interesting project under the swift umbrella: https://github.com/apple/swift-corelibs-libdispatch so now swift should have a useful approach to concurrency.
Looks like they need to port GCD/libdispatch so they can implement a native concurrency model on top of it in Swift 3(?).
Re: Swift is Open Source
#236Earlier quoted context omitted.
Not really. Your typical corporate IP lawyer might feel queasy about the collective copyright aspect, but so much of the open source world works this way now... they can suffer in their jocks. One important question they'll ask is: "Who can enforce the copyright and licence?" (Which is when the subtle difference between joint and collective copyright matters.) Non-trivial contributions are made under the terms of the…
"Who can enforce the copyright and licence?" The answer is only the owner of an exclusive right of copyright has standing to sue. So any of these open source projects that have no copyright assignments would have trouble suing. But in practice, who cares. Unless you want to sue people, it literally doesn't matter. The only folks who often care about suing are those who are trying to enforce certain types of share-ali…
Re: Swift is Open Source
#237https://github.com/apple/ This organization has no public repositories.
Re: Swift is Open Source
#238Earlier quoted context omitted.
A company that is traditionally hostile to open source gets as one of its first "contributions" to a newly opened project a troll, confirming a bad stereotype of the open source community. How could that not be considered inappropriate?
Apple is in now way hostile to OSS.
Re: Swift is Open Source
#239Can we get Adobe to open source the flash player plugin as well? Can anyone think of a reason Adobe continues to refuse?
Re: Swift is Open Source
#240Earlier quoted context omitted.
"Who can enforce the copyright and licence?" The answer is only the owner of an exclusive right of copyright has standing to sue. So any of these open source projects that have no copyright assignments would have trouble suing. But in practice, who cares. Unless you want to sue people, it literally doesn't matter. The only folks who often care about suing are those who are trying to enforce certain types of share-ali…
Joint holders can also enforce copyright, though open source codebases work more like collective copyright. That said, non-exclusive Linux kernel copyright holders have performed enforcement activities (quietly or noisily)...
Joint copyright is basically non-existent in the US. For example, you must intend to create a joint work at the time of creation. You can't make it joint later on by signing a document saying it's joint with someone. There are other issues too.
This is deliberate, as joint owners each own a 100% enforceable set of rights, and the law doesn't really want tons of people running around claiming to own the same work.
"That said, non-exclusive Linux kernel copyright holders have performed enforcement activities (quietly or noisily)..."
Not in the US. It's not possible in the US. It'll get dismissed immediately.