Übersicht Letzte Änderungen Letzte Änderungen in der Umgebung KurzAnleitung Blog RSS

CommBot

This is conversation about a robot that:
[fr] Ceci est une conversation à propos d'un robot qui :

 <lion> It'd be cool if:
 <lion> When you got the message,
 <lion> you could just reply to the message,
 <lion> and your response would be the authorization or rejection.
 <lion> So, this means we need a little more sophisticated concept of "message delivery."
 <lion> You're not just receiving a message,
 <sm> I kind of set that up yesterday
 <lion> you are receiving a message, AND making (or delaying) a decision.
 <lion> sm: Awesome!
 <sm> like this: mailed-in comments go to the wiki
 <sm> non-wiki subscribers used to get bounced
 <sm> but now they go via a mail list which forwards non-subscriber posts to me for moderation
 * lion nods
 <sm> is that like.. ?
 * lion doesn't totally get it-
 * lion was talking about:
 <lion> Whatever interface is used to deliver you the message,
 <lion> the same interface is used to communicate a decision,
 <sm> agreed
 <lion> which goes to something else, not necessarily the source of the message.
 <lion> You get: Msg + Decision
 --> entmoot__ (~entmoot@host135-229.pool62211.interbusiness.it) has joined #wiki
 <lion> The Courier understands how to communicate the results of the Decision to whatever agents can act upon it.
 <lion> Now the bot delivering the message,
 <lion> upon noticing my arrival,
 <lion> needs to negotiate with me about the appropriateness of the message and the timing-
 <lion> "Is now a good time to receive a message regarding Foo wiki?"
 <lion> It needs a sense of priorities,
 <lion> so that it can give me highest priority stuff first,
 <lion> (eventually...)
 <lion> So we want to communicate: Message + Domain of the message (to the robot)
 <lion> the robot receives the message, the domain,
 <lion> when it is able to find me,
 <lion> it asks:
 <lion> "Is this a good time to field a question about Domain?"
 <lion> To which you respond,
 <lion> "No, try back in 15 minutes."
 <lion> Or you just don't respond,
 <sm> I can see that getting kind of busy :)
 <lion> it repeats the question once in 5 minutes,
 <lion> and then if not after 5,
 * sm loves sw that requires no attention
 <lion> in 2 hours,
 <lion> and then it just keeps it on hold.
 <lion> sm: Ah, well this isn't sw.
 <lion> This is people.
 <sm> true
 <lion> The software is just a representative for a person that just submitted additions to something you wrote.
 <sm> same :)
 <lion> If you aren't responsive,
 <lion> you know- they'll just take their edit power somewhere else. {;D}=
 <lion> BUT! What you say fits right in:
 <lion> Some domains,
 <sm> yes, nice to be able to get all this notification when you want it
 <lion> you'll just want to say: "Never bug me about this. I'll let you know if I'm interested."
 <lion> You could ALSO-
 <lion> You could put into the bot:
 <lion> "I'm working on X right now."
 <lion> "If someone has a message for me about X,"
 <lion> "good."
 <lion> "If it's a high priority emergency,"
 <lion> "good."
 <lion> "otherwise, hold it for now."
 * sm must go.. see you later
 <lion> Bot may ocassionally ask: "Are you done working on X now?"
 <lion> okay {:)}=
 <lion> take care {:)}=

Afterthoughts:

Implications for Wiki

If a HalfWiki uses a system like this, there's no reason the edits wouldn't be be near-instantaneous.
[fr]Si un SemiWiki utilise un système comme ceci, il n'y a pas de raison que les éditions ne soient pas proche de l'instantanée.

That is, if someone submits an edit, and 5 minutes later, it's been approved and worked in, that communicates something to people.
[fr] Ce qui signifie que si quelqu'un soumet une édition, et 5 minutes plus tard, elle est approuvée et travaillée, ceci communique quelque chose aux personnes.

It could even be the case that 10 people's comm-bots can collaborate, and wait for just 1 person to give approval. If approval is given, a PaperTrail? is granted, and the "message" is deleted from the 9 other people's queues..! The end result is that contributors would notice a very fast response time (5 minutes to edit approval,) and thus become more likely to engage in the process.
[fr]Ceci pourrait même être le cas quand 10 comm-bots de personnes peuvent collaborer et attendre pour simplement une personne pour donner une approbation. Si le consentement est donné un PaperTrail? est accordé et le "message" est effacé des queues des 9 autres personnes…! Le résultat final est que les contributeurs noteront un temps de réponse très rapide (5 minutes pour une approbation d'édition) et de ce fait deviennent plus probalement prêts à s'impliquer dans le processus.

If they become engaged, eventually you just hand the person free reign over the wiki. Ideally, fitted with a CommBot themselves.
[fr]S'ils s'impliquent, éventuellement vous donnez simplement la main à la personne pour avoir un règne libre sur le wiki. Idéalement, cela colle avec un CommBot.

This is not to confuse HalfWiki with a "Real" wiki- a carefully guarded wiki is still different than a wiki that anybody can go to, and immediately write on.
[fr]Ceci pour ne pas confondre le SemiWiki avec un "Vrai" wiki - un wiki soigneusement gardé est encore différent d'un wiki où quiconque peut se promener et écrire immédiatement dessus.

Discussion

See IrcTranscript for some meta discussion.
Voir IrcTranscription pour d'autre meta discussion

Diese Seiten lokal erstellen: PatrickAnderson

Sprachen: