[12:38] Hey belkinsa - Thank you for the help with the wiki pages. Excellent as always. [12:38] Not a problem, sorry for changing up the format of the homepage. [12:39] Most team wiki page home pages are like that. [12:39] I like it better now. Thank you! [12:39] Not a problem. [12:43] Aleo, you think we need a translation bit on the home page so people can translate our pages? [12:43] sure, Japanese, Spanish? [12:43] Russian, French, German, Swiss are four others [12:44] uuuuu, you win. [12:44] :d [12:44] Actually, if we can discuss it for a while [12:44] No, I don't speak those. I was just listing them. [12:45] what would be the purpose of having any other language? [12:45] For the non-English speakers or the ones with weak English, so they can understand what we do. [12:46] encourage participation. Sounds good, but do you think it will lead to having different groups doing different things [12:46] ? [12:47] I think not, but the main issue is within the mailing-list, most of us (right now) can speak English well and I think English is more accepted in mailing-lists in most of the teams here. [12:48] I think it is a great idea, however we would need to keep a universal language for coordinating our efforts [12:48] +1 [12:48] let's try one or two language "branches" [12:49] and see what happens [12:49] Sure. [12:49] sounds like an experiment. Let's call English language Control, haha [12:50] lol [12:50] Maybe Spanish is one of the branches. [12:50] We would need to do different mailing list just in case it is too confusing. [12:51] We could but that might get too messy. [12:51] yes, actually. Translation in the same email? [12:52] Too messy too. [12:52] I need to look at other teams and hjow they do it. [12:52] how* [12:52] Is there precedent of a group handling different languages at the same time? [12:53] I would like to research that too. [12:53] I don't know [12:54] let's try to find out. Give me some time. I will reply again before going to sleep today. [12:54] About an hour. [12:56] Okay, I have other work to do and I still need to dress for the day [13:38] @belkinsa yes I am free, just got to work [13:39] I know that was last night, I leave this window open at work [13:40] You just can use belkinsa, not with @. Ah, I see. Our next meeting is next Friday at 1900 UTC. [13:40] Agenda: https://wiki.ubuntu.com/UbuntuScientists/Meetings/Agenda/06282014 [13:46] Aleo, https://wiki.ubuntu.com/Translations [13:50] Thank you, I have been looking at it. I have not been able to find double language mailing list in any group yet. [13:50] How do you make red letter, by the way. [13:51] You have x-chat, right? [13:51] yes [13:51] It's highlighting when someone types in your name. [13:52] Easiest way to type in a name in the channel, if the person is there, is to type in the first letter of the name in lower case and press tab to get it. [13:52] ah, so when I write your name it makes it red. Even though I do not see it. [13:52] ah, ok [13:52] got it [13:52] Yup. [13:52] Aleo [13:52] belkinsa, [13:52] haha [13:52] Yup [13:53] Ok, I will keep looking at the info. I am asking at the ubuntu translator irc channel [13:54] Alright, thanks for your help. Should this be added to the agenda: https://wiki.ubuntu.com/UbuntuScientists/Meetings/Agenda/06282014 [13:54] You can add your own notes there if you want [13:54] Just don't forget to @SIG@ after the notes for an item [13:57] what is @SIG@? [13:58] A moinmoin wiki function that allows you to timestamp something [13:58] Example, "This is comming from http://summit.ubuntu.com/uos-1406/meeting/22241/community-1406-ubuntu-dubuntu-scientists/UOS, I was think about roles like founder, deputies (if needed), go-to-people for program related questions (see here), ect. -- belkinsa 2014-06-20 08:37:14 " [13:59] That belkinsa 2014-06-20 08:37:14 is the stamp [14:00] All of it is manually written? [14:00] No, it does it for you when you submit changes on a wiki page with @SIG@ [14:00] http://wiki.ubuntu-women.org/FAQ#How_can_I_edit_a_wiki_page.3F [14:02] Ok, I understood. I will do as you say. Thank you again [14:02] Not a problem. [14:03] Oh, you may also add items to the agenda but you can just mark your name on them but I want notes to be @SIG@ 'd. [14:20] belkinsa is something like this useful? [14:20] https://wiki.ubuntu.com/akshmakov/sandbox/Packaging [14:20] I'm writing up some other topics I've been working with recently, OpenCL at the moment [14:41] akshmakov, you know there might be a page already like this one. [14:45] I found that the existing pages are either outdated or present innefficient solutions [14:46] Are you fixing them because it's useful to get them up to date. [14:46] Its mainly a reference for myself [14:46] They are not so much out of date, just scattered references on individual tools [14:46] I see, but make sure after you are done, you place the final copy on the wiki page of that program. [14:46] Out of date was in reference to OpenCL [14:47] The point of the page was how to package custom software, which can be very useful in a scientific setting [14:47] I see. [14:48] Especially when you build your own forks of libraries and want to use them on your system [14:48] We could point that final product to our resources page [14:48] It can take months to get changes to get approved upstream [14:48] and even longer before they get incorporated into debian/ubuntu [14:48] Indeed. [14:48] I think we have a debian guy in our team [14:49] I am indirectly involved with neurodebian myself [14:49] https://launchpad.net/~ghisvail is the guy [14:50] Yes, he emailed me when I introduced myself on the email list asking for some details on my experience [14:50] Ah, I see. [14:51] The utility of explaining this to users is it can allow for quick testing and distribution of in house software [14:51] I write a script for my lab that lets them use equipment X [14:51] I can have it on the lab repo within a day [14:51] They can use it in the meantime while I deal with having it merged upstream [14:52] If there is even a project to merge it with [14:52] I see, I think bringing it up to the next meeting might be pointless at this time, maybe the next one? We only have two developers (I think) and I think the rest of us are non-developers. [14:53] I briefly explained to ghisvail my philosophy on getting labs to use open source software [14:53] Wait... [14:53] * belkinsa faceplams [14:53] That's a goal of our team. [14:53] That could be brought up in the next one. [14:53] you have to make it easy, and for labs this means someone needs to take the torch in management [14:55] >I think the rest of us are non-developers [14:55] Good point. [14:55] And leadership is needed also. [14:56] Thats ok, the whole point is utilizing the technical users in a lab/group and make it as easy as possible to share their work with their colleagues [14:56] akshmakov, I look forward to reading whatever you write and lear from it. [14:56] belkinsa, I am going to sleep. I could not find any team that handles double language in the mailing list. I will write it as a discussion item for the next meeting. [14:56] Aleo, sure thing. [14:57] Slaapwel, Aleo. [14:57] Sleep well* [14:58] See you! [15:00] I can bring it up in terms of input, I think it is very difficult to give a lab a single cd image of an ubuntu that works for everyone [15:00] Sure. [15:01] Instead my personal opinion is about teaching the technical users in the lab how to set up an efficient lab ecosystem for linux and ubuntu specifically [15:02] Of course, there is still a lot of overlap between users, say everyone in a math group will need to use Mathematica [15:02] In my experience it has been a lot easier to get people to use linux when you show how much simpler it is than managing a windows system [15:03] But if both systems require you to fiddle around with compiling packages or broken installers or out of date software [15:03] stick with the devil you know is the general attitude