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