=== Pici` is now known as Pici === Rafik_ is now known as Rafik [09:37] Why isn't there #ubuntu-confessional or #ubuntu-empty-your-mind channels ! :p [09:39] I can lend you my guinea pigs for that [09:41] Rafik, there is #ubuntu-offtopic but all ubuntu channels are expected to be CoC compliant, so the contents of some people's minds simply isnt appropriate [09:41] there are other places to do that, anyway. [09:42] lol [09:42] elkbuntu: you are right [09:42] half left as well. [09:43] elkbuntu: many many ideas in my mind.. ubuntu-arabic is nearly dead.. don't find a way to find contributor.. should we kill the project.. should we try to reawake it.. [09:44] that's the kind of things I need to talk about.. [09:46] ubuntu-arabic is the translation project? [09:50] no, it's separated from ubuntu-l10n-ar even if we tried to encourage the translation via the ubuntu-arabic project [09:51] separated why? [09:52] I meant the translation team will not be affected it ubuntu-arabic is dissolved. [09:53] ah [09:53] so what is the actual aim of ubuntu-arabic? [09:54] ubuntu-arabic was created to let the arabic loco work together to produce/offer the arabic ubuntu-related contents/support [09:55] we even offered to host websites.. [09:55] ok right. and who were the original locos? [09:56] Jordan, Tunisia, Morocco, Lebanon, Saudi Arabia, Egypt.. [09:56] some LoCos are not active themselves [09:57] I personnaly tought if we build a bigger team, it will work [09:57] sometimes a bigger team means everyone else sees other people who can do the work, rather than opportunities to do the work/ [09:58] first step is to inspire the locos again somehow [10:01] the problem is : the community is being divided to small unities and each one is taking a kind of Independence. This is due to two reasons. either people don't understand what is a loco or they are simply searching for personal benefits through the loco [10:02] Some are in a team for the team itself, not for ubuntu [10:04] yeah that's the problem [10:09] It's not easy to handle such things.. especially when some IT professionals are active in a loco but don't get the sens of the community.. it results in reinventing things and rules designed for the loco instead of using the existent documents [10:10] the loco simply gets out of the loco project [14:53] anyone going to be around for openweek in a few minutes? [14:54] jcastro: what do you mean? [14:55] I need to make sure #ubuntu-classroom is set in a way so that only sabdfl and myself can speak [14:55] but I have _zero_ irc kung fu [14:56] If someone could help me out that would be great [14:58] sure [14:58] you people are no use [14:58] I WANT TO KNOW HOW TO HYPHENATE HYPHENATE [14:58] groar [14:59] :-( [14:59] and wrong channel to boot. [14:59] * Myrtti goes to bed to cry [14:59] nalioth: thanks <3 [15:00] jcastro: when you need to speak, op up and /mode #ubuntu-classroom +m [15:00] when the class is over, do the same, but with -m [15:00] nalioth: you're late [15:00] Myrtti: i am? [15:01] [17:00] ~~~jcastro [n=jcastro@ubuntu/member/jcastro] has left #ubuntu-irc [] [15:01] [17:00] < nalioth> jcastro: when you need to speak, op up and /mode #ubuntu-classroom +m [15:01] ah [15:01] i'm going blind, too === Rafik_ is now known as Rafik [17:27] hi does somebody knows where i can find the freenode authplugin for supybot? [17:31] juliux: there isn't one [17:31] or am i thinking something weird? what does the authplugin do? [17:32] nalioth: it is mentioned in the bantracker read me [17:32] my supybot (ubot3) auths on connect [17:33] but i'm not any kind of supybot expert [17:33] perhaps ask in #supybot ? [17:33] ok [17:41] !botclone | juliux [17:41] juliux: Ubottu uses supybot, which is available in the main !repositories, with additional plugins that are available at http://tinyurl.com/3s8roe [18:48] jussi01: yeah i allready saw that page [18:48] :) [18:48] jussi01: i also found the freenode auth plugin;) [18:49] juliux: what do they do? [18:50] nalioth: that is the next thing i want to figure out [18:50] 9_9 [18:51] nalioth: the read me says that you can ignore with that plugin all messeas from un-identified people [18:54] juliux: well, that isn't good in an Ubuntu info bot :( [18:54] nalioth: we will use our bot not as an infobot, we have an extra infobot [18:54] nalioth: i only want to setup a log and bantracker bot [18:55] so just set it up to ignore all messages from anyone but it's owner [19:10] stdin: /window 39 [19:10] sorry === nizarus_ is now known as nizarus === fetova_ is now known as fetova [23:17] ubottu: ask [23:17] Please don't ask to ask a question, simply ask the question (all on ONE line, so others can read and follow it easily). If anyone knows the answer they will most likely reply. :-) [23:17] ubottu, no, ask is If you have a question, just ask. For example: "I have a problem with ___; I'm running Ubuntu version ___. when I try to do ___ I get the following output ___. I expected it to do ___." Don't ask if you can ask, or if anyone uses it, or pick one person to ask: always ask the whole channel. We're all volunteers; make it easy for us to help you. If you don't get an answer, ask later or at www.ubun [23:20] jspiro: Too long. [23:20] way too long [23:20] i think the present one is too long already [23:20] it was originally "Don't ask to ask, just ask" [23:20] LjL: What if I could summarize it more? [23:20] now it surpasses a line's length on my screen [23:20] Flannel: LjL: Or what if I split it into two parts, !ask and !gq ? [23:20] jspiro: What would you summarize to that isn't already in the original? [23:21] jspiro: gq? [23:21] jspiro: it's split already [23:21] oh [23:21] !attitude [23:21] The people here are volunteers, your attitude should reflect that. Answers are not always available. See http://wiki.ubuntu.com/IrcGuidelines [23:21] !please [23:21] Avoid your questions being followed by a trail of "Please, help me", "Can nobody help me?", "I really need this!", and so on. This just contributes to making the channel unreadable. If you are not answered, ask again later; but see also !repeat and !patience [23:21] !doesntwork [23:21] Doesn't work is a strong statement. Does it sit on the couch all day? Does it want more money? Is it on IRC all the time? Please be specific! Examples of what doesn't work tend to help too. [23:21] !pm [23:21] Please ask your questions in the channel so that other people can also benefit AND help you. Please don't PM a user in the channel without asking first, some find it rude. [23:21] LjL: ah. i didn't know those factoids. [23:21] !elaborate [23:21] Please elaborate, your question or issue may not seem clear or detailed enough for people to help you. Please give more detailed information, errors, steps, and possibly configuration files (use the !pastebin to avoid flooding the channel) [23:22] hmm, it seems nobody in #ubuntu uses those though. How could we make them better known? Maybe by adding "see also !elaborate" to the end of !gq? [23:22] jspiro: it's not true that nobody uses them [23:22] jspiro: I don't think its really necessary though. [23:22] LjL: ok, it seems to me. [23:22] Flannel: fair. [23:23] jspiro: When those sorts of issues arrise, generally its a situation that is best handled through actual typing [23:23] Flannel: also fair :) [23:23] jspiro: keep in mind two things. one, the bot should flood the channel as little as possible, two, people won't read overly long factoids anyway [23:23] jspiro: and to make factoids more known, there is only one way - use them when appropriate [23:24] jspiro: the bot has search functions and a webpage. if a few people are fluent with the bot and know how to search for factoids, and use them, other people will follow [23:24] i used to do that a lot, i'm much less active currently, but that doesn't make that any less true [23:24] how's this? [23:24] ubottu, example is Please give us full details. For example: "I have a problem with ___; I'm running Ubuntu version ___. when I try to do ___ I get the following output ___. I expected it to do ___." [23:25] that's the part of my proposed new !ask I really liked. [23:25] it's from #debian's bot (dpkg)'s !ask [23:25] it's basically !error put in a different way [23:25] !error [23:25] Please elaborate, your question or issue may not seem clear or detailed enough for people to help you. Please give more detailed information, errors, steps, and possibly configuration files (use the !pastebin to avoid flooding the channel) [23:25] i don't particularly like the "___", i'd change them to "..." [23:25] but it might work [23:26] Sounds more like a bug report than a support request though. [23:26] Flannel: yes. IIRC I wrote it for dpkg. It's not perfect. [23:26] in fact it's not great. [23:26] !details is Please give us full details. For example: "I have a problem with ..., I'm running Ubuntu version .... When I try to do ..., I get the following output: ..., but I expected it to do ..." [23:26] I'll remember that, LjL [23:26] !example is details [23:27] having it won't hurt [23:27] but i agree it's not always appropriate [23:27] ubottu: no, details is Please give us full details. For example: "I have a problem with ..., I'm running Ubuntu version .... When I try to do ..., my computer did: ..., but I expected it to do ..." [23:27] [23:27] LjL: a little better? [23:27] most of the time, what's important is just a description of the damn problem [23:28] jspiro: see above ;) [23:28] yep :) people have trouble explaining. [23:29] jspiro: ah there's also this [23:29] !nothing [23:29] Saying "It says nothing", "It does nothing" is generally not very useful for troubleshooting. Please be as specific as possible: if you see a black screen, say so, if you see a shell prompt, say so, if you see an !error message, say so - Also, most !CLI commands don't print anything when they succeed, but only when they fail. [23:29] and this [23:29] !errors [23:29] If you have problems or errors, you will need to describe/paste them. Please use the !pastebin for errors that cannot be quoted in a single IRC message [23:29] actually [23:29] !no error is errors [23:29] You are editing an alias. Please repeat the edit command within the next 10 seconds to confirm [23:29] !no error is errors [23:30] LjL: I think more see-also's would help. [23:30] But all those you showed are excellent factoids. [23:31] jspiro: the main problem with see-also's (although i added a LOT of them) is that people will too often use them in the channel [23:31] LjL: how do we avoid people from using them in channel? maybe a rate limit? [23:31] jspiro: do note that the "nothing" factoid, for instance, doesn't have "plain" see-alsos, but does have words prefixed with !... [23:31] i see. [23:32] jspiro: we avoid it by telling them not to, a rate limit wouldn't help because it'd need to be extremely low. [23:32] !msg the bot [23:32] uhm type that yourself if you don't know its contents [23:32] the bot has me on ignore because it's silly [23:33] LjL: :) [23:33] !msg the bot [23:33] Please investigate with me only with "/msg ubottu Bot" or in #ubuntu-bots. Search for factoids with "/msg ubottu !search factoid". [23:34] all : why does ! talk to channel by default? why doesn't ! normally /msg? [23:34] jspiro: err, and who would it /msg by default? [23:34] it can't just guess the intended recipient [23:34] LjL: good question. Dunno. How about the last 3 people to have spoken? [23:35] meh don't make things way more complicated than they need to be, no :) [23:35] ok :) [23:35] the bot needs to talk in the channel [23:35] and people need to be educated to use it in private if they need it for their own purposes only [23:35] and, as far as code tweaking goes to provide subtle hints to that -- [23:35] i assure you they've been thought over, and implemented [23:36] jspiro: try doing !test | jspiro for instance [23:36] !test | jspiro [23:36] !foo | jspiro [23:36] jspiro, please see my private message [23:36] jspiro: bar [23:37] !foo | jspiro [23:37] jspiro, please see my private message [23:37] ah i see. the (In the future, please use a private message to investigate). [23:38] jspiro: yeah. does the same if you !test > jspiro, or at least it did last time i checked [23:39] by the way stdin, i don't think the recognition of either "ubottu" or "ubotu" being in the message works [23:39] !test > floodbot1 (floodbot1, see the private message from ubotu ) [23:39] or uhm, perhaps it does now [23:39] it should [23:39] didn't couple days ago :) [23:40] why not just run a second bot named "ubotu"? [23:40] wait, floodbot1 isn't here, so it won't show the "please see my private message" anyway [23:41] jspiro: we don't own the nick [23:41] stdin: right but i'm testing it in -bots right now [23:41] with fellows who are actually there [23:41] and it does seem to work [23:42] stdin: who does? can you ask them kindly to give it to you? or can you ask freenode to? [23:42] seveas [23:43] who is seveas? [23:43] the owner of the ubotu nickname. [23:43] so would seveas give us it? [23:43] i don't think so. [23:44] and i'm not going to ask, either. [23:44] he owns the nick and always has, and he uses it afaik anyway [23:44] (for his bot) [23:44] what is his bot? [23:46] https://launchpad.net/ubot [23:48] ok. anyway, thanks for all the explanations all. === BIYJAMGe is now known as LjL