Skip to content
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

Description of all IRC bots #711

Open
Altai-man opened this issue Jul 15, 2016 · 24 comments
Open

Description of all IRC bots #711

Altai-man opened this issue Jul 15, 2016 · 24 comments

Comments

@Altai-man
Copy link
Member

@Altai-man Altai-man commented Jul 15, 2016

At the Glossary page we already have dalek, camelia and yoleaux, but also we have bisectbot. Is it still working? If yes, I think we should write about it too.

@Altai-man Altai-man added the docs label Jul 15, 2016
@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Jul 15, 2016

It is working great! There's also committable. benchable is going to appear soon too.

However, I recommend you to wait a couple of days before writing about these bots. There are way too many commits in the last few days (see https://github.com/perl6/bisectbot/), it would be sad to have some information become outdated tomorrow.

@Altai-man
Copy link
Member Author

@Altai-man Altai-man commented Jul 15, 2016

English is not my native(really, really not), so for a native reader of docs my writing skills are quite limited. Because of that, I opened this issue instead of commiting, since I hope someone else will write this out.
I'm not in a hurry too, so waiting for some time is not harmful, of course.

@AlexDaniel AlexDaniel changed the title bisect bot description Description of all IRC bots Jul 26, 2016
@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Jul 26, 2016

If we have a description for some bots, there's probably no reason not to write about all other bots we have. I changed the title of this issue.

👍 Feel free to edit this list 👍

@AlexDaniel AlexDaniel added the big label Jul 26, 2016
@zoffixznet
Copy link
Contributor

@zoffixznet zoffixznet commented Jul 26, 2016

Added desc for my bots. I think it's useful to add both the source (if people want to run a copy somewhere) and the contact for the person(s) who's running the bot in case something needs to be changed about the way the bot runs.

@coke
Copy link
Collaborator

@coke coke commented Jul 26, 2016

I wonder if this is the sort of thing that better belongs in the rakudo
wiki.

On Tuesday, July 26, 2016, Zoffix Znet notifications@github.com wrote:

Added desc for my bots. I think it's useful to add both the source (if
people want to run a copy somewhere) and the contact for the person(s)
who's running the bot in case something needs to be changed about the way
the bot runs.


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#711 (comment), or mute
the thread
https://github.com/notifications/unsubscribe-auth/AADEUeCNHhUKblkU0hVIxHf4Xe5NC9fYks5qZoR_gaJpZM4JNyNg
.

Will "Coke" Coleda

@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Jul 27, 2016

I don't think that it does. To me it seems that creating language/community is a very good idea. All things like bot descriptions will be moved there eventually (per #728).

Anyway, it is not rakudo-specific, so I'm not sure why would it fit rakudo wiki better than language docs.

@coke
Copy link
Collaborator

@coke coke commented Nov 30, 2016

Sorry, yes, I was trying to indicate non-spec, not rakudo-specific.

@coke
Copy link
Collaborator

@coke coke commented Dec 12, 2016

Maybe this belongs on perl6.org/community

@zakame
Copy link
Contributor

@zakame zakame commented Sep 2, 2017

Hmm would something like a spec that bots can implement would do to document them automatically in some way? I could imagine some other IRC doc bot querying these others for their description, function lists, example usage. and maybe author and source (for those who wish to run a copy,) so the doc bot can update a page somewhere (just like a logger bot.) This way, there's less issue about the bot list going out of date.

@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Sep 2, 2017

@zakame I don't think we will ever manage to implement something like this. Not all bots are controlled by us, so it is unlikely that there'd be something all bots will adhere to. I think a simple page with short descriptions of all bots (+ links to their documentation) is all we need.

@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Sep 2, 2017

Oh, the problem is that there's no clear place where we could put it. I was suggesting language/community page, but it seems that it won't happen. There's https://perl6.org/community/ and maybe we can even have https://perl6.org/bots ? But then it's an issue for https://github.com/perl6/perl6.org/

@toolforger
Copy link

@toolforger toolforger commented Sep 2, 2017

Providing a place to put such a description can be enough of an incentive to make bot authors fill it.
Particularly if it is useful for bot authors in some way - easier installation, less hassle with implementing standard commands, that kind of thing.

@zakame
Copy link
Contributor

@zakame zakame commented Sep 2, 2017

I suppose in https://perl6.org/community/irc then? Perhaps there should be a note there on how bot authors can update the list (e.g. post a new issue on the perl6.org repo, or reach someone on IRC, etc.)

@JJ
Copy link
Contributor

@JJ JJ commented Mar 13, 2018

Can someone please update the list? I see some "soon to be decomissioned", for instance.

@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Mar 13, 2018

Also there are more bots now.

zoffixznet added a commit to Raku/raku.org that referenced this issue Mar 13, 2018
Updates Raku/doc#711
@zoffixznet
Copy link
Contributor

@zoffixznet zoffixznet commented Mar 13, 2018

It's possible the list on https://perl6.org/community/irc is more up-to-date than this Issue. (I was under the impression it was already closed)

soon to be decomissioned

😨 poor dalek. He never hurt anyone!

@JJ
Copy link
Contributor

@JJ JJ commented Mar 13, 2018

@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Mar 13, 2018

So. Close this issue for good?

Also there are more bots now.

reportable, notable, shareable are not mentioned on the website. I think we'll also have BeastieBot soon (a clone of PufferBot but on freebsd instead of openbsd?). The issue can be moved to perl6.org repo if we need that.

@zoffixznet
Copy link
Contributor

@zoffixznet zoffixznet commented Mar 13, 2018

Puffer bot is already listed. I do notice we list three bots in Glossary in the docs tho https://docs.perl6.org/language/glossary#IRC

@JJ
Copy link
Contributor

@JJ JJ commented May 9, 2018

Is someone up for this? If you add one at a time, it's not such a hard work...

@taboege
Copy link
Member

@taboege taboege commented Dec 4, 2018

As an addendum: Bots camelia, dalek and yoleaux are mentioned with links in https://docs.perl6.org/language/glossary#Bot but none of the links work. If they are documented, that could be fixed as well. However, the links in @AlexDaniel's list point to the same non-existent anchors in the Glossary.

PS: Sorry, I accidentally clicked somewhere on AlexDaniel's list and that committed something. I can't roll back that change nor understand the "diff" it shows me to undo it.

@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Dec 4, 2018

@taboege fixed! Yeah, github comments are weird.

@AlexDaniel
Copy link
Contributor

@AlexDaniel AlexDaniel commented Dec 4, 2018

@taboege as for broken links, I think these sections existed in the glossary but then were moved elsewhere (or removed completely). @JJ can you take a look?

@JJ
Copy link
Contributor

@JJ JJ commented Dec 4, 2018

They were not moved, far as I know... They should be fixed, I guess

@rba rba mentioned this issue Jul 18, 2019
13 of 24 tasks complete
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
8 participants