You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 25, 2024. It is now read-only.
I was wondering should we consider to do the same with this one repo once the Drupal.org's migration to GitLab is successful? Maybe it would be even easier for us to work with the project when Drupal is using GitLab. Maybe between these two have a better way to syncs between the repos.
I am not sure if Drupal.org will use GitLab's Saas or own GitLab-server. So it would be great to wait once we have the answer to that.
Another question: If either Saas or their own-server, should we have this repo like our own repo such as we are doing today on GitHub or move within Drupal.org like a project? I was thinking if GitLab is very syncable and Drupal.org are using all/almost all the tools from GitLab then we can work better with the Drupal project, and it gives us credit (if it still offers when Drupal is using GitLab).
What is your thought about that/Hva tenker dere om det?
The text was updated successfully, but these errors were encountered:
Jeg er enig med dere, og tenkte derfor å ta opp denne tråden tidlig som mulig slik at vi vet hva som skjer og følger med på drupal.org når de er fullt migrert slik at vi kan være godt forbredt til drupalnorge's prosjekter :)
You might know that Drupal Association just announced a partnership with GitLab to modernize the developer tools on Drupal.org. So all their projects will move over to GitLab the next several months.
I was wondering should we consider to do the same with this one repo once the Drupal.org's migration to GitLab is successful? Maybe it would be even easier for us to work with the project when Drupal is using GitLab. Maybe between these two have a better way to syncs between the repos.
I am not sure if Drupal.org will use GitLab's Saas or own GitLab-server. So it would be great to wait once we have the answer to that.
Another question: If either Saas or their own-server, should we have this repo like our own repo such as we are doing today on GitHub or move within Drupal.org like a project? I was thinking if GitLab is very syncable and Drupal.org are using all/almost all the tools from GitLab then we can work better with the Drupal project, and it gives us credit (if it still offers when Drupal is using GitLab).
What is your thought about that/Hva tenker dere om det?
The text was updated successfully, but these errors were encountered: