From 1d935a0b2dd5eaa34e8a5210e8f489b016da5702 Mon Sep 17 00:00:00 2001
From: Michael Dawson <michael_dawson@ca.ibm.com>
Date: Thu, 14 Dec 2017 15:16:35 -0500
Subject: [PATCH] doc: instructions on how to make membership public

PR-URL: https://github.com/nodejs/node/pull/17688
Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
Reviewed-By: Jon Moss <me@jonathanmoss.me>
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Anna Henningsen <anna@addaleax.net>
Reviewed-By: Timothy Gu <timothygu99@gmail.com>
Reviewed-By: Colin Ihrig <cjihrig@gmail.com>
Reviewed-By: Gireesh Punathil <gpunathi@in.ibm.com>
Reviewed-By: Ruben Bridgewater <ruben@bridgewater.de>
---
 doc/onboarding.md | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/doc/onboarding.md b/doc/onboarding.md
index 5008a6bca08bab..af6407c4164455 100644
--- a/doc/onboarding.md
+++ b/doc/onboarding.md
@@ -38,6 +38,10 @@ onboarding session.
       * Branches in the nodejs/node repository are only for release lines
     * [See "Updating Node.js from Upstream"](./onboarding-extras.md#updating-nodejs-from-upstream)
     * Make a new branch for each PR you submit.
+    * Membership: Consider making your membership in the Node.js GitHub organization
+      public. This makes it easier to identify Collaborators. Instructions on how to
+      do that are available at
+      [Publicizing or hiding organization membership](https://help.github.com/articles/publicizing-or-hiding-organization-membership/).
 
   * Notifications:
     * Use [https://github.com/notifications](https://github.com/notifications) or set up email