32
41
Fork
You've already forked website
53

Explain the differences with GitLab and Gitea #3

Closed
opened 2022年11月06日 14:59:36 +01:00 by Ghost · 11 comments

A table that compares GitLab Gitea and codename. Not on every aspects but trimmed on those that make a difference between Gitea and codename. For instance it won't compare GitLab features that are not in Gitea nor in codename.

A table that compares GitLab Gitea and codename. Not on every aspects but trimmed on those that make a difference between Gitea and codename. For instance it won't compare GitLab features that are not in Gitea nor in codename.

What I don't like about comparison charts I've seen so far is the purpose they were made for. They often only show features that the project can do as well as or better than other projects. Features that aren't included in the abilities of the project are left out so the visitors get the impression that the project is way better than others.

What I don't like about comparison charts I've seen so far is the purpose they were made for. They often only show features that the project can do as well as or better than other projects. Features that aren't included in the abilities of the project are left out so the visitors get the impression that the project is way better than others.

If a project makes its own comparison chart it will very likely be biased.

If a project makes its own comparison chart it will very likely be biased.

A timeline as posted in the content issue seems to be a better option to me. But that way the fork can't be compared to GitHub or GitLab.

A timeline as posted in the [content issue](https://codeberg.org/codename/website/issues/2#issuecomment-666992) seems to be a better option to me. But that way the fork can't be compared to GitHub or GitLab.

I agree it is difficult to make a comparison chart that is maintainable and relevant. The first thing it needs is easy fact checking. Which most of them do not and it becomes propaganda. The second thing is to be honest about being biaised: an introduction saying something along the lines: these are the things we believe makes codename better than GitLab or Gitea and here is why.

I agree it is difficult to make a comparison chart that is maintainable and relevant. The first thing it needs is **easy** fact checking. Which most of them do not and it becomes propaganda. The second thing is to be honest about being biaised: an introduction saying something along the lines: these are the things we believe makes **codename** better than GitLab or Gitea and here is why.

I think a comparison chart is important, because every newcome will ask "how does it differ from ...".

I think that such a chart should not only focus on "better features", but also on the vision, the community, the business goal (and maybe "non-features": features that are not in scope of this project – I don't have concrete example of this, yet)

I think a comparison chart is important, because every newcome will ask "how does it differ from ...". I think that such a chart should not only focus on "better features", but also on the vision, the community, the business goal (and maybe "non-features": features that are not in scope of this project – I don't have concrete example of this, yet)

There are already chart about this:

https://docs.gitea.io/en-us/comparison/

There are already chart about this: https://docs.gitea.io/en-us/comparison/

There are already chart about this:

https://docs.gitea.io/en-us/comparison/

IMHO this is an example of what I would not want because it is difficult to fact check and is partly false. Or was last time I checked.

> There are already chart about this: > > https://docs.gitea.io/en-us/comparison/ > IMHO this is an example of what I would not want because it is difficult to fact check and is partly false. Or was last time I checked.

Maybe calling it a comparision is the wrong terminology than:

an examination of two or more items to establish similarities and dissimilarities

As comparisions are easier for features(which for now is not something to see any differences), but we might want to establish codename's position vs Gitea/GitLab's position.

I think we instead want to outline the characteristic of the forges. E.g. Gitlab/Gitea has an for-profit with hidden intentions company, codename has Codeberg E.v. with very clear ideals.

Maybe calling it a comparision is the wrong terminology than: > an examination of two or more items to establish similarities and dissimilarities As comparisions are easier for features(which for now is not something to see any differences), but we might want to establish codename's position vs Gitea/GitLab's position. I think we instead want to outline the characteristic of the forges. E.g. Gitlab/Gitea has an for-profit *with hidden intentions* company, codename has Codeberg E.v. with very clear ideals.
Ghost changed title from (削除) Comparison with GitLab and Gitea (削除ここまで) to Explain the differences with GitLab and Gitea 2022年11月07日 18:59:38 +01:00

Do this title better reflect what you suggest?

Do this title better reflect what you suggest?

Yes, that's more in line.

Yes, that's more in line.

Three weeks later this comparision does not sound like it is going to help significantly, closing. If someone is willing to work on it, please feel free to re-open!

Three weeks later this comparision does not sound like it is going to help significantly, closing. If someone is willing to work on it, please feel free to re-open!
Sign in to join this conversation.
No Branch/Tag specified
main
monthly-2026-05
mahlzahn-eslint-js
preview-link-status
nightfire
2022年12月14日-main
No results found.
Labels
Clear labels
404
Broken links or missing content
Accessibility
Accessibility
Blog post
Documentation
Forgejo Documentation
Internationalisation
i18n and l10n
User research - Accessibility
Requires input about accessibility features, likely involves user testing.
User research - Blocked
Do not pick as-is! We are happy if you can help, but please coordinate with ongoing redesign in this area.
User research - Community
Community features, such as discovering other people's work or otherwise feeling welcome on a Forgejo instance.
User research - Config (instance)
Instance-wide configuration, authentication and other admin-only needs.
User research - Errors
How to deal with errors in the application and write helpful error messages.
User research - Filters
How filter and search is being worked with.
User research - Future backlog
The issue might be inspiring for future design work.
User research - Git workflow
AGit, fork-based and new Git workflow, PR creation etc
User research - Labels
Active research about Labels
User research - Moderation
Moderation Featuers for Admins are undergoing active User Research
User research - Needs input
Use this label to let the User Research team know their input is requested.
User research - Notifications/Dashboard
Research on how users should know what to do next.
User research - Rendering
Text rendering, markup languages etc
User research - Repo creation
Active research about the New Repo dialog.
User research - Repo units
The repo sections, disabling them and the "Add more" button.
User research - Security
User research - Settings (in-app)
How to structure in-app settings in the future?
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
3 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
forgejo/website#3
Reference in a new issue
forgejo/website
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?