diff --git a/www/appendices/channels.spt b/www/appendices/channels.spt index 45383df..e321eed 100644 --- a/www/appendices/channels.spt +++ b/www/appendices/channels.spt @@ -13,6 +13,11 @@ If you would rather communicate with us privately, please send email to [support@gratipay.com](mailto:support@gratipay.com). +## Slack + +Real-time chat happens [on Slack](/appendices/chat). + + ## GitHub We use [GitHub](https://github.com/gratipay) to manage our source code and @@ -22,12 +27,6 @@ discussion happens in the repo for the relevant project, mainly [gratipay.com](https://github.com/gratipay/gratipay.com/issues). -## Radar - -We coordinate using [weekly Radar tickets](/howto/sweep-the-radar). They're a -good place to start if you're new. Introduce yourself! :-) - - ## HackerOne We run our security program [on HackerOne](https://hackerone.com/gratipay). @@ -41,15 +40,16 @@ YouTube](https://www.youtube.com/user/gratipay/videos). Older ones are in [this playlist](http://www.youtube.com/playlist?list=PLivwfG4q6DTAYCmRDmGpljRrpR3yNNSFP). -## Slack -Real-time chat happens [on Slack](/appendices/chat). +# Moribund Channels +We don't really use these anymore. They're listed here as archives. -# Moribund Channels +## Radar -We don't really use these anymore. They're listed here as archives. +We coordinate using [~~weekly Radar tickets~~](/howto/sweep-the-radar). They're +a good place to start if you're new. Introduce yourself! :-) ## IRC diff --git a/www/howto/handle-security-issues.spt b/www/howto/handle-security-issues.spt index 766f98a..e090c71 100644 --- a/www/howto/handle-security-issues.spt +++ b/www/howto/handle-security-issues.spt @@ -10,7 +10,7 @@ internal Gratipay collaborators.* ## HackerOne We [use HackerOne](https://hackerone.com/gratipay) to manage our security -[queue](./manage-queues). Our program description lives [in this +queue. Our program description lives [in this repo](https://github.com/gratipay/inside.gratipay.com/blob/master/www/appendices/security-program.md). Make changes using GitHub PRs like normal, and then copy and paste into HackerOne once merged. @@ -75,8 +75,8 @@ GitHub. Once the fix is approved and the PR is merged to `master` in `security`, here's how to deploy it: - 1. Announce your intention on the [Radar](/howto/sweep-the-radar) so that no-one -else deploys from the regular repo while you're deploying from `security`. + 1. Announce your intention on [Slack](/appendices/chat) so that no-one else +deploys from the regular repo while you're deploying from `security`. 1. Clone the `security` repo, then configure a couple more remotes: ``` diff --git a/www/howto/manage-queues.spt b/www/howto/manage-queues.spt deleted file mode 100644 index 4363a0a..0000000 --- a/www/howto/manage-queues.spt +++ /dev/null @@ -1,34 +0,0 @@ -nav_title = 'Manage Queues' -[---] -[---] text/html - -We run Gratipay via queue management ([deep -dive](http://www.amazon.com/-/dp/1935401009)), and we visualize our queues via -a somewhat manual posting of tables to [the Radar](./sweep-the-radar) (copy, -paste, `*click*`, `*click*`, update, post). Here is [an example Queues -post](https://github.com/gratipay/inside.gratipay.com/issues/290#issuecomment-125372200) -on the Radar; scan the [current -Radar](https://github.com/gratipay/inside.gratipay.com/labels/Radar) for the -latest table. The queues in the table are ordered according to their -approximate priority: as a rule of thumb, we should work the higher queues down -to zero (or until all issues are blocked) before proceeding to the lower -queues. - -The queues tend to pile up towards the bottom, with the last one, "Issues," -being our single catch-all queue. The queues above "Milestones" should be -regularly driven to zero. "Milestones," "Review," and "PRs" should be -replenished before they ever reach zero, but on the other hand they should be -constantly flushed: don't let items rot in there, and don't let them collapse -(i.e., accumulate so many items that they are no longer manageable). "Errors" -is currently -[collapsed](https://github.com/gratipay/inside.gratipay.com/issues/293). - -In addition to the main "Queues" table, individual contributors may use a -short-hand inspired by [Inbox -Zero](http://www.43folders.com/2006/03/13/inbox-zero) to signal what queue -we're each paying to and what its status is. It's simple! Just say: `Queue 0` -on the Radar. That tells the rest of us what queue you're paying attention to -and how full it is. It's acceptable to refer to personal queues that aren't in -the table, such as Inbox (for your personal email inbox), GitHub (for your -personal GitHub notifications queue), and ... Lunch! `Lunch 1` means "I'm -going to lunch" and `Lunch 0` means "I'm back." :D diff --git a/www/howto/sweep-the-radar.spt b/www/howto/sweep-the-radar.spt deleted file mode 100644 index 040da3f..0000000 --- a/www/howto/sweep-the-radar.spt +++ /dev/null @@ -1,61 +0,0 @@ -nav_title = 'Sweep the Radar' -[---] -[---] text/html - -One of our most important [communication tools](/appendices/channels) is [the -Radar](https://github.com/gratipay/inside.gratipay.com/labels/Radar), a set of -weekly tickets on the `inside.gratipay.com` repo. Anyone actively working on Gratipay -should, if nothing else, pay attention to these tickets. The Radar is the beating -heart of Gratipay. - -The Radar sweep runs Sunday to Sunday. Our [bot](https://github.com/gratipay-bot) -rotates the tickets for us—any ticket with the `Radar` label in the -`inside.gratipay.com` repo. Moreover, the full ticket description and any -additional labels are copied over week to week (here's the -[source](https://github.com/gratipay/bot/blob/master/rotate-radar.py)). - -What this means is that creating a new subteam within Gratipay is as easy as -creating a ticket with the `Radar` label and a title and description appropriate -for the team. Use the ticket description to define the scope of the subteam. -Gratipay Bot will automatically carry this new subteam Radar forward week to -week with zero additional configuration. Aaaaaand that's kinda cool. :-) - -The rest of this document describes the format of the main `Radar NN` ticket. - - -## What and Why? - -Every Radar starts out with this question: "What are you working on this week -and why?" Give it some thought. Communicating the *why* as well as the *what* -helps the rest of us understand what motivates you, which helps us get to know -you better and help you achieve your dreams. - - -## Roadmap - -The first comment is usually a visual representation of our high-level roadmap, -for which we use [interactive blockdiag](http://interactive.blockdiag.com/). - - -## Queues - -At some point we'll usually post a table showing a snapshot of our queues. This -is our mid-level view of work to be done, covering maintenance of various types -as well as Roadmap progress. It's so important that it gets [its own -howto](./manage-queues). - - -## Email - -Usually there's a final comment just after the close of the Radar that contains -a screenshot of our email activity report for the preceding week, which we -receive on Monday morning. (Our email service provider is Mandrill.) - - -## General Interest - -The Radar is the place to post items of general interest to the Gratipay -team—whether humorous or informational—that don't have a specific -action item associated with them (which is actually pretty rare).