[tomxor]

wow... reading the git trademark policy now, it's... surprising:

> While the original idea was to prevent people from forking the software, breaking compatibility, and still calling it Git, the policy covers several other cases.

> One is that you can't imply successorship. So you also can't fork the software, call it "Git++", and then tell everybody your implementation is the next big thing.

This seems like a massive violation of the spirit of GPL... explicitly disallowing official endorsement is one thing (since that would be lying), but you shouldn't be able to stop someone going and doing their own thing and calling it git-something.

[roblabla]

The GPL says nothing about branding though. The GPL is about user freedom, the ability to let the user improve (and share improved version of) the software.

In general, people tend to confuse copyright/patent with branding. The former is about using, while the later is about naming. You can totally make the next git-killer, and base it on git. What you cannot do is name it "GitSomething" (regardless of whether it uses git behind the scenes), as that would be a trademark violation.

I personally think the policy makes sense, but I also understand that there might be reasonable arguments either side. But framing it as an "anti-GPL" thing seems disingenuous to me.

[tomxor]

> The GPL says nothing about branding though

I said in spirit, not literally.

> In general, people tend to confuse copyright/patent with branding

I understand how trademark laws work, I'm talking about why this policy is wrong and against how OSS projects work in general. The original purpose (as stated by the policy itself) was supposedly to protect confusing forks of the same name or prevent pseudo successors, but it goes way beyond this to attack anything with git in the name.

> For example, imagine a software project which is only tangentially related to Git. It might use Git as a side effect, or might just be "Git-like" in the sense of being a distributed system with chained hashes. Let's say as an example that it does backups. We'd prefer it not call itself GitBackups. We don't endorse it, and it's just using the name to imply association that isn't there. You can come up with similar hypotheticals: GitMail that stores mailing list archives in Git, or GitWiki that uses Git as a backing store.

They reason this issue as "endorsement"... yet it's so common to have an ecosystem around a popular piece of software where project names are a derivative of the name of the core software it builds upon, I doubt anyone ever got confused or even cared much about endorsement, instead I think enforcement of this policy will just make the relationship and purpose of software built for use with git more opaque to users.

[clacke2]

There's a whole bunch of people out there, outside geek circles, who believe Linus created GitHub. Brand confusion is real.

[tomxor]

That may be so, there's probably also a whole bunch of people out there who think that Bill Gates invented the computer, it doesn't matter... it's a fools errand to try to eradicate ignorance of outsiders at the cost of disregarding any relationship that is not official and "endorsed" as invalid, i'd go as far as saying it's toxic.

Endorsement is not the only valid relationship between pieces of software, and it's definitely not the most important one. As an example of how bad this can be, git asked gitTorrent to change it's name to remove "git" - how absurd is that, git's protocols are modular, they are intended to be extended, this adds a torrent type protocol to git, it's for git... what the fuck else would you call it:

torrent-protocol-for-that-popular-merkel-tree-based-scm-that-is-not-mercurical-but-i'm-not-allowed-to-use-its-name

This "policy" completely disregards this as a valid relationship... why does it have to be endorsed, no one cares, they care about names that clearly communicate their purpose. gitTorrent and a thousand other extensions to git probably aren't going to be as popular as git itself, they aren't going to have enough presence that naming them something completely unique and obscure is going to be useful to users.

[edit]

I just want to say (and then I'll stop ranting), as much as this policy obviously irritates me... I love git, and so was pretty disappointed to find this, it doesn't make me love git any less, but It makes me more wary of people who "manage" open source projects.

[temprature]

I guess Richard Stallman violated the "spirit of the GPL" when he made MicroGnuEmacs change their name.

[anonymouz]

I don't think it violates the GPL, as the GPL doesn't really care about names. You still have every right to fork git, but have to call it a different name. So if you call your fork "treengler" or whatever, you'd be fine. As far as I can see, you could also still say on your website "Treengler is a fork of Git, that adds/modifies/improves... it in the following way, ...".

To me that seems to be compatible with the text as well as the spirit of the GPL. I think a similar discussion came up in the Debian project with the Firefox trademark at some point. Debian is quite picky about what it means for software to be free, and they seem to be fine with derivatives not being allowed to modify Firefox without changing the name. (At least, I think that was the end status of this discussion.)

[0x0]

That's why it's called "CentOS" and not "Free Red Hat Enterprise Linux"...

[clacke2]

Not against the spirit of GPL or free software at all. Governing the use of language and branding to promote software freedom is core to the movement.

The steward of git defining what does and does not have the git nature is completely in line with this. You want your own take on git? Go ahead, you explicitly have the four freedoms to do so, but don't muddy the waters by calling it git if you don't represent the project.

[tomxor]

> You want your own take on git? Go ahead, you explicitly have the four freedoms to do so, but don't muddy the waters by calling it git if you don't represent the project.

That was the original intent of the policy and not what I have issue with, but it goes much further than that, see my other comments for details.

Keeping this relevant: GitPub is not trying to replace git obviously.

[stephenr]

> This seems like a massive violation of the spirit of GPL...

What do you mean? The gpl literally exists to restrict the rights of downstream developers.

[clacke2]

The GPL exists to preserve the rights of downstream users. In doing so, it restricts the rights of downstream developers and distributors from restricting the rights of their users.

But we could go on and on back and forth about this. I just wanted to make sure the opposing view from yours is present in the thread near your claim.