Drupal.org changes for the sprint from 8 Oct to 21 Oct

183 views
Skip to first unread message

Drupal.org change notifications

unread,
Oct 10, 2018, 1:50:09 PM10/10/18
to 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 no longer being used by core, but is still used by some maintainers in 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.


This is the last time we will mention this deprecation - however, please bear in mind if that a future incompatibility is introduced we will *not* be introducing fixes to re-enable support.



Previous Sprint Changes


Updating events.drupal.org proposed sessions view

To support the new segmentation of session content for the builder track of DrupalCon seattle, we've added a topic tagging system to session submissions, and updated our proposed session view to allow filtering by tag.


Change record: https://www.drupal.org/node/3005717

Status: Deployed




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 continuing to evaluate the latest GitLab release (11.3) and testing our migration process, so that we can schedule a deployment window.


Beta testing a new format for the drupal.org/communtiy portal

We are in the process of beta testing a new ui for the front page of the http://drupal.org/community portal. The implementation of the 'accordian-style' content areas is still subject to change as we review for accessibility and usability and integrate this as a proper feature. If you have feedback, please view the /community section issues: https://www.drupal.org/project/issues/drupal_org_community


Change record: https://www.drupal.org/node/3005712

Issue: https://www.drupal.org/project/issues/drupal_org_community

Status: In testing and accessibility review, before moving into the D.O theme and building out the production version.


Updates to events.drupal.org schedule

Continuing with our efforts to support the new multiple-persona schedule for DrupalCon Seattle, we are updating the events.drupal.org schedule views to allow filtering by persona, and within persona by session tag.


Change record: https://www.drupal.org/node/3005719

Status: in development


Updates to events.drupal.org theme and styles

Thanks to the contribution efforts of the SixEleven team, we have some upcoming styling/theme changes for the events.drupal.org site, to support our upcoming event in Seattle. These include new social icons for instagram, linked-in, and youtube, updates to the display of speaker blockjs, etc.


Status: In review for deployment



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!



Read more about these change notifications.

Sign up to receive change notifications via email.

Reply all
Reply to author
Forward
0 new messages