Does this present any data collection / privacy / ownership issues?
On Wed, Feb 28, 2018 at 9:29 PM, Jorge Castro <jo...@heptio.com> wrote: > Hey everyone, just a quick update on this. CCing kubernetes-users as well. > > The pensive folks have agreed to a pilot for the next few weeks for us to > kick the tires. I've enabled it on #kubernetes-users and > #kubernetes-novice. Here's how it works: > > a) The bot collects questions from the channels, then once a day it puts > them in a queue. > b) A human (currently me) then goes through the queue and picks out the > good questions with answers which then pensive collects. > c) Once 100 questions have been seeded to kick off the machine learning > the bot turns on in the channels. > d) If a user asks a question that the bot thinks it has an answer to it > will PM them with what it thinks the answer is, the user then marks whether > this is useful, etc. > e) Users can also directly query the bot. > > Here's a quick demo if you missed it: https://www.youtube.com/watch? > v=34eS_L_cfYU > > Most of the interaction is directly to the asking user or if you query it, > so don't expect spamminess. One of the first things I'd like to identify is > a group of people who are willing to curate incoming questions, ideally > those of you that sit in -users and -novice and are good at recognizing > common patterns, that way we could crowdsource the curation across > timezones. If you're interested in this sort of thing ping me offlist. > > To answer some questions, Mike, it hasn't yet collected a set of questions > so I'm not exactly sure how this will work, but it appears as though the > people answering the queue can edit and polish the content, so maybe it's > relying on the human to catch a mistake if it mixes up conversations. > > I also asked about StackOverflow integration, which is currently not a > feature but something I am giving their team feedback on. For example it > would be awesome if we could ingest everything in the kubernetes tag so > that if a question is already answered on SO and a new user asks in the > channel the bot just PMs them the direct link. > > > On Fri, Jan 26, 2018 at 6:13 PM Mike Johnson <mike.john...@help.com> > wrote: > >> This could be very useful. Question, for a question to be marked as >> answered would this require @'ing the user or that the responses be a >> thread? Or can it somehow grok answers that aren't directly threaded to the >> question? >> >> >> On Friday, January 26, 2018 at 12:40:46 PM UTC-6, Jorge Castro wrote: >> >>> Hi everyone, >>> >>> We do have a ton of things in -novice and -users that eventually get >>> lost in the ether, should we investigate something like this? >>> >> >>> ---------- Forwarded message --------- >>> >>> From: Renuka Apte <ren...@pensieve.ai> >>> >> Subject: question answering for kubernetes community >>> Date: Jan 25 2018, at 4:08 pm >>> >> To: jo...@heptio.com >>> >> >>> >>> >>> Hi Jorge, >>> >>> I’m reaching out to you because my cofounder and I have been exploring >>> ways to help with question answering and support at organizations like >>> yours, and thought you might find it useful for the Kubernetes community. >>> >>> I noticed that Kubernetes has very active slack channels for helping >>> developers. We’ve built a bot that listens on a channel, automatically >>> detects questions and can answer them if they were previously answered, and >>> can detect when a new question is answered and help capture it into a Q&A >>> knowledge base. >>> >>> Here’s a demo of what we’ve built so far — https://youtu.be/34eS_L_cfYU >>> >>> I’d love to get your feedback on whether it might be useful to help you >>> better engage & support your developer community. >>> >>> We ran our code against a sample of your kubernetes-users channel and >>> here’s a screenshot of what it looks like (since this was a scrape, as we >>> don’t actually have bot permissions on your channel, I can’t show what the >>> whole interaction might look like): >>> >>> >>> Let me know what you think. >>> >>> Best, >>> Renuka. >>> www.pensieve.ai >>> https://www.linkedin.com/in/renuka-apte/ >>> >> -- >> You received this message because you are subscribed to the Google Groups >> "Kubernetes developer/contributor discussion" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to kubernetes-dev+unsubscr...@googlegroups.com. >> To post to this group, send email to kubernetes-...@googlegroups.com. >> To view this discussion on the web visit https://groups.google.com/d/ >> msgid/kubernetes-dev/0feec01f-b671-41e2-a820-a54b3eb91c3d% >> 40googlegroups.com >> <https://groups.google.com/d/msgid/kubernetes-dev/0feec01f-b671-41e2-a820-a54b3eb91c3d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> For more options, visit https://groups.google.com/d/optout. >> > -- > You received this message because you are subscribed to the Google Groups > "Kubernetes developer/contributor discussion" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to kubernetes-dev+unsubscr...@googlegroups.com. > To post to this group, send email to kubernetes-...@googlegroups.com. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/kubernetes-dev/CAHKJ1n-JTVJK%3DJ2U%2B7KsfnRUGkcx3Uh_ > w0aJNH0o9g8KDFzbJA%40mail.gmail.com > <https://groups.google.com/d/msgid/kubernetes-dev/CAHKJ1n-JTVJK%3DJ2U%2B7KsfnRUGkcx3Uh_w0aJNH0o9g8KDFzbJA%40mail.gmail.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Kubernetes user discussion and Q&A" group. To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-users+unsubscr...@googlegroups.com. To post to this group, send email to kubernetes-users@googlegroups.com. Visit this group at https://groups.google.com/group/kubernetes-users. For more options, visit https://groups.google.com/d/optout.
