nerdstein

Rector 0.8.x-dev@8896f0a
Config file: rector.yml



40 files with changes
=====================

....

nerdstein

# From: https://github.com/palantirnet/drupal-rector/blob/master/config/drupal-8/drupal-8.5-deprecations.yml
# Contains automatic fixes for some deprecations introduced in Drupal 8.5.
services:
    DrupalRector\Rector\Deprecation\DrupalSetMessageRector: ~

nerdstein

# From: https://github.com/palantirnet/drupal-rector/blob/master/rector.yml
imports:
  - { resource: "vendor/palantirnet/drupal-rector/config/drupal-8/drupal-8-all-deprecations.yml" }
  # includes:
  # - { resource: "vendor/palantirnet/drupal-rector/config/drupal-8/drupal-8.0-deprecations.yml" }
  # - { resource: "vendor/palantirnet/drupal-rector/config/drupal-8/drupal-8.4-deprecations.yml" }
  # - { resource: "vendor/palantirnet/drupal-rector/config/drupal-8/drupal-8.5-deprecations.yml" }
  # - { resource: "vendor/palantirnet/drupal-rector/config/drupal-8/drupal-8.6-deprecations.yml" }
  # - { resource: "vendor/palantirnet/drupal-rector/config/drupal-8/drupal-8.7-deprecations.yml" }

nerdstein

<?php 

// Source: https://github.com/palantirnet/drupal-rector/blob/master/src/Rector/Deprecation/DrupalSetMessageRector.php

namespace DrupalRector\Rector\Deprecation;

use DrupalRector\Utility\TraitsByClassHelperTrait;
use PhpParser\Node;
use Rector\NodeTypeResolver\Node\AttributeKey;
use Rector\Core\Rector\AbstractRector;

nerdstein

<?php

namespace Drupal\my_custom_module\Plugin\rest\resource;

use Drupal\Component\Serialization\Json;
use Drupal\Core\Session\AccountProxyInterface;
use Drupal\rest\Plugin\ResourceBase;
use Drupal\rest\ResourceResponse;
use Drupal\Component\Utility\Html;
use Psr\Log\LoggerInterface;

nerdstein

<?php

namespace Drupal\my_custom_module\Plugin\rest\resource;

use Drupal\Component\Serialization\Json;
use Drupal\Core\Session\AccountProxyInterface;
use Drupal\rest\Plugin\ResourceBase;
use Drupal\rest\ResourceResponse;
use Drupal\Component\Utility\Html;
use Psr\Log\LoggerInterface;

nerdstein

This will be a replacement for https://github.com/NuCivic/react-dash/blob/master/docs/development/workflows/publish.md

Dependencies

1. Set up an account on npm
2. Get added as maintainer on https://www.npmjs.com/package/react-dash and on the github repository
3. Identify the next release based on semantic versioning, in the form of x.y.z
4. Verify you have the appropriate git remotes, both an origin for your fork and an upstream for the React Dash repository

nerdstein

Key takeaways:

0. i have seen some etiquette guides that have example interactions

1. Giving people guidelines on how to give feedback, for example, in the issue queues needs to be right in peoples faces as they are giving that feedback. It helps them do a better job.

2. When you flag someone's post in various ways carefully scripted messages get put up that are designed to encourage positive behavior

3. we could do more to help onboard new members and provide them with resources to help navigate the community. other communities have clearer documentation for getting started: https://kubernetes.io/community/ and https://kubernetes.io/docs/tutorials/stateless-application/hello-minikube/; And I would respectfully suggest a section of d.o really isn't good enough. It needs to be the right messages in the right place throughout our infrastructure

nerdstein

Key takeaways (captured throughout meeting):

1. It strikes me that having all the information in a single place that is easily digestible would help a lot. I would be tempted to suggest taking with Gabor about his Rocketship thing and if it could be adapted to hold all the info and ongoing issues.
2. its a personal bugbear of mine that the way we disseminate info across the project is a bit unorganised. Very hard to find anything
3. I'd love to see drupal.org/community be reworked and owned by a working group
4. what people often seem to devalue is discoverability. lots of info is out there if you know where to find it. how do you find the things you dont know exist. like meetings. having them all in one place like that would rock.
5. I'm seriously open to having a community communication strategy created and implemented. Just wanted you all to know that. I've asked the team at a minimum to create a blog section on d.o/community so  there is one place for community news from groups like CWG.
6. My gut feel