New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Documentation Bot for IRC #48
Comments
Discussed 20170105 in Testing Working Group Meeting
|
AnsiBot is currently live in #ansible-devel, and has 4 commands
the next two commands do the same thing (possible split later if we can call the api directly)
|
Will need renaming (bot and Git Repo) to avoid confusion with github.com/ansible/ansibullbot/ |
@gundalow I agree
|
I picked answerbot (and answerbot_) both are now registered with NickServer on Freenode and the bot is live on |
Cool. anything left to be done on this or can it now be closed? |
I would suggest this be left open, to facilitate commity feedback.
!about points here
…On Thu, Jan 12, 2017, 20:08 Toshio Kuratomi ***@***.***> wrote:
Cool. anything left to be done on this or can it now be closed?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#48 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAqxtZdsNgytPGjWcc6qtPMUoc6Jx_J2ks5rRmwdgaJpZM4LTWRM>
.
|
when are you guys planning to enable (even as a preview/ alpha etc) in |
It is running there @DanyC97 Whats you're IRC nick, then i can catch up with you there ? |
@allanice001 following the DM chat we had should you find anything and need someone to give it a go please do reach out to me here or irc ( for everyone benefit the behavior is like this:
|
Bug fixed, and committed to upstream repo. Thanks @DanyC97 for the report |
Proposal: Documentation Bot for IRC
Author: Ally Bowles <@akatch>
Date: 2016/12/20
Motivation
Frequent users of
#ansible
have noticed that in many cases, users with questions just need to be pointed to the right documentation page. This often means that someone who wants to help must locate and link to the documentation page. Usually the correct topic is easily searchable, but it would be vastly more efficient to instead issue a command to an IRC bot and get a documentation link back. Additionally, common topics that require only a brief explanation might be available as canned command responses, allowing us to provide more consistent advice to users.Problems
What problems exist that this proposal will solve?
Solution proposal
Many software-related IRC channels have documentation bots that provide the correct documentation link given key words. One excellent example of this is the
#nginx
channel on Freenode - their bot provides documentation links, canned responses, and even a paste site that automatically links directly to the channel upon upload. This makes it very easy to give standardized, detailed answers to new users who many have a lot of the same questions. It negates the need for a user providing support to have to hunt down the correct documentation page and instead simply issue a command that returns a documentation link or canned response directly to the user asking the question.Dependencies (optional)
Testing (optional)
We will want to verify that user-issued commands work as expected
Documentation (optional)
Yes - the bot should have a "help" command that sends a private message to the requesting user containing usage documentation.
Anything else?
Our discussion in the 2016/12/20 Core meeting suggested that the bot's code should/would be public to facilitate community PRs.
The text was updated successfully, but these errors were encountered: