14:37:31 #startmeeting 14:37:31 Meeting started Thu Sep 1 14:37:31 2011 UTC. The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:37:31 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:37:45 #topic Marketing and Fundraising 14:37:51 jjmarin, ? 14:37:55 hi 14:37:55 something new here? 14:38:12 well, bryen pass me the gnome_a11y twitter account 14:38:32 so any suggestion 14:38:32 yay! 14:38:39 will be welcome 14:38:40 :-) 14:39:22 I'm going to ask the US event box master 14:39:47 Well, any time there's something a11y and gnomey to announce, tweet it. You know how to use twitter properly, so I don't think you need suggestions. ;-) 14:39:54 for storing the a11y banners and stand from Bryen 14:40:30 and we need to start to define the goal 14:40:44 for a FoG campaign 14:41:07 So far, I think the candidate for that goal 14:41:24 will be the Performance Evaluation and Improvement 14:41:53 I was thinking about starting a wiki page for wrting 14:42:06 the the a11y porpose 14:42:16 not sure if I have to do 14:42:17 in 14:42:23 https://live.gnome.org/GnomeMarketing 14:42:24 jjmarin, joanie has a draft and in theory I was reviewing it 14:42:39 OK 14:42:45 jjmarin: all a11y team stuff live in live.gnome.org/Accessibility 14:42:47 jjmarin, hmm, probably it would be better to add those under our roadmap wiki 14:42:50 anyway 14:43:02 all a11y marketing stuff live in live.gnome.org/Accessibility/Marketing 14:43:06 after all it is just adding details to one of the entries that we already have on the wiki 14:43:23 I don't know if there are other candidates 14:43:27 as for editing the roadmap.... 14:43:42 from our roadmap 14:43:46 I'd prefer we don't edit that until we have official roadmap changes 14:43:53 in other words..... 14:44:06 I propose that if you would like to start planning the FoG on the wiki 14:44:17 you do so on live.gnome.org/Accessibility/Marketing/FoG 14:44:23 ok 14:44:25 please 14:44:27 and thank you 14:44:28 :-) 14:45:06 jjmarin, ok, could you try to summarize all these stuff in pretty #info? 14:45:10 for minutes sake? 14:45:12 but do you think we should evaluate more goals for a FoG campaign 14:45:57 # Juanjo will start planning the a11y FoG campaign in live.gnome.org/Accessibility/Marketing/FoG 14:46:20 jjmarin: use #action 14:46:31 for action items 14:46:32 oh !!! 14:46:44 and #info for things which go in the minutes (like the summary) 14:46:51 :-) 14:46:56 #action Juanjo will start planning the a11y FoG campaign in live.gnome.org/Accessibility/Marketing/FoG 14:47:51 API, so you will review the performance text 14:47:54 clown: If memory serves me, you'll have a proposal for jjmarin to include regarding gs-mag caret and focus tracking? 14:48:03 yes 14:48:14 joanie, yes. 14:48:17 but, we can include this as well 14:48:24 awesome 14:48:44 sorry, but remind me of the dealine again. I was going to work on it this week, but there were other fires to put out. 14:48:49 so far peformance + gs-mag caret and focus tracking 14:48:51 #action Team members who want something funded need to get proposals to jjmarin 14:48:55 "deadline" 14:49:05 jjmarin, well, yes 14:49:10 joanie: thanks ! 14:49:11 clown: yesterday ;-) 14:50:04 well, anything else on this point? 14:50:27 jjmarin, ? 14:50:29 do we have any idea of the money for each of these goals ? 14:50:48 jjmarin, this is one of the reasons they want a specific proposal 14:50:51 I mean, we should provide what we want to do and how much we need 14:51:06 some felt that a project like that 14:51:12 would be too ambitious 14:51:22 in order to check if that should be splitted or something 14:52:03 clown: probably goes without saying given what jjmarin and API just said, but if your proposal could include a figure, that would be good I suspect. :-) 14:52:47 * clown1 university's network is really flakey today. ... 14:52:57 what did I miss? 14:53:12 clown: probably goes without saying given what jjmarin and API just said, but if your proposal could include a figure, that would be good I suspect. :-) 14:53:12 * clown1 (~clown@205.211.169.2) has joined #a11y-meeting 14:53:12 * clown1 university's network is really flakey today. ... 14:53:12 what did I miss? 14:53:43 Well, I think I don't have more to say 14:53:43 thanks API. 14:54:10 jjmarin, ok so lets move 14:54:20 #topic GNOME 3.2 progress 14:54:21 * clown1 wired network is completely down. reports are some construction crew cut the fibre optic ... 14:54:32 at this moment I guess that the bit topic here is talk about 14:54:35 pygobject madness 14:54:36 "call before you dig" 14:54:39 joanie, jhernandez ? 14:54:47 something to report? 14:54:49 jhernandez: you first? 14:55:27 * joanie wonders if nacho got the release off 14:55:32 joanie: you first! 14:55:33 :P 14:55:46 hah 14:55:49 * clown1 herding cats ... 14:56:01 joanie, nacho? 14:56:02 #info Joanie committed Orca's introspection port in time for 3.1.90. 14:56:25 congratulations, joanie! 14:56:26 #info Orca now depends on pygobject 3.1.90 due to recent fixes in that module. 14:56:51 #info John Palmieri then failed to do a release of pygobject 2.90.3. 14:57:18 #info The release team pinged Joanie, also pinged John, and in theory Nacho did a pygobject 2.90.3 release. 14:57:52 #info Joanie is well aware of a number of bugs and issues resulting from the introspection work. Some are in Orca, some in Gtk+, some remain to be found. 14:58:00 joanie: from #release-team 14:58:02 the missing piece was pygobject, and it arrived during the meeting 14:58:02 yeah 14:58:22 #info Joanie is both optimistic and fearful of getting things out in time for shipping GNOME 3.2, but she'll do her very best. 14:58:57 #info Piñeiro reported from #release-team that the release of pygobject has been done. 14:58:59 (done) 14:59:03 API thanks for checking!! 14:59:08 and in fact 14:59:09 http://ftp.gnome.org/pub/gnome/sources/pygobject/2.90/ 14:59:23 API I was going to look while jhernandez did his report 14:59:26 the files are thre 14:59:28 but then jhernandez told me to go first 14:59:30 there 14:59:58 jhernandez: your turn 15:00:10 so, Accerciser is in the same state as Orca is 15:00:42 we have some known issues regarding pygobject/gtk/whatever 15:00:45 jhernandez: #info is your friend :-P 15:01:26 #info jhernandez accomplished accerciser's introspection port for 2.1.90 15:01:46 s/2/3/ 15:01:49 :] 15:02:29 #info there are some known issues regarding pygobject/gtk/whatever and I'm working on them 15:02:49 jhernandez: known issues are going to kill us 15:02:56 joanie: :P 15:03:06 * clown unknown issues just stab you in the back. 15:03:18 clown: for sure! 15:03:19 xD 15:03:22 so, I'm done 15:03:37 jhernandez: congrats on your release! 15:03:48 joanie: congrats for yours too!! 15:03:54 ;) 15:03:56 (ours) 15:03:57 ;-) 15:04:01 :] 15:05:07 well, so in summary all the modules using old gtk bindings were ported, right? 15:05:29 API all a11y modules 15:05:33 to our knowledge 15:05:54 everyone else, who knows? 15:06:28 API: AFAIK, yes 15:07:06 well, good news 15:07:18 so the only "old stuff" still around is gconf 15:07:22 right? 15:07:36 API:I'm not sure "everything" is true. 15:07:42 But maybe everything within gnome. 15:07:48 I'm working on fixes for LDTP and mago 15:07:51 * joanie doesn't have any gcof 15:07:54 or gconf 15:08:03 although I guess that with the gconf-dbus background that is less important 15:08:12 API:I'm not sure "everything" is true. 15:08:15 I don't understand 15:08:23 what it is "everything"? 15:08:35 accerciser uses gconf for only to store its preferences, but I'm working on the gsettings port 15:09:34 jhernandez: and we still need to revisit, merge your gsettings work for Orca ;-) 15:09:56 API:I think I just repeated what joanie said, in a less clear way ;-). 15:10:30 bnitz, ah ok 15:10:33 * joanie grins 15:10:54 speaking Piñeiro takes years of practice bnitz :-P 15:10:59 eventually you'll master it. 15:11:03 * joanie runs and hides 15:11:10 joanie: you're right! ;) 15:11:24 ok, so using #infor 15:11:48 #info a11y modules are already ported to new pygobject, as far as the a11y team knows 15:12:04 #info work to migrate to gsettings is really near to be finished 15:12:13 ok, something else about gnome 3.2 15:12:17 I will try to ask clown 15:12:27 hoping that he will be connected long enough 15:12:32 API, go ahead try... 15:12:46 it seems that some of your gs-mag thing will not be ready for 3.2... 15:13:10 that appears to be correct. no go ahead on committing any of the patches. 15:13:23 * joanie frowns 15:13:35 clown, I was reviewing some of your bugs 15:13:37 clown: nice try on getting them through 15:13:45 and it seems that it is related to some of the work moved to clutter 15:13:55 and due being on API frozen mode now 15:14:07 is this the reason for the "no go ahead" or there is something more? 15:14:20 #info Joanie notes that, for the record, Joseph did tons of work and responded in a timely fashion to feedback provided to him. 15:14:30 thanks, joanie. 15:14:46 I don't know of anything more, API. 15:14:56 clown: thank YOU. Some things are simply beyond our control :-/ 15:15:10 I responded to criticisms, made changes to code, and supplied new patches. 15:15:24 but, there was always "one more thing" to improve. 15:15:38 that is, the reviewer asked for another change or changes. 15:15:39 joanie, well, this is the point "tons of work" 15:15:41 I know clown 15:15:48 and time just went past the deadline. 15:16:08 clown, yes thats true, it seems that they always ask your for the finished version 15:16:16 sometimes they are more conservative than me ; 15:16:17 ) 15:16:21 although... in one case, there was not a full review of my patch -- that's the inverse video, brightness, and contrast effects. 15:17:24 but that was the one moved to clutter, right? 15:18:17 well, as time passes and so on, joanie provided a #info with some conclusions, but there is a little lack of context 15:18:25 clown, could you summarize all this in a pretty #info 15:18:26 yes, about two weeks ago, when it looked like GS would review it, the suggestion was to move parts of it to clutter. 15:18:42 API, info's comin up... 15:19:12 #info Joseph's feature additions to gs-mag will not be ready for 3.2 15:19:38 #info these include a gnome-control-center zoom options dialog for the current gs-mag preferences. 15:20:02 #info inverse video, brightness, and contrast effects for gs-mag. 15:20:29 #info new gsettings for those three screen effects (gsettings-desktop-schemas). 15:21:02 #info near the 3.2 deadline, the suggestion was to move the effects to up stream to clutter 15:21:29 #info clutter developer is okay with that, but doesn't want to add the classes util October time frame. 15:21:48 #info summary: gs-mag feature improvements missed the 3.2 deadline. 15:21:56 I think that captures it. 15:22:47 so... done 15:22:57 thanks clown 15:23:07 3.4 here we come! :-) 15:23:34 anyone else has something to add about 3.2? 15:23:46 Remind: dear members of the a11y team, we have some release notes for 3.2 first :-) 15:23:54 http://live.gnome.org/Accessibility/ReleaseNotes/ThreePointTwo 15:23:54 :-) 15:24:22 there is any kind of #reminder thing in meetbot? 15:24:30 I dunno 15:24:33 I shall find out 15:24:38 #help 15:24:45 hmmm 15:24:50 jjmarin: later 15:24:59 ok, as workaround 15:25:14 #info jjmarin reminds to all a11y members the need to fill the release notes 15:25:23 5 minutes till the end 15:25:29 #topic miscellaneous time 15:25:31 jjmarin, help just assigns a person to provide some aid (not sure what that entails). 15:26:03 #help (alias #halp) 15:26:03 Add a HELP item to the minutes. Confusingly, this does not give supybot help. See #commands. 15:26:05 #commands 15:26:05 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #rejected #restrictlogs #save #startmeeting #topic #unchair #undo #unlurk 15:26:29 guys, focus 15:26:30 ;) 15:26:34 I have something for misc time 15:26:39 #focus 15:26:40 miscellaneous time is not so miscellaneous 15:26:44 a11y stuff please ;) 15:26:58 mgorse: what's the status on the check a11y work? 15:27:16 "check a11y work" ? 15:27:28 org.a11y.Status.IsEnabled 15:27:37 can be read but not written 15:27:40 etc. 15:27:50 ok 15:27:52 in other words, we need a freedesktop solution to check if a11y is enabled 15:28:13 not a gnome key versus a kde environment var versus whatever xfce does 15:28:29 yeah, right now it can be read but not written 15:28:56 except that it might not work right if a11y is toggled until the session is restarted; it works by checking whether the accessibility bus is active 15:28:57 mgorse: so dumb question. If it "cannot be written" does that mean no one can set it? 15:29:05 "org.freedesktop.a11y.Status.Enabled"? 15:29:21 yeah 15:29:32 yeah to which? 15:29:53 a11y can't be toggled that way yet 15:30:23 what process(es) can toggle it? 15:30:41 gsettings for GNOME 15:31:28 mgorse: do we have an estimated time for full implementation so that we have a reliable, freedesktop-wide solution we can all use? 15:32:43 If people really want that in for 3.2, then I can try to work on it, although I presume I need permission from the release team 15:33:11 Oh, I'd love it for 3.2 because then we can get it used by xfce 15:33:24 not that we'd say that as a justification. ;-) 15:34:06 * joanie wonders if our fearless RT member could get that change blessed 15:34:39 well, it seems just a little addition 15:34:44 that nobody is using 15:34:51 I mean that it would be different if 15:35:04 we were talking about something that all people are using and we 15:35:12 were planning to modigy somehow 15:35:23 but that just my humble opinion ;) 15:35:29 :-) 15:35:43 mgorse: could you do a patch on a bug so we can ask for blessing? 15:35:48 mgorse, you could try to send again that mail asking if it makes sense 15:35:48 please 15:35:54 well, makes sense 15:35:57 it makes sense 15:36:08 I mean if people think that can be added before 3.2 15:36:13 I'd also need to test that it works to enable/disable a11y at runtime, which is the main reason I didn't commit it with the other change. I ought to have done this sooner; it just slipped my mind / never made it onto my to-do list 15:36:16 if nobody ask I could try to ping people on IRC 15:36:46 API: For a feature freeze break, should I have a patch first, and then email release-team? 15:36:46 API ping people == ? 15:37:34 mgorse, not sure if this is a requirement but it would make things easier 15:37:48 you could also try to send the mail first, to at least check 15:37:55 if they are receptive 15:38:04 joanie, next release team meeting is planed in one month 15:38:10 ah 15:38:11 Regardless, working on a patch won't hurt, since we'll need it anyway, whether it goes into 3.2 or not 15:38:20 +1 mgorse 15:38:20 ping people means: hey, have you seen mgorse mail? what do you think? 15:38:28 API I know what ping means 15:38:30 so getting the bless via IRC instead ml 15:38:33 I meant what people and why 15:39:02 joanie, well, people==release team folks, why==next meeting in a month more or less 15:39:10 anyway, mgorse you rock thanks!!! 15:39:18 API thanks for the clarification 15:39:29 well in fact 15:39:31 - next meeting: September 15th, 18UTC 15:39:49 that's only two weeks away. mgorse how much work is involved? 15:40:35 Oh wow 3.1.91 is this coming Monday?! 15:40:45 zomg really? 15:40:46 crap 15:40:55 that means I don't get to sleep again 15:41:02 frick 15:41:22 jhernandez: you see that ^^ ? 15:41:26 yepo 15:41:28 :S 15:41:31 Monday is labour day. North Amercian holiday, at least. 15:41:32 mgorse, joanie 15:41:32 It would have been two weeks from .90 with the original .90 date, so I guess the release team delayed .90 but not .91 15:41:33 .91 is typically code freeze 15:41:34 https://live.gnome.org/ThreePointOne 15:42:05 an .92 hard code freeze 15:42:17 phew 15:42:18 15:42:18 Sep 19 15:42:18 15:42:18 GNOME 3.1.92 rc tarballs due 15:42:18 15:42:20 Hard Code Freeze: no source code changes can be made without approval from the release-team. Translation and documentation can continue. 15:43:04 #info For the record, Joanie would like it known that she knows exactly where the schedule happens to be but is sleep deprived and has a migraine due to getting the introspection work done. :-P 15:43:47 oke 15 minutes over time 15:43:51 lets finish this 15:43:58 thanks people for coming here 15:44:01 #endmeeting