Better naming convention

What questions are you trying to answer?

Re-naming few words like Projects, Groups, Merge requests

  • Change Project -> Repository (see the image below)

If we check the meaning of Repository (a central location in which data is stored and managed)

image

  • Change Repository -> Code (it is an actual place where we can read and write code)

  • Change Merge requests -> Pull requests (Optional)

Whats the Difference between a Pull Request and a Merge?

  • Change Groups -> Organization

We can consider that the Organization is the main company who do the coding stuff and it is possible that the organization can directly own the repository or it can be owned by a project.

  • Change Sub-groups -> Projects

For example, A company is working on a new product called "A" and we create a new project in GitLab with a name "A" and then created a repository inside the Project.

  • Issue Board -> Boards or Project Boards

Are you looking to verify an existing hypothesis or uncover new issues you should be exploring?

(Not sure what it is)

What is the backstory of this project and how does it impact the approach?

Naming is very important in our lives, it is a way to understand or recognize someone before we interact with a person and same goes for the naming of the features or the tools in the GitLab.

What do you already know about the areas you are exploring?

It will help the users to better understand the GitLab and to easily navigate around.

What does success look like at the end of the project?

It will easy for those people who are already familiar with the GitHub.

Edited by Yashu Mittal