Drupal.org changes for the sprint from 15 to 28 Jan 2018

12 views

Skip to first unread message

Drupal.org change notifications

unread,

Jan 17, 2018, 12:13:48 PM1/17/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

Announcements

Drupal is now 17 years old!

Read the announcement by project founder Dries Buytaert, and watch the video to see the amazing ways Drupal has impacted the world.

Assoc.Drupal.org Membership API Deprecated

Assoc.Drupal.org’s API for membership is now deprecated. The replacement is querying Drupal.org directly. See https://www.drupal.org/drupalorg/docs/api for the new API documentation.

The old API endpoints at https://association.drupal.org/api/membership/… will become increasingly incomplete as we migrate memberships this year. We plan to remove the API later this year.

Upcoming Changes

Changes to the Drupal.org Hosting Listings

We are refreshing the Drupal.org hosting listings section of the marketplace, and providing a new navigation that will show all listing providers, in addition to filtering providers by type.

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

Status: targeting 2018-01-21

Distinguishing 'countries you have a physical presence in' from 'countries in which you do business' for organization profiles

On several occasions there has been confusion from both service providers and for end-users as to whether a particular service provider has a physical presence in a country, vs simply doing business in that country while not being located there. To resolve this issue we're going to break these into two separate fields on organization profiles, and adjust the marketplace filtering options accordingly.

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

Status: targeting week of 2018-01-21

Show all historical credits on user profiles

Right now, we only show the most recent year's worth of contributions on user profiles. In part this was because we did not have historical data when first creating the credit system, but it was also to encourage ongoing contribution.

However, we want to make it possible to see the full history of a user's contributions, so we will begin displaying all user credits from the time that the credit system was implemented (April 2015).

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

Issue(s): https://www.drupal.org/node/2042697

Status: targeting week of 2018-01-21

Show all historical credits on organization profiles

For organizations, we currently only display their contributions from the past 90 days. Again, this is a deliberate choice to encourage ongoing contribution, and because it matches the ranking factors used in the marketplace. However, there is value in being able to see an organizations complete contribution history, so we'll provide the option to see an organizations credits going back to the beginning of recorded credit (April 2015).

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

Issue(s): https://www.drupal.org/project/drupalorg/issues/2649100, https://www.drupal.org/node/2042697

Status: targeting week of 2018-01-21

Ongoing Changes

Helping to troubleshoot random test failures due to APCU cache issues
We are working with core to help troubleshoot random testbot failures in DrupalCI due to APCU caching issues.

Issue: https://www.drupal.org/project/drupal/issues/2930022, https://www.drupal.org/project/drupal/issues/2926309,

Status: reviewing suggested hotfix in this issue: https://www.drupal.org/project/drupal/issues/2926309#comment-12398863

Akismet on Drupal.org
Mollom is fast approaching its end of life, and so we've been putting in place new measures, such as ReCaptcha, to help strengthen our anti-spam protections. For content analysis protection we'll be implementing Akismet on Drupal.org

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

Issue: https://www.drupal.org/project/drupalorg/issues/2925121

Status: Deployed to Drupal.org, we are watching it's spam/ham classifications in silent mode alongside Mollom to evaluate its success.

More flexible top-level navigation on Drupal.org
We are experimenting with ways to improve the top level navigation on Drupal.org - making it easier for users of different personas to find the areas of the site that are best targeted to them. This might involve adding drop down menus to the main navigation.

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

Issue: https://www.drupal.org/node/2481515 , https://www.drupal.org/project/content/issues/2223199

Status: Experimenting on a dev site. This change will not necessarily be deployed if we don't find a good navigation schema.

DrupalCI: Repurposing owned hardware to run testbots

We are repurposing some of our owned hardware as vmhosts to run dedicated testbots. These bots are not as high performance as our AWS spot instances, and therefore will be used for the daily and weekly tests, rather than for commit or patch tests which developers may be waiting for.

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

Status: ongoing

Production servers being updated

Old webnodes have been phased out, and we are continuing to migrate services to their newer instances.

Most recent update: our git staging environment is nearly ready.

Change Record: https://www.drupal.org/node/2827899

Status: Remaining: Solr, Media/NFS, Git, GitDev

Previous Sprint Changes

Promoting industry pages when filtering the marketplace
Drupal.org has been experimenting with providing targeted content for evaluators highlighting success stories built with Drupal in different industries. We think it would be valuable to highlight these same success stories on the Marketplace, when visitors filter by these same industries. We'll experiment with adding a block that appears to promote the appropriate industry page when the relevant filters are used.

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

Issue: https://www.drupal.org/project/drupalorg/issues/2928460

Status: targeted for the week of 2018-01-02

Provide in-context explanation for issue tags
Issue tags are used for a wide variety of purposes, but some have a specific meeting that helps project maintainers or core committers keep track of key issues. To make it easier to understand what issue tags mean, we'll be providing some in-context explanation.

You can help to maintain the issue tags here: https://www.drupal.org/drupalorg/docs/maintenance/maintaining-issue-tags

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