Add forks information to the explore pages

Problem to solve

Add forks information to the explore pages.

Further details

All repositories get the stars numbers displayed on the explore page. Adding the numbers of forks alongside the stars would add useful information for the visitors. A highly starred and forked repo is strong, and combining these information better represent the health of a repo.

Currently, whoever wants to have the forks information without being logged in must follow the repo link and add /forks, e.g. https://gitlab.com/gitlab-org/gitlab-ce/forks. As this information is not private, let's make it more visible.

Proposal

This feature request include 2 potential developments:

1. Add the forks number alongside the stars number (the <i class="fa fa-code-fork" aria-hidden="true"></i> should be used):
   
2. As for the Most stars menu, a similar one entitled "Most forks" could be added:
   

What does success look like, and how can we measure that?

Something similar to the images attached above would be a good achievment.

Links / references

@akaemmerle This may be a candidate for movingtogitlab

added ~2278658 ~2975006 forking project labels

cc @jeremy_ as well for info, for the social aspect related to this.

Thank you for your proposal, @ponsfrilus!
Adding the fork counter to the project lists metadata makes sense to me and should be fairly straight-forward. I am currently planning a UX research on improving project lists and group lists from a holistic view via https://gitlab.com/gitlab-org/gitlab-ce/issues/48470. I will make sure this will be considered.

@jeremy_ Also like the idea of showing a "Most forks" tab. What do you think?

mentioned in issue #48470 (closed)

added Manage [DEPRECATED] devopsmanage and removed ~2278658 ~6575249 labels

added Create [DEPRECATED] label

@akaemmerle I think this issue has been fixed by the new design, at least for the part regarding showing the number of forks.

Probably a new issue discussing the creation of a "Most forks" page should be created?

added [deprecated] Accepting merge requests label

added groupoptimize label

removed [deprecated] Accepting merge requests label

mentioned in issue #66222 (closed)

mentioned in merge request gitlab-org/quality/triage-ops!268 (closed)

mentioned in issue #66564 (moved)

added 1 deleted label and removed devopsmanage groupoptimize labels

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue