My reasoning behind the idea is the following:

  • Coherency within Drupal ecosystem: now Drupal community has shifted to using GitLab as SCM-hosting provider. From the viewpoint of User Guide reader’s experience, if I were a technical beginner, then I'd probably benefit more from accommodating with a GUI for the very first time of my own repository, that GUI is already being used for Drupal projects and will see many places around in the future.
  • Friendly partnership: when DA started to communicate (Developer Tools Initiative) the efforts they put into migrating from oldish cgit to something more modern interface, I felt comments from community members tending to support something less "corporatish", more "communitish" solution to be adopted. Later on, the official announcement confirmed my subjective impression:
    Screenshot

    "However, following our blog series, the GitLab team reached out directly to the Drupal Association team, and asked us to give them the chance to resolve the blockers and close the gaps in our integration.
    At the same time, we saw an outpouring of feedback from our community asking us to see if we could find a way to make GitLab work."

    AFAIK GitLab engineering team demonstrated a very supportive attitude during the preparation and the moving process as well. Based on their blog post I do feel that the Drupal community and GitLab now is in a friendly partnership.

  • Ideology viewpoint: GitLab stands closer to the concept of open-source as it’s entire software is freely available to the public. GitHub is definitely closed-source.

If the proposal is supported, then it seems a quite easy fix to recompose the wording of that few occurrences in the source text of User Guide.

CommentFileSizeAuthor
#10 interdiff.txt681 bytesjhodgdon
#10 3061981-v2.patch2.48 KBjhodgdon
#5 3061981.patch2.48 KBjhodgdon
gitlab-instead-github.png56.08 KBbaluertl

Comments

Balu Ertl created an issue. See original summary.

baluertl’s picture

baluertl
he/him
Primary language Hungarian
Location Budapest 🇪🇺
commented
Issue summary: View changes
gábor hojtsy’s picture

gábor hojtsy
he/him
Primary language Hungarian
Location Hungary
commented

if I were a technical beginner, then I'd probably benefit more from accommodating with a GUI for the very first time of my own repository, that GUI is already being used for Drupal projects and will see many places around in the future.

Agreed with this absolutely.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

Sounds like a good plan. Anyone want to make a patch? Here is the topic as it is now:
https://www.drupal.org/docs/user_guide/en/extend-git.html
and the file is source/en/extend-git.txt in the source repository for the User Guide.

Since we don't explain how to use GitHub, really all we need to do I think is add a sentence in the "Prerequisite knowledge" section with links to how to set up a repo in GitLab. And maybe in the first section where we do the "git remote add" command, put in a sample Gitlab URL?

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Assigned: baluertl » jhodgdon
Category: Plan » Task
Status: Active » Needs review
Issue tags: +Translation updates needed
StatusFileSize
new 3061981.patch2.48 KB

Here's a proposed patch. Any thoughts? There were only mentions of GitHub in two files: extend-git and install-tools, so I modified both of them. I verified that the clone URLs for GitLab are pretty much the same as for GitHub, by the way.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

As a note, I think it is still a good idea to mention GitHub, because it is still very commonly used. But I elevated GitLab to before GitHub when we mention both.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

As another note, if you go to gitlab.com you are redirected to about.gitlab.com, so that is the URL I put into the install-tools doc.

hansfn’s picture

hansfn commented
Status: Needs review » Needs work

Thx for the patch - really! Some comments after review.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented

OK, I can change the docs link. But I don't want to remove the link to the github help, because I think if people are using GitHub, they do need that article to avoid confusion about which URL to use, right? And we're still suggesting either GitHub or GitLab (which I think is appropriate, since a large segment of the open source community is on GitHub).

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Status: Needs work » Needs review
StatusFileSize
new 3061981-v2.patch2.48 KB
new interdiff.txt681 bytes

Anyway, here is a new patch to change the URL for GitLab help. I agree that the create project link is better.

eojthebrave’s picture

eojthebrave
he/him
Primary language English
Location Minneapolis, MN
commented
Status: Needs review » Reviewed & tested by the community

This looks good to me. I like that we're adding GitLab. And agree that it's a good idea to still mention GitHub as it's probably still more commonly used for personal/client projects.

jhodgdon’s picture

jhodgdon
she/her
Primary language English
commented
Status: Reviewed & tested by the community » Fixed

Committed, and sending out email update shortly. Thanks again all!

  • jhodgdon committed 5f43460 on 8.x-7.x 
    Issue #3061981 by jhodgdon, Balu Ertl, eojthebrave, Gábor Hojtsy, hansfn...

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.