Open Questions - Resources - People to talk to

Open Questions

• Which version of GitLab are we running specifically? Is it "Ultimate"? https://about.gitlab.com/pricing/ We are on Ultimate version 13, soon to be 14.

Resources

• Notes from meeting with DA: https://docs.google.com/document/d/1Gh6SdlA62u43jRzh5-M-uvMCvi50PoHZnUHjX9WWPbU/edit
• Inventory of collaborative features: https://docs.google.com/spreadsheets/d/18jS8pBWUyWIqi_9ZvXUVIsDC0zK72xwNWGNHqW8nhrI/edit#gid=0
• Drupal GitLab Meta issue: gitlab-org/gitlab#293749 (moved)
• Miro board w/ user journeys: https://miro.com/app/board/o9J_lElQnVg=/
• GitLab issues that affect Drupal Spoons: drupalspoons/webmasters#17
• How to get involved as a contributor to GitLab: https://about.gitlab.com/community/contribute/
  • They use gitter.im in place of Slack for external communication
  • There's also a community forum https://forum.gitlab.com/ — running Discourse https://www.discourse.org/
  • Contributors channel: https://gitter.im/gitlabhq/contributors
  • Neat! A merge request coach system!
  • Contribution acceptance criteria: https://docs.gitlab.com/ee/development/contributing/merge_request_workflow.html#contribution-acceptance-criteria
  • List of maintainers: https://about.gitlab.com/handbook/engineering/projects/
  • List of product managers and other key personnel per feature: https://about.gitlab.com/handbook/product/categories/
• GitLab architecture: https://docs.gitlab.com/ee/development/architecture.html
• Breaking changes in 14.0 (June 22, 2021): https://about.gitlab.com/blog/2021/06/04/gitlab-moving-to-14-breaking-changes/
  • Looks like they're similar to Drupal… they can announce deprecations as long as there are alternatives, and then break APIs during major versions. (Compare with https://about.gitlab.com/releases/2021/05/22/gitlab-13-12-released/#release-deprecations)
• GitLab hackathon: https://about.gitlab.com/community/hackathon/

Problems with Merge Requests

• "Etiquette" around turning a "patch" issue into a "MR" issue.
• Breaking "muscle memory" around doing work on localhost, generating a patch, creating an issue.
  • Explicitly remember that this is an option when creating an issue.
• Issue? Pull request? What to use when? Nothing that prompts you "do you want to make a MR while you're creating this issue?"
• Seems like more work than creating a patch. Easier to "drop and run" consistent contribution commands across projects/issues.

Chief Concerns

1. We're not going to get screwed (aka surprised by sudden changes to our workflow)
2. MRs got turned on; buggy but functional, but then visible progress stopped.
3. No transparency/visibility about what's happening beyond trawling the issue queue.
4. More insight into this effort. That it's happening.

Ability to edit MRs
Ability to edit issue summaries (these are on d.o, NOT on the MR)
- Half the comments on d.o, half on GitLab.

People to talk to

• Core contributors:
  • Tim Plunkett
  • Jess
• Security team:
  • Michael Hess
  • Jess
• "End User" Input
  • Matt Glaman
  • Alison (from Migrate channel)
  • Lauri/Ben/Wim
• GitLab
  • Moshe Weitzman