Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
1–10 of 136 posts
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#2Unfortunately this will probably run afoul of Git's trademark:
"In addition, you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service without Conservancy's written permission. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a portmanteau to refer to a product or service's use of Git code."
How enforceable that is... I'm not a lawyer.
https://git-scm.com/about/trademark (section 2.3)
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#3I like the approach that sourcehut took overall. I would like to find a way to implement issue tracking into Git, but the mailing list approach isn't a bad idea.
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#4Unfortunately this will probably run afoul of Git's trademark: "In addition, you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service without Conservancy's written permission. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a…
How do gitlab, github, gitea, etc get away with it then?
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#5I like the approach that sourcehut took overall. I would like to find a way to implement issue tracking into Git, but the mailing list approach isn't a bad idea.
> I would like to find a way to implement issue tracking into Git
Maybe git-bug would work for you? https://github.com/MichaelMure/git-bug
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#6Unfortunately this will probably run afoul of Git's trademark: "In addition, you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service without Conservancy's written permission. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a…
Could they keep the same domain and change the name to gitly.org?
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#7Unfortunately this will probably run afoul of Git's trademark: "In addition, you may not use any of the Marks as a syllable in a new word or as part of a portmanteau (e.g., "Gitalicious", "Gitpedia") used as a mark for a third-party product or service without Conservancy's written permission. For the avoidance of doubt, this provision applies even to third-party marks that use the Marks as a syllable or as part of a…
How do gitlab, github, gitea, etc get away with it then?
GitLab team member here.
Git is a trademark of Software Freedom Conservancy and our use of 'GitLab' is under license.
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#8Don't like that it tries to mimic Github UI.
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#9I like the approach that sourcehut took overall. I would like to find a way to implement issue tracking into Git, but the mailing list approach isn't a bad idea.
> I would like to find a way to implement issue tracking into Git Maybe git-bug would work for you? https://github.com/MichaelMure/git-bug
Thank you. I am interested, but am concerned by this statement:
> This is now more than a proof of concept, but still not fully stable. Expect dragons and unfinished business
Re: Gitly: A light and fast GitHub/GitLab alternative written in V lang (pre-alpha)
#10I like the approach that sourcehut took overall. I would like to find a way to implement issue tracking into Git, but the mailing list approach isn't a bad idea.
Isn't that what Fossil does? https://www.fossil-scm.org/