14:35:55 <API> #startmeeting
14:35:55 <tota11y> Meeting started Thu Oct  6 14:35:55 2011 UTC.  The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:35:55 <tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:36:04 <API> btw, joanie will not be here
14:36:07 * clown wants a new agenda — one for Oct 6.
14:36:17 <API> and somehow, that explains that missed agenda
14:36:18 <API> heh :P
14:36:31 <clown> glad to be of service ;-)
14:36:36 <API> it seems that clown volunteered himself for next agenda ;)
14:36:50 * clown wha? who?  where?
14:36:51 <API> anyway, most of the topics to talk about would be the same
14:37:04 <API> so lets use last agenda as a template
14:37:23 <API> #topic Hackfest planning
14:37:40 <API> #info API started to talk with WebkitGTK organizers
14:37:51 <API> #info main concern is how much the attendance will grow
14:38:07 <API> #info right now it is estimated about 16-17 people for WebkitGTK alone
14:38:20 <API> #info a hackfest with more people is more than a hackfest, a summit
14:38:35 <API> #action API will keep talking with them, and bring a conclusion
14:38:43 <API> questions, thoughts?
14:38:59 <API> btw, I will made a global ping
14:39:16 <API> aleiva, API clown fregl mgorse Pendulum SeaJay tota11y meeting started
14:39:16 <API> ;)
14:39:23 <aleiva> :)
14:39:40 <aleiva> what was the estimated date?
14:39:49 <API> 29nov-5Dec
14:39:59 <aleiva> when you say is more than ban hacjfest you mean logistic problems?
14:40:06 <API> just before spanish Constitution holidays
14:40:15 <aleiva> how many people is going to attend from our side?
14:40:33 <API> more or less the same that atk hackfest
14:40:37 <API> although likely
14:40:38 <API> less
14:40:42 <aleiva> around 10
14:41:11 <API> as the idea is being more focused on at-spi2, and hack, and not so much about checking the current state of ATK and AT-SPI2
14:41:40 <aleiva> ok looks good
14:42:02 <aleiva> when you will have a decission about the date?
14:42:04 <mgorse> There's some overlap, though, at least--a few people who are coming to the hackfest would be coming anyway
14:42:11 <API> but as I said, still need to confirm if a joined hackfest is viable
14:42:30 <API> aleiva, I will try to have an answer asap
14:42:33 <mgorse> although I get their concern that they have as many people as they can handle
14:42:51 <API> as is the answer is yes, flight tickets needs to be checked soon
14:43:07 <aleiva> yup
14:43:56 <API> so, anyother question, thought here?
14:44:07 <aleiva> so, ok, holding on until API management
14:44:58 <API> ok, lets move then
14:45:10 <API> #topic marketing and fundraising
14:45:16 <API> well, jjmarin is not here
14:45:20 <API> so
14:45:35 <API> #info jjmarin was not present, we will ask him on next meeting
14:45:50 <API> any other want to share something about this point?
14:46:22 <aleiva> umh
14:46:44 <aleiva> jhernandez adds his blog into p.g.o.
14:47:08 <aleiva> he is going to blog about his work into a11y
14:47:32 <aleiva> i thin we need to blog and communicate more :)
14:47:35 <API> good
14:47:37 <API> yes,
14:47:47 <API> I have pending a summer-summary post ...
14:47:49 <aleiva> I dont usually do
14:47:52 <API> Im lazy in that kind of things
14:47:55 <aleiva> also ;)
14:48:00 <aleiva> me too
14:48:13 <aleiva> nothing more to add
14:48:14 <API> #info jhernandez was included on p.g.o, he plans to blog
14:48:21 <API> well, jhernandez post would be good
14:48:29 <API> some people feel that accerciser is dead
14:48:36 <API> and nobody is taking care of it
14:48:40 <jhernandez|eee> ¿?
14:48:42 <jhernandez|eee> ok
14:48:44 <API> it would be good to correct that
14:48:51 <jhernandez|eee> I'll post a little about it
14:49:05 <API> ie: about the gobject-introspection madness ;)
14:49:10 <aleiva> hehe
14:49:24 <API> ok, anything else in this point?
14:49:36 <aleiva> nope
14:49:42 <API> ok, well
14:49:48 <API> #topic GNOME 3.4 planning
14:49:55 <API> #info feature proposal is opened
14:50:07 <API> #info it would be good to propose some kind of a11y-related feature
14:50:17 <API> #action a11y team should start to think about it
14:50:19 * clown notes that he uses accerciser all the time to "test" aria implementations.
14:50:33 <API> btw, at this point feature
14:50:38 <API> is something "visible"
14:50:39 <aleiva> i was thinking today in that
14:50:43 <API> and "marketable"
14:51:08 <aleiva> we can accelerate focus tracking into gs mag
14:51:12 <API> ie: brighness contrast control on gnome-shell
14:51:16 <aleiva> accelerate the development
14:51:23 <API> yes, this is another example
14:51:33 <clown> yes, API, aleiva
14:51:42 <API> although release-team in this case will ask for "plans"
14:51:47 <API> in the case of clown is easy
14:52:01 <API> as he made a lot of job, and it is "finishing" the details
14:52:09 * API using "" too much
14:52:23 <API> so in summary, think about features
14:52:32 <API> clown, any update from that brightness/contrast stuff?
14:53:00 <clown> API, I have been researching various calcuclations for brightness and contrast...
14:53:30 <clown> and am close to claming that the algorithms used by gnome-mag, which I copied into clutter, are correct.
14:54:03 <clown> I will be posting my findings to the bug in bugzilla
14:54:04 <API> anyway, I wonder why they are asking for so many academic research for that ...
14:54:14 <clown> ask them :-)
14:54:17 <API> not sure if they ask so much in other places
14:54:27 <API> anyway, not complaining
14:54:39 <API> clown, anyway, targetting 3.4 seems sensible, right?
14:54:50 <clown> they aren't sure that the caculcations are correct, and want justification for it.
14:54:59 <clown> 3.4?  yes.
14:55:19 <clown> one other thing to promote for 3.4 — UI for controlling the magnifier settings.
14:55:57 <clown> my zoom options dialog for gnome-control-center was committed a few weeks back, but it is disabled by defautl.
14:56:17 <clown> there, the issue is (still) " the UI need work".
14:56:18 <API> disabled ?
14:56:22 <API> the zoom or the dialog?
14:56:26 <clown> the dialog
14:56:32 <aleiva> hehe that is the hard part convince gs guys
14:56:41 <API> can the users enable it?
14:57:13 <clown> if you look at the "Seeing" tab in the Universal Access panel there ought to be a "zoom options…" button, but it's nowhere to be found.
14:57:31 <clown> the only way to enable it is to go into the glade file, and make that button visible and active.
14:57:37 <clown> can "users" do that?
14:57:45 <API> well, no
14:57:51 <clown> right.
14:57:59 <clown> I was being rhetorical.
14:58:10 <API> ok, thanks for the summary,
14:58:11 <API> hmm
14:58:20 <API> pretty #info, please?
14:58:27 <clown> want some info's?
14:58:33 <clown> right...
14:59:23 <clown> #info for 3.4, for the magnifier, desirable to push for (1) brightness and contrast effects, (2) focus tracking, and (3) zoom options preferences dialog
14:59:56 <clown> #info wrt to (1), Joseph is investigating various brightness and contrast calculations to justify the use of the algorithms in the code he wrote.
15:00:16 <clown> #info writ (2), Joseph needs to start on that (and needs to find the time).
15:00:41 <API> ok, thanks
15:00:47 <clown> #info wrt (3), the zoom options code is committed, but the triggering button is disabled and invisible.
15:01:06 <API> people, anything else in this "gnome 3.4 point"
15:01:07 <clown> #info the ui people want refinements to the zoom options UI .
15:01:10 <clown> done.
15:01:25 * API sorry :P
15:01:35 * clown no problem.
15:02:10 <API> ok, well, lets move, and with something related
15:02:18 <API> #topic Quarterly reports
15:02:40 <API> #info mail asking Q2 reports was sent
15:02:50 <API> #info still not sure about specific deadline
15:03:02 <API> #info a11y-team also need to write their reports
15:03:07 <API> questions., thoughts?
15:03:59 <clown> I missed the email — was it sent to the a11y list?
15:04:16 <API> hmm, no, I think that was sent yesterday
15:04:21 <API> to desktop-devel or something
15:04:27 <API> was a general mail to all teams
15:04:31 <API> but good point
15:04:41 <API> #action API will send a reminder to a11y list
15:06:13 <API> silence everywhere ....
15:06:24 <API> well, lets move then with the hidden agenda
15:06:25 <API> :P
15:06:37 <API> #topic GNOME 3.2 postmorten
15:06:48 <API> well, we have an ISO to test GNOME 3.2
15:06:52 <API> jhernandez, thanks
15:06:57 <API> or should I say
15:07:01 <API> jhernandez|eee, thanks
15:07:08 <jhernandez|eee> :]
15:07:10 <API> but, have someone tested it ?
15:07:21 <clown> where is it?
15:07:25 <API> how good is the a11y integration/interaction?
15:08:05 <jhernandez|eee> API: I tested a little bit
15:08:26 <jhernandez|eee> and, it seems that all is working ok
15:08:40 <jhernandez|eee> but
15:08:51 <jhernandez|eee> maybe I should do
15:09:03 <jhernandez|eee> "more performance tests"
15:09:06 <jhernandez|eee> :]
15:09:17 <API> #info there is a ISO to test GNOME 3.2
15:09:37 <API> #info it would be good if some people test integration, interaction, tools and performance
15:09:42 <clown> where is it? (is there an echo in here?)
15:09:47 <jhernandez|eee> http://www.gnome.org/getting-gnome/
15:09:58 <clown> thanks, jhernandez|eee  :-)
15:10:49 <jhernandez|eee> well, about the GNOME 3.2
15:11:13 <jhernandez|eee> in the iso, firefox a11y isn't working
15:11:53 <API> jhernandez|eee, for a know reason?
15:11:58 <jhernandez|eee> like in my jhbuild environment since some time ago
15:11:58 <API> or requires investigation?
15:12:06 <jhernandez|eee> API: it requires investigation
15:12:47 <mgorse> My guess would be that it still wants the gconf key or an environment variable to be set
15:12:51 <jhernandez|eee> I lost firefox a11y in my 3.2 jhbuild env, and I asked about it, but, it was like the problem was only with my dev environment
15:13:03 <jhernandez|eee> :S
15:13:20 <aleiva> no, I reproduced it in my system
15:13:26 <aleiva> we'll provide some "bug"
15:13:35 <aleiva> and talk with ff guys
15:13:44 <jhernandez|eee> mgorse: I tested with the gconf key, with ACCESSIBILIY=1 thing and in more many ways
15:14:00 <mgorse> oh. interesting
15:14:23 <jhernandez|eee> and, still no firefox a11y, at least for me
15:14:59 <jhernandez|eee> and, in the gnome 3.2 images, it's the same, but, I hadn't time to investigate more
15:15:14 <API> strange,
15:15:19 <API> fwiw
15:15:21 <jhernandez|eee> API: +1
15:15:22 <jhernandez|eee> :}
15:15:25 <API> it works with oneiric
15:15:35 <API> and in theory is more gnome3 alike
15:15:49 <API> but summarizing it:
15:16:02 <API> #info firefox a11y is not working on the GNOME 3.2 ISO
15:16:23 <API> someone wants to add any other comment, thought about GNOME 3.2?
15:16:29 <API> postmorten conclusions and so on
15:19:04 <API> ...
15:19:11 <API> well, it seems that no
15:19:14 * clown crickets.
15:19:18 <jhernandez|eee> #info jhernandez will make some investigations about this issue, but, more peeople should do that aswell
15:19:26 <API> ;)
15:19:35 <jhernandez|eee> sorry, connection issues ... :S
15:19:41 <API> I said "some people" that it is plural ;)
15:19:46 <API> so lets move
15:19:53 <API> #topic miscellaneous time
15:20:00 <API> so, here we are
15:20:16 <API> anything not included on the inexistent agenda?
15:20:22 <jhernandez|eee> xDDD
15:20:31 <clown> lol
15:20:55 <clown> I have a question:
15:21:35 <clown> the place where I work, the IDRC, has a position available, and I was asked to post it in some relevant gnome mailing list.  is it okay to post it to gnome-a11y?
15:21:48 <clown> or is there a better list?
15:22:40 * clown crickets.
15:23:05 <mgorse> Is the position accessibility-related?
15:23:16 <clown> yes.  accessibility programmer.
15:23:27 <clown> not necessarly, gnome progamming though.
15:23:28 <API> well, this is a good question, but not sure
15:23:32 <jhernandez|eee> i think gnome-a11y is ok, addingly you can tweet or post about it
15:23:41 <API> recently started a effort to list GNOME companies
15:23:52 <API> but it is more the other side
15:23:58 <API> but I agree with jhernandez|eee
15:24:06 <API> I don't see any harm to send a mail like that
15:24:21 <clown> okay, I'll send it out in the next couple of days.
15:24:37 <clown> thanks.
15:26:07 <jhernandez|eee> I have another question/petition
15:27:03 <jhernandez|eee> since I lost last meeting, did you talked about dasher?
15:27:39 * clown wonders if the minutes ever were published.
15:27:58 <jhernandez|eee> clown: +1
15:28:18 <API> ah
15:28:25 <API> yes, we were talking about dasher
15:28:29 <jhernandez|eee> ok
15:28:42 <jhernandez|eee> I can wait for the log
15:28:46 <API> but not sure if in the meeting or during this week
15:28:53 <API> ah yes
15:29:04 <jhernandez|eee> (if someone is planning on to publish it)
15:29:07 <jhernandez|eee> :P
15:29:07 <API> well, on previous meeting joanie mentioned but we
15:29:16 <API> didn't have time to talk too much about it
15:29:18 <API> in summary
15:29:32 <API> we want to get dasher being again a "blessed" module
15:29:47 <API> so first we need to check how it works with GNOME 3.x
15:29:53 <API> missing stuff and so on
15:29:58 <API> joanie was testing it a little
15:30:13 <API> she found that some documentation was outdated
15:30:25 <API> ie: it is not working unless you launch it in a specific way
15:30:30 <API> Pendulum gave joanie the hing
15:30:35 <API> the hint I mean
15:30:40 <API> but it is not documented
15:31:08 <API> and btw, someone sent a patch in order to migrate dasher from cspi to libatspi
15:31:10 <API> but not tested
15:31:27 <API> not sure how useful is a patch not tested, but at least there is something there
15:31:35 <API> jhernandez|eee, and this is what we have right now about dasher
15:31:53 <API> well, over meeting time
15:31:55 <jhernandez|eee> ok
15:32:00 <clown> one more thing...
15:32:03 <clown> sorry.
15:32:04 <API> so, any other (quick) question ?
15:32:08 <API> shoot
15:32:23 <clown> just noticed this in our calendar.
15:32:27 <clown> apparently there is a "Cloud4All Kickoff Meeting in Madrid" on Nov 3.
15:32:44 <clown> thought people nearby might be interested.
15:33:06 <API> cloud4all?
15:33:12 <clown> alas, I don't know anything more than that — I could find out if any are interested.
15:33:26 <API> well, in the same sense
15:33:27 <clown> API, cloud4all is part of the GPII.
15:33:33 <API> at november there is
15:33:36 <API> http://tifloinnova.once.es/index.cfm
15:33:51 <API> a meeting organized by once and others, about a11y stuff, also in madrid
15:33:56 <API> nov 18-20
15:34:18 <API> clown, GPII?
15:34:27 <clown> http://gpii.net/
15:34:34 <API> clown, thanks
15:34:48 <clown> Global public inclusive infrastructure
15:35:04 <API> interesting, I will read that page
15:35:14 <API> and now, 5 minutes over meeting time
15:35:15 <API> ;)
15:35:17 <API> anything else?
15:35:26 <clown> I'll shut up now.
15:35:32 <API> ok,
15:35:33 <API> lets finish
15:35:36 <API> #endmeeting