1 16:09:32 <API> #startmeeting
   2 16:09:32 <tota11y> Meeting started Thu Jun 20 16:09:32 2013 CET.  The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot.
   3 16:09:32 <tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
   4 16:09:51 <API> #topci GSoC updates
   5 16:09:54 <API> #topic GSoC updates
   6 16:09:59 <API> magpie, clown ?
   7 16:10:23 <clown> who goes first, magpie?  I'm inclined to hand you the conch.
   8 16:11:29 <clown> yes, *if* the caret tracking code works.
   9 16:11:46 <API> clown, why *if*?
  10 16:11:57 <API> I mean
  11 16:12:01 <clown> or, more specifically, we can show that JS can handle caret-moved events.
  12 16:12:04 <API> magpie doesn't need to investigate the freeze
  13 16:12:13 <API> it doesn't matter if the caret tracking code works or not
  14 16:12:32 <clown> API, up to now, the test code has just tested handling focus events.
  15 16:12:56 <clown> Strictly speaking we don't *know* that caret events won't show a problem.
  16 16:13:09 <clown> They probably wont', but it's good to verify that.
  17 16:14:01 <clown> cool magpie.  Good news.
  18 16:14:18 <API> clown, I'm still lost
  19 16:14:20 <joanie> yay! progress!!
  20 16:14:26 <API> so that means that being pessimistic
  21 16:14:38 <API> there is a possibility of finding new freezes once
  22 16:14:42 <clown> #action Joseph to review magpie's latest focus caret tracker code and possible suggest changes.
  23 16:14:43 <joanie> magpie: your name after #action
  24 16:14:43 <API> new stuff get implemented?
  25 16:15:18 <clown> yes, API.  But, it's very unlikely that it will happen.
  26 16:15:23 <joanie> API I think that clown is being "paranoid" just like you and I are.
  27 16:15:26 <clown> yes, I'm pessimistic.
  28 16:15:31 <clown> or paranoid.
  29 16:15:34 <clown> sure.
  30 16:15:37 <API> ok, just wanted to understand the *if*
  31 16:15:41 <joanie> clown: said with finger quotes
  32 16:15:44 <API> thanks for the explanation
  33 16:15:51 <joanie> API and I are similar; just with different stuff
  34 16:15:55 <clown> no problem-o
  35 16:16:32 <joanie> magpie: so you are on schedule?
  36 16:16:56 * clown waits
  37 16:17:19 <clown> oh my.  I have no opinion.
  38 16:17:27 <joanie> magpie: when you have something to say, say it. :)
  39 16:17:36 <API> magpie, not sure if it makes sense a timetabling
  40 16:17:38 <API> yes that
  41 16:17:44 <joanie> unless there is a stipulation that you must blog x-number-of-times
  42 16:17:49 <clown> what is the planet gnome blog for?
  43 16:17:51 <API> as joanie said, probably it would be better a milestone based posts
  44 16:17:58 <API> something like "I solved this => post"
  45 16:18:06 <API> instead of
  46 16:18:07 <clown> I like that API.
  47 16:18:10 * joanie agrees with API
  48 16:18:12 <API> "2 weeks passed => post"
  49 16:18:21 <API> magpie, who are "they"?
  50 16:18:29 <joanie> magpie: if you can find that stated somewhere, please provide me with a link
  51 16:18:32 <clown> what does GSOC require?  Do anyone know?
  52 16:18:42 <joanie> clown: that is what we're trying to ascertain
  53 16:19:14 <joanie> having said that, my understanding is that we are in charge and GSoC is happy if we are happy
  54 16:19:22 <clown> okay.  I'd say *if* GSOC requires timely updates, and there no milestone, simply state the problem you are working on, the current status, and when you think it will be done.
  55 16:19:23 <joanie> and we'll be happy with milestone-based entries
  56 16:19:46 <clown> and, follow that up with milestone results when you have one.
  57 16:19:58 <joanie> magpie: if you could poke around (just a small bit) and see if you can find anything that lists the blogging "requirements"
  58 16:20:01 <joanie> that would be good
  59 16:20:40 <joanie> not now
  60 16:20:44 <joanie> eventually
  61 16:22:10 * API waiting for magpie check
  62 16:22:46 <API> magpie, ok thanks
  63 16:22:49 <API> so anything else?
  64 16:22:52 <API> next topic?
  65 16:23:49 <API> I don't think so, as nobody is raising questions
  66 16:23:50 <API> sooo
  67 16:23:51 <API> moving
  68 16:24:10 <API> #topic GUADEC BoF scheduling
  69 16:24:12 <API> joanie, ?
  70 16:24:25 <joanie> k
  71 16:24:45 <joanie> #info Joanie added our BoF request to the GUADEC planning page
  72 16:24:50 * joanie grabs link
  73 16:25:11 <joanie> https://live.gnome.org/GUADEC/2013/BOFs
  74 16:25:25 <joanie> #info Joanie also emailed the papers committee as per the instructions
  75 16:25:40 <joanie> #info Joanie did this a week ago and has heard nothing back.
  76 16:26:01 <joanie> #info Our plan is to have the BoF on the 6th at the latest or not have it at all.
  77 16:26:04 <joanie> questions?
  78 16:26:50 <joanie> magpie: because I -- and API -- have a bunch to do
  79 16:26:52 <API> magpie, because we foresee people running out of brno after the core days
  80 16:27:13 <API> joanie mentioned herself and me
  81 16:27:22 <API> but probably a lot of people will not be around
  82 16:27:24 <joanie> so you can have a BoF, but the core a11y team members likely will be gone
  83 16:27:26 <API> so long
  84 16:27:43 <joanie> i.e. it will be a single bird
  85 16:27:55 <joanie> or several birds who need answers, etc. (if hacking)
  86 16:27:55 <clown> bird of A feather?
  87 16:28:01 <joanie> and no one to provide the answers
  88 16:28:06 <joanie> because they'll be traveling
  89 16:29:37 <joanie> the plan magpie is that people will come and go
  90 16:29:51 <joanie> i.e. no one needs to be at the a11y bof the full day
  91 16:30:04 <joanie> last year people came and went
  92 16:30:52 <joanie> and we cannot do the 5th (almost certainly) due to GNOME Advisory Board meeting (all day, can't come and go, API and I both have to go)
  93 16:32:00 <API> so after answering all these questions
  94 16:32:02 <API> more questions?
  95 16:32:06 <API> comments, doubts?
  96 16:32:10 <joanie> why is the sky blue?
  97 16:32:18 <joanie> is the sky blue?
  98 16:32:23 <joanie> sorry
  99 16:32:25 * joanie sits down
 100 16:32:26 <clown> why is the sky orange in Star Trek?
 101 16:32:40 * clown lies down.
 102 16:32:54 <joanie> API kicks joanie and clown
 103 16:33:02 * clown whuh?
 104 16:33:10 <joanie> we're being bad minions
 105 16:33:11 <API> clown, because of batman
 106 16:33:26 <clown> ah;, that makes sense API.   Not.
 107 16:33:33 <API> #topic W3C updates
 108 16:33:40 <clown> well, hi there!
 109 16:33:46 <API> clown, your turn oh orange sky master
 110 16:34:25 <clown> #info The WAI-ARIA working group is pushing to get all issues regarding the UAIG document cleaned up, so it can be published as a last call document
 111 16:34:35 <clown> #info the hope is to publish sometime in July
 112 16:35:19 <clown> not going to info this, but I think that's unlikely since it's summer, and getting everyone to commit is difficult.
 113 16:35:33 <clown> my guess is that the document will be published early in the fall.
 114 16:35:44 <clown> or autumn, as they say in Scotland.
 115 16:35:57 <clown> questions?
 116 16:36:02 <API> clown, so I guess that you mention that because there are two options
 117 16:36:09 <API> or a total agrement before holidays
 118 16:36:13 <API> *agreement
 119 16:36:20 <API> or postponing it after holidays
 120 16:37:23 <clown> API, that's part of it.  But, another is that various people in the working group are assigned actions, such as, "provide the correct values to the table in section x of the document".
 121 16:37:39 <clown> similar to our assigning actions to ourselves at these meetings.
 122 16:37:53 <clown> people are unlikely to fulfill those task over the summer (I think).
 123 16:38:30 <API> this is the reason I said "postponing after holidays"
 124 16:38:34 <clown> especially since everything (almost) done at the W3C is voluntary.
 125 16:38:41 <API> anyway
 126 16:38:43 <API> thanks for the update
 127 16:38:48 <API> more qeustions, doubts, comments?
 128 16:38:48 <clown> sure.
 129 16:39:38 * API wonders if that "sure." means that clown has more comments or agreeing with my "thanks for the update"
 130 16:39:58 <clown> s/sure/you're welcome/
 131 16:40:11 <API> clown, ok
 132 16:40:23 <API> #topic Marketing
 133 16:40:24 <API> hmm
 134 16:40:28 <API> jjmarin is not here
 135 16:40:32 <API> marketing is good!
 136 16:40:46 <API> hmm, that was a really bad attempt to be jjmaring
 137 16:40:49 <API> jokes apart
 138 16:40:56 <API> anyone has something to say here?
 139 16:41:21 <API> magpie, well,in the scope of this meetings
 140 16:41:30 <API> marketing actions related with the accessibility effort of GNOME
 141 16:41:33 <API> for example
 142 16:41:49 <API> promote the past friends of gnome
 143 16:41:56 <API> initiative in relation with accessibility
 144 16:42:01 <API> then announce the winner
 145 16:42:12 <API> having material about accessibility
 146 16:42:21 <joanie> magpie: There's a full GNOME marketing team. Juanjo is our team's marketing lead and works with the GNOME Marketing team.
 147 16:42:22 <API> on the annual report, wirte the accessibility "chapter"
 148 16:42:23 <API> etc
 149 16:42:49 <joanie> because one of the messages of GNOME is that we value accessibility
 150 16:43:05 <joanie> GNOME can be used by all users of all abilities all over the world, etc., etc.
 151 16:43:20 <joanie> so we need to be sure that message goes out and gets heard
 152 16:43:29 <joanie> and jjmarin does that :)
 153 16:44:20 <joanie> magpie: on a related note, after your awesome work is completed, jjmarin will work with you to promote it appropriately :)
 154 16:45:11 <API> magpie, more questions?
 155 16:45:26 <joanie> awesome
 156 16:45:29 <joanie> :)
 157 16:45:51 <clown> cool
 158 16:47:03 <API> well, having said so
 159 16:47:05 <API> lets keep moving
 160 16:47:12 <API> #topic miscellaneous time
 161 16:47:25 <API> someone wants to add something (short) not previously scheduled?
 162 16:47:53 <clown> yes.
 163 16:49:08 <joanie> magpie: I think it is.
 164 16:49:10 <joanie> clown: ?
 165 16:49:47 <clown> the only thing I remember is an email (a week ago) that listed two-week blocks of time and tasks.
 166 16:49:58 * clown looks.
 167 16:50:27 <joanie> clown: I think magpie is asking about our opinions, etc. (though I could be wrong)
 168 16:50:43 <joanie> it is magpie's job to be sure she is on schedule more or less
 169 16:50:46 <joanie> :)
 170 16:51:08 <clown> sure, joanie, but that schedule in that email (can't find it), I noted that she was ahead of schedule.
 171 16:51:18 <clown> I noted that in my reply to magpie.
 172 16:52:17 <clown> magpie, do you remember that email?
 173 16:54:36 <clown> anyhow, I remember replying that it looked like you were a week ahead in terms of that schedule.  My guess is, by now, you are "on time".
 174 16:55:15 <joanie> and we have the "next steps" identified?
 175 16:55:55 <clown> yeah, it was in that schedule.
 176 16:56:07 <clown> It listed dates, and tasks.
 177 16:56:17 <clown> I *think* the dates were two week blocks of time.
 178 16:56:38 <clown> "Fix the freeze" was one of the tasks.
 179 16:57:26 <clown> I found the email!
 180 16:58:18 <clown> my reply was Jun 17, and the subject was "Re: Mike Gorse fixed the freeze!"
 181 16:58:30 <clown> it was sent to all the mentors.
 182 16:59:29 <clown> "24 June - 5 July: Solve the “Freeze Problem”*"
 183 17:00:31 <clown> the output of that task is a patch to gnome-shell that is the basic focus tracker code.  That patch should be done by Monday, latest.  Possible sooner.
 184 17:00:37 <API> well people
 185 17:00:43 <API> I think that we can summarize this as
 186 17:00:58 <API> "yes, magpie is not behind schedule and clown has proofs of that"
 187 17:01:01 <API> having said soO
 188 17:01:06 <API> I propose to end the meeting
 189 17:01:09 <joanie> second
 190 17:01:15 <joanie> we have another meeting
 191 17:01:17 <API> after all, we are already over time
 192 17:01:25 <API> clown, thanks for the research
 193 17:01:31 <API> magpie, thanks for the (on schedule) good work
 194 17:01:33 <clown> my pleasure API.
 195 17:01:40 <API> thanks everybody for coming here
 196 17:01:43 <API> #endmeeting