Drupal.org changes for the sprint from 12 Feb to 25 Feb 2018
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
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
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-02-12
DrupalCI: Automate the creation of a code-style fix patch during testing
DrupalCI provides code style testing as part of the test suite. To save developer resources for more complex problems, we want to update DrupalCI to automatically generate a patch for the issue with the automated code-style fixes.
Change record: https://www.drupal.org/node/2848491
Issue: https://www.drupal.org/node/1299710
Status: targeting week of 2018-02-19
DrupalCI: Replace css lint with stylelint
Stylelint is ultimately a better choice for DrupalCI because core patches can potentially update it and add plugins.
Change record: https://www.drupal.org/node/2940458
Issue: https://www.drupal.org/project/drupalci_testbot/issues/2866840
Status: A yarn build step has been added, unblocking this feature. Targeting week of 2018-02-19
Show all historical credits on user profiles
Right now, we only show the most recent year's worth of contributions on user profiles. This was because we did not have historical data when first creating the credit system.
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-02-19
Show all historical credits on organization profiles
For organizations, we currently only display their contributions from the past 90 days. This is a deliberate choice to encourage ongoing contribution, and matches the ranking factors used in the marketplace. However, there is value in being able to see an organization's complete contribution history, so we'll provide the option to see an organization's 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-02-19
Improve the gender field on Drupal.org
The gender field is an optional field on Drupal.org profiles, which is used for any member of the community who wants to positively and publicly affirm their gender/gender identity within the community. While some members of this community subscribe to the 'its no ones business' attitude, for others positively affirming this visibility is important, so we want to make the option available.
We will likely be updating the existing field to use something like drupal.org/project/gender instead of the current custom field, so that it can continue to be updated as that project updates. We have also suggested that the project include the Open Demographics 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: targeting week of 2018-02-19
Ongoing Changes
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.
Production servers being updated
Old webnodes have been phased out, and we are continuing to migrate services to their newer instances.
Most recent update: Git server migration is complete, the remaining servers are Solr, logging, and Media/NFS
Change Record: https://www.drupal.org/node/2827899
Status: Remaining: Solr, Media/NFS
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: TBD after the production server updates above are complete.
Previous Sprint Changes
Git server maintenance
Wednesday Jan 31st there was be an outage of Drupal.org git service, as we migrated git to new servers. The maintenance window for this work was from 2pm to 4pm Pacific.
http://www.thetimezoneconverter.com/?t=2:00pm&tz=Pacific%20Time%20(PT)&
For additional updates: https://twitter.com/drupal_infra/status/958094062783025152
Status: The migration to the new git server VMs was successful.
Updated the account registration welcome page with a better demographic field
Drupal.org now collects Big8/Big 10 registration information on the sign up field, in lieu of other more specific demographic information. That additional information (such as gender) will be updated and continue to be made available as an optional field on user profiles for those community members who want to positively affirm their identity within the community.
This particular change provides a broad based, intersectional understanding of community representation, and will remain private, being used only to provide aggregate understanding into our community. This follows the same change which was added to the speaker submission form.
Change Record: https://www.drupal.org/node/2944169
Issue: https://www.drupal.org/project/drupalorg/issues/2940759
Status: Deployed
Read more about these change notifications.
Sign up to receive change notifications via email.