1 16:01:16 <API> #startmeeting
   2 16:01:16 <tota11y> Meeting started Thu Feb  6 16:01:16 2014 CET.  The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot.
   3 16:01:16 <tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
   4 16:01:26 <API> #topic 5 minutes of margin; waiting for people
   5 16:01:41 <API> hmmm topic didn't change
   6 16:01:46 * clown waves
   7 16:01:47 <API> I don't have ops power today
   8 16:01:52 <mgorse> API: tota11y doesn't have ops. Not sure what should be done ab out that
   9 16:01:52 <aday> hi all
  10 16:02:00 <clown> he aday
  11 16:02:04 <clown> or, hi, rather.
  12 16:02:15 <jjmarin> hi aday !
  13 16:02:15 <API> probably joanie knows better
  14 16:02:27 <API> in any case, for minutes sake, I think that #topic still works
  15 16:02:32 <clown> no one has authority today?
  16 16:02:46 <magpie> anarchy!
  17 16:02:50 <API> clown, no, today is no-authority day
  18 16:03:09 <clown> API, does that mean you are *not* our fearless leader?
  19 16:03:11 <API> btw, taking into account that aday and clown are already here, although agenda put 3.12 as third item
  20 16:03:12 <clown> anymore?
  21 16:03:23 * clown looks
  22 16:03:24 <API> we can put as first item
  23 16:03:28 <API> clown, is a de-cup
  24 16:03:45 <clown> https://wiki.gnome.org/Accessibility/Meetings
  25 16:03:49 <clown> ?
  26 16:04:04 <clown> okay with me, API
  27 16:04:39 <API> clown, I mean coup detat
  28 16:04:53 <API> I think that English stole that from French
  29 16:04:54 <clown> well, yes, that makes more sense.
  30 16:05:01 <API> Im not too used to french
  31 16:05:08 <API> in any case 5 minutes now
  32 16:05:09 <clown> c'est vrai.
  33 16:05:14 <API> so we can start the real meeting
  34 16:05:28 <API> #topic Progress towards 3.12
  35 16:05:30 <jjmarin> fossdem syndrome, speak in French
  36 16:05:50 <clown> en Français?  Pas moi.
  37 16:05:53 <API> clown, aday, magpie , I think that you can start with the settings+magnifier focus tracking thing
  38 16:05:59 <API> but please, in english
  39 16:06:01 <clown> okay API
  40 16:06:05 <magpie> #info Crosshairs Are Broken https://bugzilla.gnome.org/show_bug.cgi?id=723709 (This bug is caused by https://git.gnome.org/browse/gnome-shell/commit/js/ui/magnifier.js?id=193f872ebedfb1fb1107a428b595855812f42153 ) I already have a fix for this waiting on review
  41 16:06:05 <tota11y> 04Bug 723709: critical, Normal, ---, gnome-shell-maint, UNCONFIRMED, Crosshairs Are Broken
  42 16:06:26 <clown> Intereseting, but let's talk about that later, magpie.
  43 16:06:49 <magpie> #info at fosdem aday florian and I all met up to talk about adding preferences to the control center
  44 16:07:20 <clown> #info A couple of days ago, aday and magpie approached me in #a11y about adding said preferences.
  45 16:07:30 <magpie> #info but there was some ambiguity about what was vital for the next release and how it should be done so that the preferences are clear to users
  46 16:08:02 <magpie> #info Magdalen explained there are still some bugs to iron out with the focus tracking so it's important people can turn it off and on again
  47 16:08:09 <aday> i'm confident that i can come up with an updated design for the preferences
  48 16:08:11 <magpie> Magnifier: Focus Tracking should focus "objects" more complete https://bugzilla.gnome.org/show_bug.cgi?id=720716
  49 16:08:11 <magpie> Magnifier: Focus Tracking flipps on left screen edge in some cases https://bugzilla.gnome.org/show_bug.cgi?id=720715
  50 16:08:11 <magpie> Magnifier: Focus Tracking should jump more smooth to the next focus point. https://bugzilla.gnome.org/show_bug.cgi?id=720723
  51 16:08:11 <tota11y> 04Bug 720716: normal, Normal, ---, gnome-shell-maint, UNCONFIRMED, Magnifier: Focus Tracking should focus "objects" more complete
  52 16:08:12 <tota11y> 04Bug 720715: normal, Normal, ---, gnome-shell-maint, UNCONFIRMED, Magnifier: Focus Tracking flipps on left screen edge in some cases
  53 16:08:13 <tota11y> 04Bug 720723: normal, Normal, ---, gnome-shell-maint, UNCONFIRMED, Magnifier: Focus Tracking should jump more smooth to the next focus point.
  54 16:08:39 <magpie> #info Allan is confident he can come up with a design to update the preferences
  55 16:08:50 <clown> \o/
  56 16:09:01 <aday> will maybe be tomorrow or the beginning of next week, and will mostly be a reshuffle of what's already there, with the addition of some extra tracking options
  57 16:09:19 <magpie> info Allan thinks will maybe be tomorrow or the beginning of next week, and will mostly be a reshuffle of what's already there, with the addition of some extra tracking options
  58 16:09:28 <magpie> opps forgot the #
  59 16:09:35 <API> please, could you?
  60 16:09:37 * aday doesn't know how to talk robot
  61 16:09:39 <magpie> #info Allan thinks will maybe be tomorrow or the beginning of next week, and will mostly be a reshuffle of what's already there, with the addition of some extra tracking options
  62 16:09:40 <API> would make minutes easier
  63 16:09:50 <magpie> s'ok aday I'll translate
  64 16:10:00 <aday> magpie, i think i've got it :)
  65 16:10:01 <API> fwiw
  66 16:10:24 <API> #info API notes that users also asked about how to turn on/off or change the mode on the mailing lists
  67 16:10:38 <clown> aday, when you say "adding extra tracking options", is the starting point magpie's suggestions in bugzilla 708452?
  68 16:10:46 * clown looks up url
  69 16:10:57 <clown> https://bugzilla.gnome.org/show_bug.cgi?id=708452#c7
  70 16:10:57 <tota11y> 04Bug 708452: normal, Normal, ---, control-center-maint, UNCONFIRMED, Focus and Caret Tracking: Include preferences
  71 16:10:58 <magpie> #info there was also some discussion about whether or not the colour and tinting preferences should be in the zoom or not
  72 16:11:15 <clown> whoops, that's not point at the right thing.
  73 16:11:31 <aday> i think for the time being the best thing we can do is rename "zoom" to "zoom & color" or "zoom & tint"
  74 16:11:35 <magpie> #info that discussion was informed by https://bugzilla.gnome.org/show_bug.cgi?id=596386
  75 16:11:35 <tota11y> 04Bug 596386: normal, Normal, ---, gnome-shell-maint, UNCONFIRMED, Dyslexia support screen tinter
  76 16:11:53 <API> well, and now starting some small discussion without infos
  77 16:11:59 <API> imho,
  78 16:12:04 <magpie> https://bugzilla.gnome.org/show_bug.cgi?id=676814
  79 16:12:04 <tota11y> 04Bug 676814: normal, Normal, ---, gnome-shell-maint, UNCONFIRMED, make 'zoom' independent of color-related shader use
  80 16:12:11 <API> has more priority adding preferences to the focus/caret tracking
  81 16:12:14 <API> that to the tinting
  82 16:12:23 <API> in several cases
  83 16:12:32 <API> a magnifier without tracking is useless
  84 16:12:40 <clown> Sorry, I'm  totally lost regarding which single aspect of the magnifier we are talking about.
  85 16:12:41 <API> obviously it would be awesome to have both
  86 16:12:55 <API> there are two things that right now
  87 16:13:07 <API> you can't control with a preference UI
  88 16:13:11 <API> one is the focus/caret tracking
  89 16:13:34 <API> and the other is the tinting (so changing the brightness/etc from each color component)
  90 16:13:52 <API> additionally magpie is mentioning this bug:
  91 16:13:57 <API> https://bugzilla.gnome.org/show_bug.cgi?id=676814
  92 16:13:57 <tota11y> 04Bug 676814: normal, Normal, ---, gnome-shell-maint, UNCONFIRMED, make 'zoom' independent of color-related shader use
  93 16:14:02 <clown> IMHO, the focus/caret tracking preference UI has priority.
  94 16:14:02 <API> as I mentioned this monday
  95 16:14:10 <API> that bug is in summary
  96 16:14:23 <API> cleaning all the magnifier preferences
  97 16:14:30 <API> because as some have noted
  98 16:14:48 <API> sometimes you want to changes colors without changing the zoom, so somehow are independent
  99 16:14:50 <API> but imho
 100 16:14:55 <API> that is a big amount of work
 101 16:15:01 <API> and probably it would be better this
 102 16:15:17 <magpie> #info Magdalen spoke to drag01 about perhaps making the colour changes in g-s firslty so that the colour/tinting can be activates independently of the magnifier in there
 103 16:15:25 <API> 3.12: add a new tab for focus/caret preferences (if time permits also tintint)
 104 16:15:36 <API> 3.X (x>12): clean all the magnifier preferences
 105 16:15:46 <magpie> #info this would mean that the preferences could come later on
 106 16:15:55 <API> well, my approach is somewhat conservative
 107 16:16:01 <API> but is just a suggestion
 108 16:16:15 <API> doing all that for 3.12 would depend on the people available for this
 109 16:16:18 <magpie> aday, do you have any questions so far?
 110 16:17:37 <aday> magpie, API, i think we're in agreement. at this point in the cycle my instinct is to go for the low hanging fruit
 111 16:17:58 <API> ok
 112 16:18:00 <magpie> API, that's true, but if aday can do it I can help. We can prioritise the tracking without necessarily ruling out the colour changes depends how hard aday thinksit will be
 113 16:18:05 <API> so next question is
 114 16:18:10 <API> aday will work on design
 115 16:18:20 <API> who will work on the patches for gnome-control-center?
 116 16:18:56 <clown> that would involve the code freeze, correct?
 117 16:19:14 <clown> which is Mar 17?
 118 16:19:43 <aday> clown, ui freeze is in a couple of weeks, i think
 119 16:19:45 <clown> I mean, working on the code for g-c-c.  It would have to be done by Mar 17, right?
 120 16:19:49 <magpie> #info Magdalen can do help aday on the control center patches as long as she knows what the design is because Magdalen is a bit lost with the design end of things
 121 16:19:51 <API> well ui freeze
 122 16:20:08 <API> that is (for now) Feb 17
 123 16:20:10 <clown> aday, I'm think the UI can be frozen while the code that runs it is still in development.
 124 16:20:12 <magpie> 17th feb
 125 16:20:19 <clown> *I'm thinking
 126 16:20:23 <magpie> #info the freeze is on 17th Feb
 127 16:20:30 <API> clown, but take into account that most all of this is UI
 128 16:20:39 <aday> magpie, but i think it will be delayed by a week
 129 16:20:55 <magpie> oh useful
 130 16:21:10 <clown> API, well, you asked who will work on the patches for gnome-control-center?  I thought you meant the code.
 131 16:21:26 <API> aday, it is not clear yet, I will talk about that when I summarize the wayland status
 132 16:21:44 <API> clown, yeah, but that code is about ui
 133 16:21:53 <API> in any case
 134 16:21:54 <aday> API, oh ok. i thought it was fairly certain
 135 16:22:00 <clown> that is, changes to gnome-control-center = UI patches + code patches.
 136 16:22:12 <API> aday, well, due FOSDEM
 137 16:22:16 <API> some replies arrive late
 138 16:22:19 <clown> so the UI freeze (Feb 17) applies to the code for the UI as well?
 139 16:22:25 <API> but today andre also mentioned it
 140 16:22:28 <API> in any case
 141 16:22:32 <API> is Feb17 or a week later
 142 16:22:38 <API> so is not a lot of time in any case
 143 16:22:47 <magpie> #info the schedule is here https://wiki.gnome.org/Schedule
 144 16:22:59 <API> (any case twice in the same sentence, I'm the new Shakespeare)
 145 16:23:07 <clown> hee hee
 146 16:23:11 <API> so
 147 16:23:16 <API> as we have an agreement
 148 16:23:21 <API> and some assignments
 149 16:23:26 <andre_> UI freeze means that the UI is not expected to change anymore. So depends on what your code change does. ;)
 150 16:23:27 <API> is there anything else to discuss here?
 151 16:23:45 <clown> andre_  makes the UI "work" as expected :-)
 152 16:24:10 <magpie> #info Magdalen thinks the most important thing is to allow people to turn each of the tracking on and off independently because people will have different requirements but suspects clown might have some more thoughts to share on this topic
 153 16:24:13 <API> yeah, andre_ explained it better that me
 154 16:24:16 <clown> well, I'll repeat my last question, API
 155 16:24:27 <clown> so the UI freeze (Feb 17) applies to the code for the UI as well?
 156 16:25:03 <API> as andre_ said, if it modifies the UI, then yes, it applies
 157 16:25:11 <API> so we are talking here about the UI freeze
 158 16:25:39 <clown> my perspective is the reacts to the users selection of buttons, radio buttons, etc, and properly sets/unsets the relevant gsettings.
 159 16:25:58 <clown> the code doesn't change the UI, it just, well, engages it.
 160 16:26:10 <API> clown, in other words
 161 16:26:18 <API> if you make an screenshot
 162 16:26:23 <API> before and after any change
 163 16:26:30 <API> after UI freeze, it needs to be the same
 164 16:26:39 <API> and note that we are talking here about the UI of the settings dialog
 165 16:26:50 <clown> a screenshot of the contorl center dialog? Or of the whole screen?
 166 16:26:56 <API> control-center-dialog
 167 16:27:33 <magpie> clown I hadn't realised that. I was thinking it would be waiting on design.
 168 16:27:34 <clown> yes, that's pretty much what I mean.  The appearance of that dialog is fixed, but the code is being developed/debugged/tested to make that UI work properly.
 169 16:27:45 <clown> The code doesn't change the appearnce of that UI.
 170 16:28:00 <clown> magpie, it does wait on the design.
 171 16:28:15 <API> clown, right now there isn't any button (or checkbutoon or widget)
 172 16:28:16 <clown> No point in wriing a handler for a radio button that doesn't exist yet...
 173 16:28:17 <magpie> #info the code for preferences does not depend on the design it just engages the design.
 174 16:28:20 <API> to set on or off the tracking
 175 16:28:31 <API> so if you add that button
 176 16:28:33 <magpie> true that clown.
 177 16:28:33 <API> the ui changes
 178 16:28:43 <clown> magpie has made suggestions for the UI.  I have htoughts, and aday might have time to fully develop the UI.
 179 16:28:58 <clown> So, I think the UI is close, but I may be biased.
 180 16:29:03 <API> in any case, I think that this discussion is going in circles
 181 16:29:10 <clown> sorry, I'll shut up.
 182 16:29:18 <API> in summary, this is affected by the UI freeze
 183 16:29:33 <magpie> #idea including mouse tracking now the focus caret are there it might be good to have a way to turn mouse tracking off and still use magnifier too
 184 16:29:58 <API> magpie, there are already preferences for that
 185 16:30:01 <clown> magpie, that would probaly make the machine unusable.
 186 16:30:02 <API> as aday said
 187 16:30:08 <magpie> API not to turn it off
 188 16:30:18 <API> at this point we should go for the priorities
 189 16:30:33 <API> imho
 190 16:30:35 <magpie> before it was taken for granted the mousetracking was always needed when the magnifier was on
 191 16:30:57 <magpie> so it;s not in the preferences to turn that off and continue to use magnification
 192 16:31:06 <clown> because turning off mouse tracking means the mouse could go completely out of view.  It becomes next to impossible to find it again.
 193 16:31:18 <clown> it's that way on purpose.
 194 16:31:43 <magpie> there's a way to keep the mouse pointer in view i think
 195 16:31:50 <clown> this is beyond the scope of the meeting, though.
 196 16:31:58 <magpie> but the cross hairs still do need to be restored
 197 16:32:01 <API> I agree with clown
 198 16:32:09 <API> magpie, that is a bug, and not part of this topic
 199 16:32:17 <clown> API, can you summarize where we are with respect to focus tracking control centre work?
 200 16:32:18 <API> so (and again)
 201 16:32:32 <aday> i'll circulate some design ideas as soon as possible - we can discuss it then
 202 16:32:39 <API> clown, the summary is mostly on those bugs
 203 16:32:55 <API> aday, ok thank you
 204 16:33:02 * clown thanks aday.
 205 16:33:11 <API> so as we have an agreement, can we move to next topic?
 206 16:33:12 <magpie> ok aday, thanks has this been useful or do you have some further questions?
 207 16:33:43 <aday> magpie, nothing right now thanks. i'm sure i'll have plenty of questions when i get stuck into it
 208 16:33:58 <API> aday, ok
 209 16:34:06 <clown> #info aday will circulate some design ideas as soon as possible - to be discussed further.
 210 16:34:29 <magpie> ok thanks for your help with this it is really appreciated!
 211 16:34:40 <API> +1
 212 16:34:55 <API> taking into account that we are already over half of the meeting time
 213 16:35:01 <API> I will move to next topic
 214 16:35:19 <API> #topic Wayland
 215 16:35:50 <API> #info mclasen sent a email to release-team suggesting to move GNOME release one week
 216 16:36:21 <API> #info this change is related with the next release of Wayland, so GNOME 3.12 could use the last stable one
 217 16:36:52 <API> #info during the same week, API sent a email asking about what should be the default for GNOME 3.12
 218 16:37:13 <API> #info as the wiki still seems to suggest that would be Wayland, but for what he knew, it was not mature enough
 219 16:37:26 <API> #info consensus was that X will be still default for 3.12
 220 16:37:48 <API> #info this is good news for accessibility, because as you know, there are still some feature not ported to Wayland
 221 16:38:13 <mgorse> so I guess we're not the only people who have work to do
 222 16:38:26 <API> #info due this (X being the default) some people of the release-team thinks that it doesn't worth to change GNOME schedule due Wayland
 223 16:38:53 <magpie> API have you identified what features those are?
 224 16:38:59 <API> #info so right now it is not clear if the schedule will change or not
 225 16:39:01 <API> done
 226 16:39:13 <API> magpie, yes, we identified them
 227 16:39:20 <API> we have a wiki listing them
 228 16:39:25 <magpie> link?
 229 16:39:42 * API looking
 230 16:39:53 <API> https://wiki.gnome.org/Initiatives/Wayland/Gaps#Accessibility
 231 16:40:00 <API> https://wiki.gnome.org/Accessibility/Wayland
 232 16:40:00 <magpie> thanks
 233 16:40:18 <API> mgorse, yes, we are not the only ones with work to do, but still we have a lot to do
 234 16:40:21 <API> having said so
 235 16:40:23 <API> questions?
 236 16:41:21 <magpie> nope
 237 16:42:00 <API> well, mostly all of this was informative
 238 16:42:22 <API> andre_ you usually don't come to the a11y meetings
 239 16:42:26 <API> (thanks for coming btw)
 240 16:42:35 <API> but is your presence related to this wayland thing?
 241 16:42:43 <andre_> yeah. I just lurk. It's the only thing I'm really good in! ;)
 242 16:42:52 <andre_> nope :)
 243 16:42:56 * clown looks anxiously over his shoulder.
 244 16:43:08 <magpie> the other side clown!
 245 16:43:30 <API> ok, so as people doesn't have questions
 246 16:43:32 * magpie thinks andre_ is also good at bugzilla postings
 247 16:43:39 <API> lets move to next point
 248 16:43:50 <API> #topic W3C updates
 249 16:43:54 <API> clown?
 250 16:43:56 * clown collects his thoughts
 251 16:44:24 <clown> #info The ARIA specifcations are very nearly at the next stage of publication, namely "Proposed Recommendation".
 252 16:45:01 <clown> #info The next step is to have the W3C members' official representative vote on approval of the documents.
 253 16:45:26 <clown> #info I anticipate that they will be approved (I have inside information that Igalia will approve.)
 254 16:45:55 <clown> #info Sometime in the next week or so the proposed recommendation version of the spec will be published.
 255 16:46:08 <clown> #info I will annouce that on gnome-a11y list.
 256 16:46:14 <clown> done, questions?
 257 16:46:35 <API> hmm, I was hopoing a kind of summary of what happened on Toronto two weeks ago
 258 16:46:38 <API> *hoping
 259 16:46:50 <clown> oh.  Lots.  Hmmmm
 260 16:46:57 * clown wonders how to summarize
 261 16:47:15 <clown> I could dig up the urls to the meeting minutes.
 262 16:47:22 <clown> would that be useful.
 263 16:47:24 <clown> ?
 264 16:48:12 <API> well, if you don't have anything else ;)
 265 16:48:27 <clown> I'll try for some general summary of what happened.
 266 16:48:47 <clown> #info The  ARIA working group met in Toronto for three days two weeks ago.
 267 16:49:16 <clown> #info  They went over the (long) list of outstanding issues and actions for version 1.1.
 268 16:49:43 <clown> #info They pared it down to the highest priority items.
 269 16:50:07 <clown> #info Work will begin on those items after the documents are published as proposed recommendation.
 270 16:50:24 <clown> #info more info can be found in the meeting mintues.
 271 16:50:28 * clown looks up urls.
 272 16:52:29 * API thinks that clown got lost on the wide internet
 273 16:52:34 <clown> alas, I can't seem to find them.  I will keep looking and you can move on, unlesss there are questions.
 274 16:52:47 <magpie> nope
 275 16:52:52 * clown just got lost in www.w3c.org space.
 276 16:53:30 <API> clown, ok dont worry
 277 16:53:34 <API> if you find them
 278 16:53:45 <API> send us a email, so we can include it on this meeting minutes
 279 16:53:54 <clown> sure, API
 280 16:54:24 <API> and as sands of time are running low
 281 16:54:28 <API> Im moving to next topic
 282 16:54:37 <API> #topic Marketing
 283 16:54:38 <API> jjmarin, ?
 284 16:54:47 <Javido> Hi, are these specifications will be published today ? http://lists.w3.org/Archives/Public/w3c-wai-ig/2014JanMar/0025.html
 285 16:55:02 <jjmarin> #info Juanjo is working in updating the Wikipedia ATK and AT-SPI entries. I have draft, I will send the maintainers, API and mgorse, today for some corrections improvements (API already did it, but again just in case to add some more).
 286 16:55:54 <jjmarin> #info after the corrections, Juanjo will start the process to update the Wikipedia.
 287 16:56:12 <jjmarin> I can send to more people, if any of you feel like that :-)
 288 16:56:14 <API> Javido, taking into account previous comment from clown:
 289 16:56:21 <API> <clown> #info Sometime in the next week or so the proposed recommendation version of the spec will be published.
 290 16:56:42 * API send his apologies to jjmarin, I was replying a question
 291 16:56:54 <API> jjmarin, ok, as soon as you send your email I will review it
 292 16:57:01 <jjmarin> Don't worry :-)
 293 16:57:14 <jjmarin> Finally,
 294 16:57:22 <jjmarin> #info Juanjo will write a summary of the accessibility work done for the GNOME annual report
 295 16:58:10 <jjmarin> maybe there infor are more like a action, I hope it doesn't matter too much
 296 16:58:21 <jjmarin> these info I mean
 297 16:58:35 <API> is ok
 298 16:58:36 <jjmarin> sorry is broken :-)
 299 16:58:37 <API> don't worry
 300 16:58:46 <API> so, people
 301 16:58:53 <API> more questions, doubts on this potic?
 302 16:58:56 <API> *topic
 303 16:59:19 <jjmarin> jjmarin English is contagious :-)
 304 16:59:35 <magpie> #action  Juanjo will write a summary of the accessibility work done for the GNOME annual report
 305 16:59:40 <magpie> there you go
 306 16:59:47 <jjmarin> ok :-)
 307 17:00:34 <API> ok
 308 17:00:38 <API> and  nobody is asking questions
 309 17:00:43 <API> so jjmarin thank you
 310 17:00:50 <API> #topic miscellaneous time
 311 17:00:55 <API> so before closing the meeting
 312 17:01:14 <API> anyone has something (short) to say not included on the agenda?
 313 17:01:25 <clown> API, I have the urls for the aria f2f meeting minutes, but I'm not sure they are public.
 314 17:01:33 <clown> Shall I paste them in her?
 315 17:01:35 <clown> *here?
 316 17:01:42 <API> yes go on
 317 17:01:45 <API> please
 318 17:02:01 <clown> #info ARIA face-to-face meeting day 1:  http://www.w3.org/2014/01/23-aria-minutes.html
 319 17:02:16 <clown> #info ARIA f2f day 2:  http://www.w3.org/2014/01/24-aria-minutes.html
 320 17:02:29 <clown> #info ARIA f2f day 3:  http://www.w3.org/2014/01/25-aria-minutes.html
 321 17:02:31 <clown> done.
 322 17:02:35 <magpie> #info Crosshairs Are Broken https://bugzilla.gnome.org/show_bug.cgi?id=723709 (This bug is caused by https://git.gnome.org/browse/gnome-shell/commit/js/ui/magnifier.js?id=193f872ebedfb1fb1107a428b595855812f42153 ) I already have a fix for this waiting on review
 323 17:02:35 <magpie> can someone do the honours
 324 17:02:35 <tota11y> 04Bug 723709: critical, Normal, ---, gnome-shell-maint, UNCONFIRMED, Crosshairs Are Broken
 325 17:03:04 <magpie> that's all from me for now. g2g thanks everyone.
 326 17:03:30 <API> magpie, if you are asking if we can do the honours
 327 17:03:37 <API> we could review the patch
 328 17:03:39 <API> but as we are not
 329 17:03:49 <API> gnome-shell maintainers I don't think that that
 330 17:03:56 <API> would be enough to get a commit-bless
 331 17:04:09 <magpie> ok just that giovanni was saying it doesn't need to be fixed for a few month
 332 17:04:29 <jjmarin> clown: those urls are public :-)
 333 17:04:31 <magpie> so it might be useful to have someone from a11y as an extra review
 334 17:05:04 <clown> thanks for checking jjmarin
 335 17:05:11 <API> magpie, ok, will try to take a look later
 336 17:05:14 <magpie> to speed things along whilst the crosshairs do not work and there is a fix written already it should not need to take so long as two months imho
 337 17:05:26 <clown> and, thanks, aday, for looking into those focus/caret tracking preferences.
 338 17:05:39 <aday> clown, thank me when i've done it :)
 339 17:05:56 <API> is a preventive thanks
 340 17:06:00 <clown> aday, or perhaps curse you ?  :-) nah.
 341 17:06:01 <magpie> yeah thanks aday, clown, API for your help with the tracking
 342 17:06:17 <API> in any case, we are already over time, and as we are just saying to each other how awesome we are
 343 17:06:22 <API> I will close the meeting
 344 17:06:26 <aday> clown, you can do that too ;)
 345 17:06:29 <clown> okay, aday, I'll amend my thanks:  Thanks for getting the ball rolling again.
 346 17:06:34 <clown> :-)
 347 17:06:37 <API> you can continue with the awesomeness at the IRC
 348 17:06:47 <API> #endmeeting