16:08:18 #startmeeting 16:08:18 Meeting started Thu Jan 17 16:08:18 2013 CET. The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot. 16:08:18 Useful Commands: #action #agreed #help #info #idea #link #topic. 16:08:19 now 16:08:40 #topic Caribou and Mousetrap 16:09:10 #info some weeks ago Daiki Ueno was interested on being caribou maintainer 16:09:21 #info This week we were talking with eitan, and he sees that a good idea 16:09:41 #info eitan said that he will send a mail to daiki ueno soon 16:10:01 Ugh. Sorry. Lost track of time. 16:10:09 #info extra: it is seems that daiki ueno lives in Japan, something to take into account when pinging him 16:10:11 mgorse, no problem 16:10:15 we have just started 16:10:42 #action API will wath over this, in order to ensure that Daiki receives the message, and also giving hints about releases 16:10:49 joanie, ? 16:10:53 I think that you would be the best 16:10:57 to talk about mousetrap here 16:11:00 ok 16:11:05 I'll info like you did 16:11:20 makes sense 16:11:44 #info There is a new NSF-funded program called FOSS2SERVE 16:12:01 Oh, that sounds awesome :) 16:12:41 #info This program is designed to get profs more comfortable with and actively teaching free software with a humanitarian focus in university CS courses. 16:13:23 #info The program is a collaboration between Western New England University (Heidi), Drexel University, and Nassau Community College. 16:13:57 #info As part of this, and as part of my idea to do an outreach program for professors, we are giving Mousetrap to them as a module. 16:14:18 #info The students are beginning work on making Mousetrap GNOME 3 compatible 16:14:41 #info And PiƱeiro and I will be more or less mentoring the professors on being module maintainers 16:14:53 #info And doing so according to GNOME practice 16:15:19 #info If, for some reason, nothing becomes of this, we lose nothing. 16:15:38 #info And we stand to gain more contributors and getting Mousetrap back into shape. 16:15:55 #info And ultimately accepted as a proper module and AT. 16:16:19 #info We may or may not see students in #a11y. Currently they are going to use #mousetrap. 16:16:44 #info But if any students (or professors) show up asking questions about Mousetrap, this is why. :) And please help them. :) 16:16:49 I think that covers it 16:17:09 and sorry for being slow. I have a migraine and a 3G connection thanks to comcast. 16:17:53 no problem 16:17:55 was good 16:18:12 so, any question doubt comment about caribou and mousetrup stuff that we shared? 16:18:17 *mousetrap 16:18:18 faster than me ;-) 16:18:40 sorry, who is daiki ? 16:19:25 daiki ueno 16:19:31 is a developer who is doing most 16:19:37 of the recent work of caribou 16:19:46 and when I say most, is about 95% of the commits 16:19:54 me being just the releaser 16:20:16 he is experienced on this virtual keyboard thing, as was (is) the maintainer of eekboard 16:20:25 and also have experience on input methods 16:20:36 he collaborate now and then with rui matos 16:20:40 (IRC: rtcm) 16:20:46 ok, thanks ! 16:21:03 you are welcome 16:21:21 ok, so lets move 16:21:23 #topic Python 3 (Are we there yet?) 16:21:31 well, this week was release week 16:21:33 * joanie smiles at jhernandez 16:21:37 and we had a accerciser release 16:21:39 so ... 16:21:42 jhernandez, ? 16:21:48 something to mention about that last release? 16:21:58 on the topic of Python 3 16:22:00 :) 16:22:13 yes 16:23:11 #info There were a few bugs regarding the newly Python3 code 16:23:55 #info Joanie did a good work reporting bugs and providing patches. All patches have been reviwed and merged into master. 16:25:03 #info So Accerciser 3.7.4 seems to be the definitive-and-working Python3 release 16:25:07 (done) 16:25:08 :] 16:25:15 well, that seems good ;) 16:25:16 thanks 16:25:19 so that leaves the mag example 16:25:31 well, and as clown is not here 16:25:31 which is not a requirement 16:25:37 unless you have information about that 16:25:41 but since it is not python 3 related.... 16:25:50 no info 16:25:58 ok, then I will add some info myself 16:26:03 but I am wondering if we should remove it 16:26:04 ok 16:26:13 #info I tried to do a python3 build of the gnome stack 16:26:44 #info by setting os.environ['PYTHON'] = 'python3.3' at my .jhbuild rc 16:26:51 #info some relevant modules are still not ported 16:27:09 #info specific example: gobject-introspection 16:27:31 #info talking with Colin Walters, seems to suggest that he doesn't plan to fix that soon, but that patches are welcome 16:27:49 #info current python3 porting table: https://live.gnome.org/GnomeGoals/Python3Porting 16:28:07 Oh, right--I noticed that, too. Seems that there is C code that refers to Python structures that needs to be ported. 16:28:40 #info why I was mentioning it? /me fears that 3.8 will be still a python mixed release, so it seems that as usually, we did our homework before a lot of people 16:29:14 But I can run Orca and Accerciser in Fedora 18 with Python 3 16:29:22 it seems that in general we feel the pressure of those gnome goals stronger that others 16:29:28 joanie, that is good 16:29:35 so either it's a non-issue or distros are fixing it for us 16:29:46 what I mean is that on a 3.8 environment 16:29:56 probably it would be still required to have python2 16:30:06 so that old "ubuntu xxx will only ship python3" 16:30:14 still seems unrealistic to me 16:30:35 it was basically a FYI bunch of #infos 16:30:47 so, any other question, comment doubt about python3? 16:30:48 I hope the release team doesn't ask everyone to port back to Python 2 again--I remember mclasen saying that requiring both Python 2 and Python 3 is a non-starter 16:30:51 distros will keep shipping python 2 for other modules not gnome 16:31:19 mgorse, I also hope that (/me says with his release team hat) 16:31:33 joanie, really? 16:31:49 maybe not on live CDs 16:31:58 in that sense, now I really stopped to understand that "soon ubuntu will only ship python3" 16:32:01 ah ok 16:32:15 so, moving? 16:32:18 but I suspect there's all sorts of downstream stuff that is still python 2 based 16:32:40 not moving yet 16:32:48 two questions 16:33:07 does matthias and others know about the gobject-introspection "patches welcome" thing? 16:33:48 * joanie waits for API 16:33:57 well, when I was talking about g-i with 16:34:01 Colin Walters 16:34:03 on #testable 16:34:07 matthias was around 16:34:17 and paying attention? 16:34:29 he also replied some Colin walter (is glib already python3 compliant) questions 16:34:33 Or maybe that just means that the release team needs to try to find someone to fix that module 16:34:38 so he was paying attention to the conversation 16:34:40 ok 16:34:49 don't know if he realized that "patches are welcome" thing 16:35:03 mgorse, afaik, the one looking at g-i is colin walters 16:35:10 at least he did the last releases of that module 16:35:27 my other question is about the gnome-shell mag example 16:35:45 should we remove it from pyatspi until it is python 3 compatible? 16:35:51 I think we should 16:36:14 well, it is just an example 16:36:22 anyway, don't know/I'm not sure 16:36:22 so it is not critical 16:36:34 and it is not python 3 compatible 16:36:49 and it's not just a matter of simple changes 16:36:55 it's dbusy stuff as well 16:37:12 so the example doesn't work in a python 3 world 16:37:38 so it's a not-important, non-functioning, example that people complain about not being python 3 ready 16:37:50 so why not remove it until it is ready 16:39:13 IMVHO 16:39:24 let the maintainer decide it 16:39:43 mgorse: as the maintainer of pyatspi, what do you think? 16:40:26 I think I'll just remove it from the distribution for now (ie, keep it in git but don't distribute the examples directory) 16:40:41 ok 16:40:55 either that or I could add a comment that it needs Python 2 16:41:11 or both 16:41:21 On the other hand, it provides an example for how to use pyatspi 16:41:33 we could write a new example 16:41:37 that functions in python 3 16:41:48 Having some sort of example would be good 16:41:53 * joanie nods 16:42:14 yeah, probably maitaning it on master, but not distributing it, would be a good middle-term solution 16:42:21 +1 16:42:35 okay then; I'll do that for now 16:42:36 and it would make us officially Python 3 ready 16:42:44 go us 16:42:46 :) 16:43:07 that should probably be infoed 16:43:10 for the minutes 16:44:37 mgorse, could you #info the recent stuff? 16:45:43 #info The pyatspi example is not Python3-ready yet. mgorse will remove it from the distribution for now. 16:46:01 ok thanks 16:46:04 so, moving now? 16:46:08 yeah 16:46:10 thanks 16:46:14 ok 16:46:17 #topic GNOME 3.8 updates 16:46:33 I think that was covered in the previous topic 16:46:48 #info current week (w3) was a GNOME release week 16:47:05 #info specifically 3.7.4 16:47:27 #info just to mention that ATK added new API, versioning tools so apps/libraries could get the ATK version being used 16:47:41 and as joanie said, a lot of stuff was already mentioned on python3 topic 16:47:50 so thats all for me 16:47:54 anyother? 16:48:04 (wants to add something on this topic) 16:48:12 not from me. I just keep on keepin' on 16:50:06 moving on? 16:50:55 taking into account that nobody stepped 16:50:58 ok with moving 16:51:09 #topic W3C updates 16:51:22 #info joseph is not at the meeting, so no update from him 16:51:28 joanie, any update from your side? 16:51:33 nope 16:52:16 ok 16:52:23 #topic Marketing 16:52:24 jjmarin, ? 16:52:48 #info Juanjo is still working in a accessibility (Spanish) article for gnome hispano 16:52:57 API: Do you mind to check it out before send it to the gnome hispano list ? 16:54:08 and well., maybe joanie can practise her Spanish as well :-) 16:54:13 heh 16:54:52 * joanie wonders if API fell asleep 16:55:23 or maybe he has comcast 16:55:25 I'm ok about reviewing it 16:55:36 jjmarin, could you add an action about that? 16:55:45 #action Juanjo will send to API for corrections in the following days 16:56:05 done ! no more from me 16:56:41 anything you want from marketing ? 16:56:54 no from my side 16:57:35 ok, we can move on then 16:57:36 as no one else asked 16:57:40 exactly 16:57:41 :-) 16:57:46 #topic miscellaneous time 16:57:55 anyone want to add something not previously scheduled? 16:58:03 #info For the record, comcast sucks. 16:58:06 done 16:58:08 ;) 16:59:32 Spanish telcom as well (and expensive) :-) 17:01:02 * joanie suggests we close the meeting 17:01:18 yep, seems a good suggestion 17:01:23 so thanks everybody 17:01:26 API: Error: Can't start another meeting, one is in progress. 17:01:28 ups 17:01:30 #endmeeting