Paws for trello github software#

And only some of our Trello boards need to track those cards. Only some GitHub issues need to become Trello cards that we can move around on our boards. But for non-engineers Trello is a more congenial way to organize, track, and discuss product and marketing plans, design sketches, and a range of other artifacts.

Paws for trello github software#

For core software development artifacts and for issues surrounding their development, deployment, and support, GitHub is the system of record. The missing ingredient here is API-level integration. That goofy solution is better than nothing, but it fails the One Search Box test. As a workaround I made a Slack slash command, /gsearch, that gives you back the gnarly Google Groups search URL (that nobody can remember) with your query appended to it. But there doesn't seem to be a search API for Google Groups, nor any way to wire such a feature into Slack's search box. OpenSearch showed us a decade ago that it can be easily done. Why not enable Slack to search Google Groups directly? Can you, for example, add Google Groups as a provider of results to Slack's search system? Your choice is too much noise or incomplete search. But you need to be selective about those alerts, and that makes for a lose/lose trade-off. It's true that dropping a document into a Slack channel or routing an email message there can alert the team to the existence of that item, as well as expose it to search. But these integrations duplicate data and feel intrusive. Others, like email to mailing lists (aka Google Groups), can be routed into Slack using glue providers like IFTTT and Zapier. Some, like Google Docs, can be ingested using Slack's native integrations. The question becomes: How do you expose those things to Slack's search? If the same query can also find Google documents and Trello cards and email messages, search becomes a superpower. If a query can find Slack messages, that's helpful. That matters in proportion to the completeness of the community memory. If you put something into Slack, somebody else can most likely find it. I imagine One GitHub to Rule Them All not because I cherish that outcome, but because I find knitting best-of-breed components together doesn't produce the results I want.Ĭonsider Slack: One of its key selling points is searchable community memory. Īlthough GitHub is a document manager, project manager, and discussion system, it makes less sense in those roles as you move away from code-centric workflows. The non-engineers are hostile to GitHub, but friendly to Trello and Slack. We've been adding more non-engineers than engineers to staff. In an earlier post, I explored how GitHub might provide much of the document management, project management, search, and discussion a company - not only a software company, but any company - would need. If you are a small software startup operating in 2015, as we are, you have quite possibly converged, as we have, on Google Apps and the trio of GitHub, Slack, and Trello.