Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Git implemented in Rust

github.com

Post reply on HN
Print view View original

11–20 of 122 posts

Re: Git implemented in Rust

#11

Post by adrianN »

littlestymaar wrote: post #4
hannob wrote: post #2

I don't see any info about a license. Strongly recommend using some standard FOSS license before plenty of people add commits and it gets a big mess clearing up the licensing situation later.

> Implementing git in rust for fun and education! Also, not having a license file isn't a messy situation, that means “this project is protected under Berne Convention copyright“: the author is the only one holding every rights on the code and every use that is not explicitly allowed is a copyright infringement (unless it's fair use).

Fair Use doesn't exist in many jurisdictions.

Re: Git implemented in Rust

#12

Post by EwanToo »

fxfan wrote: post #10
littlestymaar wrote: post #4

Earlier quoted context omitted.

> Implementing git in rust for fun and education! Also, not having a license file isn't a messy situation, that means “this project is protected under Berne Convention copyright“: the author is the only one holding every rights on the code and every use that is not explicitly allowed is a copyright infringement (unless it's fair use).

since you sound knowledgeable- if I go and without any contract "donate" some of my code to the repo- what becomes of the right to that code (the patch I contributed)?

You retain the copyright of the patch and can re-use it somewhere else under a different licence.

And in turn, the project you submitted it to cannot re-licence that patched section of code (e.g. become either GPL licenced) without your permission, as it does not belong to them.

(Edit for clarity)

Re: Git implemented in Rust

#13

Post by ernst_klim »

ioquatix wrote: post #8
ernst_klim wrote: post #6

Also a git implementation in pure OCaml, used for irmin git-based kv storage: https://github.com/mirage/ocaml-git https://github.com/mirage/irmin

Here is an implementation of a Ruby based kv store build on top of rugged, which is built on top of libgit2: https://github.com/ioquatix/relaxo-model It's so much fun, but not that practical for scalable websites.

>It's so much fun, but not that practical for scalable websites.

Git based kv has a bit different purpose than the regular kv storage. They are intended for communication between entities, running in parallel, sort of transactional memory. They are not intended for users' data storage.

Re: Git implemented in Rust

#14

Post by mnd999 »

littlestymaar wrote: post #4
hannob wrote: post #2

I don't see any info about a license. Strongly recommend using some standard FOSS license before plenty of people add commits and it gets a big mess clearing up the licensing situation later.

> Implementing git in rust for fun and education! Also, not having a license file isn't a messy situation, that means “this project is protected under Berne Convention copyright“: the author is the only one holding every rights on the code and every use that is not explicitly allowed is a copyright infringement (unless it's fair use).

Arguably by downloading it from github you’ve made an illegal copy.

Re: Git implemented in Rust

#15

Post by slavik81 »

littlestymaar wrote: post #9
CamouflagedKiwi wrote: post #5

Earlier quoted context omitted.

The author doesn't hold copyright on code other people submitted unless they explicitly give ownership via a CLA or similar. A licence would make it clearer, or at least a lot easier for other people to consume.

Exactly, but since it's a learning project it's not obvious it's supposed to receive and accept code contribution anyway (so far it didn't receive any, the only two commits are fixes to typos in the README). That being said, it would be nice from the author to put the code under a permissive license to allow other people to play with his code too (at the moment, even forking it is a copyright infringement…).

> at the moment, even forking it is a copyright infringement

Not that it changes much, but from the GitHub Terms of Service:

> By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories https://help.github.com/en/articles/github-terms-of-service#...

Re: Git implemented in Rust

#17

Post by louiz »

mnd999 wrote: post #14
littlestymaar wrote: post #4

Earlier quoted context omitted.

> Implementing git in rust for fun and education! Also, not having a license file isn't a messy situation, that means “this project is protected under Berne Convention copyright“: the author is the only one holding every rights on the code and every use that is not explicitly allowed is a copyright infringement (unless it's fair use).

Arguably by downloading it from github you’ve made an illegal copy.

No, you copied on your hard drive something that was offered to you for free on github.

Hosting that code yourself somewhere else would be illegal though.

Re: Git implemented in Rust

#19

Post by Zarel »

littlestymaar wrote: post #4
hannob wrote: post #2

I don't see any info about a license. Strongly recommend using some standard FOSS license before plenty of people add commits and it gets a big mess clearing up the licensing situation later.

> Implementing git in rust for fun and education! Also, not having a license file isn't a messy situation, that means “this project is protected under Berne Convention copyright“: the author is the only one holding every rights on the code and every use that is not explicitly allowed is a copyright infringement (unless it's fair use).

That sounds nice and all but it's wrong in two major ways.

First: GitHub has a Terms of Service which was somewhat-recently amended to make this license grant explicit:

https://help.github.com/en/articles/github-terms-of-service#...

"Any User-Generated Content you post publicly, including issues, comments, and contributions to other Users' repositories, may be viewed by others. By setting your repositories to be viewed publicly, you agree to allow others to view and 'fork' your repositories (this means that others may make their own copies of Content from your repositories in repositories they control)."

(Crucially, it doesn't require an open-source license, though.)

Second: even without that, there's such a thing as an implied license:

https://en.wikipedia.org/wiki/Implied_license

Like, if you write something down on a piece of paper, you can't then sue the owner of the paper for copyright infringement.

Similarly, if you upload code to GitHub, and tell it to share your code, you can't then sue them for sharing your code, ToS or no ToS.

Re: Git implemented in Rust

#20

Post by devit »

littlestymaar wrote: post #4
hannob wrote: post #2

I don't see any info about a license. Strongly recommend using some standard FOSS license before plenty of people add commits and it gets a big mess clearing up the licensing situation later.

> Implementing git in rust for fun and education! Also, not having a license file isn't a messy situation, that means “this project is protected under Berne Convention copyright“: the author is the only one holding every rights on the code and every use that is not explicitly allowed is a copyright infringement (unless it's fair use).

"Use" is allowed, redistribution of the original or derivative works is essentially what is not permitted.
Post reply on HN