Jeff Lindsay

automate. automate. automate. https://github.com/danger/danger https://github.com/bkeepers/PRobot

Some references for putting together a basic Code of Conduct. This would probably also become the general Glider Labs community CoC. https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/ http://contributor-covenant.org/version/1/4/ https://wealljs.org/code-of-conduct

Use this issue to collect notes until we've had some experience using Honeycomb for production debugging, and after a refactoring that will make it easier to capture certain events. *...

* Gruops provide namespace of shared commands for a set of users. Similar to GitHub orgs for repos * Groups are non-user command "owners" * Groups have members and admins...

* Ideally not builtin to Cmd, but a separate service * Using comlab we can incubate in Cmd and split out later * Not all users in slack would be...

* Optionally have commands come with their own Docker Engine instance. It would also be stateless, but allows you to perform Docker operations from your command, like builds and pushes,...

web ui

1

* What does it do * List and manage commands. (think early Heroku) * Sign-in w/ Auth0 * Link to change/cancel plan * Web console/terminal * Hterm, see termshare *...

* cmd can fetch release notes for current version from github * visibility into activity of project * `ssh cmd.io cmd-changelog` * Formatted version of release notes * Link to...

* Hooks are user definable implementations to internal extension interfaces * What form does user define hooks? * Webhooks * Commands as hooks * RPC/Duplex * ... * auth hook...

Expanding on command authoring #69, this would add: * `:edit` Which would open a terminal editor to edit the file. We could use Nano for now. Later use [micro](https://github.com/zyedidia/micro)