feat: activity on repo has been stalled, this kickstarts it #1541

.github/workflows/nodejs-macos.yml

@@ -0,0 +1,26 @@
+name: Node.js (macOS) CI
+
+on:
+  push:
+    branches: [ "master" ]
+  schedule:
+    - cron:  '5 4 * * 0'
+
+jobs:
+  npm-test:
+
+    runs-on: macos-latest
+
+    strategy:
+      matrix:
+        node-version: [18.x]
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+    - run: npm ci
+    - run: npm test

.github/workflows/nodejs-ubuntu.yml

@@ -0,0 +1,28 @@
+name: Node.js (Ubuntu) CI
+
+on:
+  push:
+    branches: [ "master" ]
+  pull_request:
+    branches: [ "master" ]
+  schedule:
+    - cron:  '5 4 * * 0'
+
+jobs:
+  npm-test:
+
+    runs-on: ubuntu-latest
+
+    strategy:
+      matrix:
+        node-version: [14.x, 16.x, 18.x, latest]
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+    - run: npm ci
+    - run: npm test

.github/workflows/nodejs-windows.yml

@@ -0,0 +1,26 @@
+name: Node.js (Windows) CI
+
+on:
+  push:
+    branches: [ "master" ]
+  schedule:
+    - cron:  '5 4 * * 0'
+
+jobs:
+  npm-test:
+
+    runs-on: windows-latest
+
+    strategy:
+      matrix:
+        node-version: [18.x]
+
+    steps:
+    - uses: actions/checkout@v3
+    - name: Use Node.js ${{ matrix.node-version }}
+      uses: actions/setup-node@v3
+      with:
+        node-version: ${{ matrix.node-version }}
+        cache: 'npm'
+    - run: npm ci
+    - run: npm test

ROADMAP.md

@@ -1,37 +1,32 @@
 # Hubot Roadmap
 
-Hubot v3 aims to be a bot framework optimized for developers and developer workflows, with great integration with the most popular chat clients and developer tools, and an active community that is sharing scripts and best practices.
+Hubot aims to be a bot framework optimized for developers and developer workflows, with great integration with the most popular chat clients and developer tools, and an active community that is sharing scripts and best practices.
 
-This roadmap represents some of priorities for us over the next couple months. Issues or pull requests will be opened to discuss each of these items as they progress.
+This roadmap represents some priorities for us over the next couple months. Issues or pull requests will be opened to discuss each of these items as they progress.
 
 ## 1. Return to a “maintained” status
 
-- [x] Create a Hubot core team with at least 2 GitHub employees and at least 1 community member. The core team is [@technicalpickles](https://github.com/technicalpickles), [@bkeepers](https://github.com/bkeepers), [@mose](https://github.com/mose), and [@gr2m](https://github.com/gr2m) ([#1323](https://github.com/github/hubot/pull/1323))
+- [x] Create a Hubot core team with invested users with no direct connection, interested in continuing the #hubot project.
+- [x] Review all [open PRs](https://github.com/github/hubot/pulls) and triage [open issues](https://github.com/github/hubot/issues)
 - [ ] Document all maintainer processes (triage, release, etc.)
 - [ ] Create an issue template that addresses common requests
-- [ ] Configure automation ([probot stale](https://github.com/probot/stale), [Greenkeeper](https://greenkeeper.io/), [semantic-release](https://github.com/semantic-release/semantic-release))
-- [ ] Review all [open PRs](https://github.com/github/hubot/pulls) and triage [open issues](https://github.com/github/hubot/issues)
-- [ ] Establish a release process and regular release cadence of the first Tuesday of every month.
-- [ ] Establish a first-responder rotation, which will aim to reduce the average time to first response on all new Issues and PRs to 48 hours.
+- [ ] Establish a release process and regular release cadence.
 
 ## 2. Modernize the community
 
-- [ ] Consolidate all officially supported Hubot projects into a single GitHub organization. This will include github/hubot and a handful of supported scripts, but will not include all community scripts in https://github.com/hubot-scripts ([#1327](https://github.com/github/hubot/issues/1327))
-- [ ] Create a community forum to provide a place for people to ask questions, get help, and share best practices. [Discourse](https://www.discourse.org/) is the obvious choice here.
-- [x] Choose a chat platform for maintainers and contributors, and post notices in various existing places (#hubot on freenode, github/hubot on Gitter). Slack is the obvious choice here. [Join us on Slack](https://hubot-slackin.herokuapp.com/).
-- [x] Add a code of conduct based on http://contributor-covenant.org/ and processes to enforce it in all official spaces. ([#1334](https://github.com/github/hubot/pull/1334))
-- [ ] Publish weekly community updates (blog, newsletter, etc) which highlight recent and upcoming changes, give shoutouts to contributors / maintainers, and maybe mention interesting uses of Hubot
 - [x] Create Hubot Evolution—inspired by [Swift Evolution](https://github.com/apple/swift-evolution)—for proposing user-visible enhancements. ([hubotio/evolution#1](https://github.com/hubotio/evolution/pull/1))
+- [ ] Review and update the [contributing guide](CONTRIBUTING.md)
+- [ ] Review hubot scripts and discuss whether or not we should fork them into this org or not.
+- [ ] Do we want a chat community for Hubot?
+- [ ] Review the [code of conduct](CODE_OF_CONDUCT.md) based on http://contributor-covenant.org/
+- [ ] Decide on setting up Github Pages
 
 ## 3. Modernize the project
 
-Each of these proposals will go through the [Hubot Evolution](https://github.com/hubotio/evolution) process.
-
-- Translate from CoffeeScript to JavaScript and update to modern versions of Node.js and NPM (or Yarn)
+- Update to modern versions of Node.js
 - Revisit new bot generator (yeoman has a ton of dependencies, some of which can be error prone on windows)
 - Support for running multiple adapters and archetypes (chat, deployment, CI, github, etc)
-- Merge with [@probot](https://github.com/probot) and build out first class GitHub integration.
-- Introduce "Commands”, an explicit interface for registering commands (like Slack’s slash commands) as an alternative to regular expressions
-- Publish a ChatOps RPC spec and implement support for Hubot acting as both a client and a server.
+- Discuss introducing the `Commands` concept as an interface for registering commands (like Slack’s slash commands) as an alternative to regular expressions
+- Discuss publishing a ChatOps RPC spec and implement support for Hubot acting as both a client and a server.
 - Support rich messages and interactions on platforms that support it
 - Publish a public script directory backed by NPM

bin/hubot.js

@@ -23,7 +23,7 @@ const options = {
   adapter: process.env.HUBOT_ADAPTER || 'shell',
   alias: process.env.HUBOT_ALIAS || false,
   create: process.env.HUBOT_CREATE || false,
-  enableHttpd: process.env.HUBOT_HTTPD || true,
+  enableHttpd: process.env.HUBOT_HTTPD !== 'false',
   scripts: process.env.HUBOT_SCRIPTS || [],
   name: process.env.HUBOT_NAME || 'Hubot',
   path: process.env.HUBOT_PATH || '.',
@@ -80,10 +80,6 @@ Parser.on((opt, value) => {
 
 Parser.parse(process.argv)
 
-if (process.platform !== 'win32') {
-  process.on('SIGTERM', () => process.exit(0))
-}
-
 if (options.create) {
   console.error("'hubot --create' is deprecated. Use the yeoman generator instead:")
   console.error('    npm install -g yo generator-hubot')

docs/deploying/windows.md

@@ -8,16 +8,16 @@ Hasn't been fully tested - YMMV
 
 There are 4 primary steps to deploying and running hubot on a Windows machine:
 
-  * node and npm
-  * a way to get source code updated on the server
-  * setting up environment variables for hubot
-  * a way to start hubot, start it up if it crashes, and restart it when code updates
+* node and npm
+* a way to get source code updated on the server
+* setting up environment variables for hubot
+* a way to start hubot, start it up if it crashes, and restart it when code updates
 
 ## node and npm
 
 To start, your windows server will need node and npm.
 The best way to do this is with [chocolatey](http://chocolatey.org) using the [nodejs.install](http://chocolatey.org/packages/nodejs.install) package.
-I've found that sometimes the system path variable is not correctly set; ensure you can run node/npm from the command line. If needed set the PATH variable with "setx PATH \"%PATH%;C:\Program Files\nodejs\" "
+I've found that sometimes the system path variable is not correctly set; ensure you can run node/npm from the command line. If needed set the PATH variable with `set PATH=%PATH%;\"C:\Program Files\nodejs\"`
 
 Your other option is to install directly from [NodeJS](https://nodejs.org/) and run the current download (v0.12.4 as of this documentation). This should set your PATH variables for you.
 

docs/patterns.md

@@ -218,3 +218,17 @@ Organizations that have a number of chat rooms that serve different purposes oft
 
 Work on generalized blacklist solution is [ongoing](https://github.com/kristenmills/hubot-command-blacklist). A whitelist soultion could take a similar approach.
 
+## Use scoped npm packages as adapter
+
+It is possible to [install](https://docs.npmjs.com/cli/v7/commands/npm-install) package under a custom alias:
+
+```bash
+npm install <alias>@npm:<name>
+```
+
+So for example to use `@foo/hubot-adapter` package as the adapter, you can:
+```bash
+npm install hubot-foo@npm:@foo/hubot-adapter
+
+bin/hubot --adapter foo
+```

es2015.js

@@ -13,7 +13,7 @@ module.exports = {
   User,
   Brain,
   Robot,
-  Adapter: Adapter,
+  Adapter,
   Response,
   Listener: Listener.Listener,
   TextListener: Listener.TextListener,