Drupal.org changes for the sprint from 24 Sep to 7 Oct
Drupal.org change notifications
Software related change records:
https://www.drupal.org/list-changes/drupalorg
Infrastructure related change records:
https://www.drupal.org/list-changes/infrastructure
There may be some disruption in the change notification schedule as the Drupal Association backfills some of the responsibilities of the Director of Engineering, hestenet, who is stepping into the role as Interim Executive Director.
Thank you for your patience!
Announcements
Change to the Git remote format for Drupal.org
We have deprecated the Git remote format <username>@git.drupal.org/project/<yourproject>.git in favor of g...@git.drupal.org:project/<yourproject>.git in preparation for changes to our developer tooling stack. If you used the <username>@ format for your git remotes, you should change your remote to the git@ format. Please note: you cannot use password authentication with the new git@ format, you will need to upload SSH keys to your Drupal.org profile.
The version control tab at the top of any project will display the correct instructions that you can copy and use moving forward.
For more detailed instructions please review: https://drupal.org/gitauth
For more information about why we're making this change: https://www.drupal.org/drupalorg/blog/developer-tools-initiative-part-5-gitlab-partnership
Change to Sandbox Git remote URLs
HTTP clones for sandbox projects have changed from: https://git.drupal.org/sandbox/<author-username>/<project-node-id>.git
to:
https://git.drupal.org/sandbox/<author-username>-<project-node-id>.git
Git urls for sandboxes have changed from the format:
<username>@git.drupal.org:sandbox/<author-username>/<project-node-id>.git
the format should be changed to: g...@git.drupal.org:sandbox/<author-username>-<project-node-id>.git
The version control tab at the top of any project will display the correct instructions that you can copy and use moving forward.
For more detailed instructions please review: https://drupal.org/gitauth
For more information about why we're making this change: https://www.drupal.org/drupalorg/blog/developer-tools-initiative-part-5-gitlab-partnership
Deprecating PhantomJS
PhantomJS is currently being used in core and contrib for running automated Javascript tests on DrupalCI. The PhantomJS software is no longer supported, and we're going to be deprecating support for this testing method in DrupalCI soon. We strongly encourage all maintainers to migrate their Javascript tests to Nightwatch/Chrome web driver.
Previous Sprint Changes
Added a pronoun field to user accounts
Thanks to the contributed work of @justafish we've added a new field to user profiles for specifying pronouns. This work will be followed with additional work to expose user's location and primary language, to encourage better cross-cultural communication.
Change record: https://www.drupal.org/node/3002830
Issue: https://www.drupal.org/project/drupalorg/issues/2961229
Status: Deployed - with follow ups for the additional fields coming.
Upcoming Changes
Scheduling Phase 1 of the GitLab migration
We recently announced our partnership with GitLab to power the developer tools on Drupal.org. This will be a multi-phase process. In the first phase we'll be replacing the current Git backend as well as the code viewing tools with GitLab. The team is currently evaluating the latest release of GitLab and testing our migration process, before scheduling a migration window.
For more information about the upcoming changes, check out this video:
https://www.youtube.com/watch?v=q06taaJPGDw
Change record: https://www.drupal.org/node/3002828
Issue: https://www.drupal.org/project/infrastructure/issues/3002827
Status: We are evaluating the latest GitLab release (11.3) and testing our migration process,so that we can schedule a deployment window.
Ongoing Changes
Change the issue credit attribution to default to crediting commenters (maintainers must deselect commenters to remove credit attribution)
A number of maintainers and contributors from the core and contrib spaces have suggested that we change the Issue Credit Attribution process, so that commenters are credited by default, instead of having to be manually credited by the maintainer.
We want to continue to observe feedback on this change in the issue thread, but based on the current consensus and positivity around this idea, we are intending to make this change.
Change record: https://www.drupal.org/node/2974366
Issue: https://www.drupal.org/project/drupalorg/issues/2972225
Status: On hold while we continue to review community feedback on this issue
Importing existing donation and membership data to new membership system
If you've ever needed to look up a history of your donations to the DA for tax purposes, you'll be happy for this one. Now you will see the full history of donations, not including memberships, on your Drupal.org profile.
Change record: https://www.drupal.org/node/2956455
Issue: https://www.drupal.org/project/drupalorg/issues/2934492
Status: In progress
Implementing Open Demographics Initiative on Drupal.org
To improve the inclusiveness of our community, we want to provide better tools for understanding our community, and for allowing members of our community (at their choice) to positively affirm their identity and expression.
There are a number of important axes of identity and expression, however. We are evaluating making a module to include the Open Demographics Initiative, by @drnikki, with input from @sagesharp, @rachel_norfolk, @justafish, among others.
Change record: https://www.drupal.org/node/2944177
Issue: https://www.drupal.org/project/drupalorg/issues/2938949
Status: We have submitted a pull request to provide all of the questions and answers from ODI in a JSON format: https://github.com/drnikki/open-demographics/pull/48 further reviews are welcome!
We are also closing following the work on the Gender module, to use the standardized options said out by ODI.
Read more about these change notifications.
Sign up to receive change notifications via email.