1 15:05:31 <API> #startmeeting
   2 15:05:31 <tota11y> Meeting started Thu Dec 29 15:05:31 2011 UTC.  The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot.
   3 15:05:31 <tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
   4 15:06:01 <API> #topic FOSDEM Update
   5 15:06:22 <API> #info API send a talk proposal to talk about accessibility in general (not only GNOME)
   6 15:06:33 <API> #info Mario made the same, to talk about webkitgtk a11y
   7 15:06:44 <API> #info both waiting for answers
   8 15:06:47 <API> any other?
   9 15:08:03 <API> well, looking here:
  10 15:08:05 <API> https://lists.fosdem.org/pipermail/crossdesktop-devroom/2011-December/thread.html
  11 15:08:15 <API> I don't see any other accessibility related
  12 15:08:24 <API> talk on crossdesktop-devroom
  13 15:08:28 <API> not sure in other meetings
  14 15:08:49 <API> sorry
  15 15:08:52 <API> in other devrooms
  16 15:09:12 <API> questions, doubts?
  17 15:11:04 <API> I will conclude that no
  18 15:11:05 <API> so moving
  19 15:11:12 <API> #topic hackfest update
  20 15:11:47 <API> #info finally we got the confirmation that travel committee will cover hotel+flights
  21 15:12:34 <API> #info about the hotel, we are going to use the same procedure that in the webkitgtk hackfest
  22 15:12:57 <heidi> I hadn't heard about the hackfest and haven't seen any link to date information in the minutes. Can someone fill me in briefly?
  23 15:13:21 <API> #info Igalia will book the hotel Avenida, so once the people knew the exact days contact us
  24 15:13:31 <API> heidi, https://live.gnome.org/Accessibility/Hackfests/ATK2012
  25 15:13:46 <heidi> API, thanks!
  26 15:13:47 <API> in summary, we had a atk/at-spi2 hackfest on may
  27 15:13:50 <API> this is the follow up
  28 15:14:29 <API> #info last week we finally made the public announcement
  29 15:14:31 <API> https://mail.gnome.org/archives/gnome-accessibility-devel/2011-December/msg00014.html
  30 15:14:39 <API> so, questions doubts?
  31 15:15:29 <joanie> so I guess we need to fill in our arrival and departure times
  32 15:15:40 <joanie> for hotel booking
  33 15:16:03 <API> yes, we will use the table at the hackfest page as base
  34 15:16:19 <API> although we will contact people to final confirmation
  35 15:16:39 <API> anyway, this is what we did on previous hackfest, as we think that it is easier
  36 15:16:48 <API> if people prefer other way
  37 15:16:57 <API> this is the time to debate it
  38 15:17:05 <joanie> I think most people will prefer we make the reservations for them
  39 15:18:14 <jjmarin> yes, confirm their attendance and book for them seems a good idea
  40 15:19:32 <API> I also suppose that it is easier for foundation, as in the end is just one reimbursement
  41 15:20:00 <API> anyway, taking into account that not all hackfest attendees are there
  42 15:20:11 <API> al those #info require a custom mail
  43 15:20:28 <API> #action API will send a informative mail to the current confirmed attendees
  44 15:20:34 <API> and having said so
  45 15:20:37 <API> questions, doubts?
  46 15:22:41 <API> it seems that no
  47 15:22:44 <API> so lets move
  48 15:23:00 <API> #topic Marketing and Fundraising
  49 15:23:02 <API> jjmarin, ?
  50 15:23:09 <jjmarin> yes
  51 15:23:18 <jjmarin> #info The accessibilty FoG campaign was launched the 16th december. Unfortunately, I haven't data about how is going on so far.
  52 15:25:03 <jjmarin> #info API and Bryen made posts in planet gnome, and Alan Bell and Pendulum will do another one in Planet Ubuntu
  53 15:26:08 <jjmarin> #info Also the announce have been published in www.gnome.org and social media
  54 15:26:52 <jjmarin> #info There are problems with the donation progress bar, but I wasn't informed about the current status
  55 15:27:24 <jjmarin> and I think that's all, suggestions or questions about the campaign ?
  56 15:27:35 <API> jjmarin, where is supposed to be published that progress bar?
  57 15:27:48 <API> at the fog webpage?
  58 15:28:12 <jjmarin> yes. In the past also was in planet gnome and in www.gnome.org
  59 15:29:26 <jjmarin> but they have technical problems to put in order. I hope at least to bring some data from the gnome paypal account
  60 15:29:37 <jjmarin> for the next meeting
  61 15:29:48 <API> and finally, as there is a progress bar
  62 15:29:59 <API> it is supposed that this campaign has a deadline, right?
  63 15:30:17 <API> I mean that it will be there until the proposed money is got
  64 15:30:29 <API> but I suppose that it will have also a time limit
  65 15:30:30 <API> right?
  66 15:31:53 <jjmarin> yes. But it wasn't set by now. The current money to get is 20,000 US
  67 15:32:21 <jjmarin> but it can be bigger if we get a good donation these days
  68 15:32:38 <API> jjmarin, ok thanks
  69 15:32:43 <API> I don't have more quesitons
  70 15:32:51 <API> questions
  71 15:33:00 <API> others?
  72 15:35:59 <API> people is silent, so I assume that no
  73 15:36:01 <API> lets move
  74 15:36:12 <API> #topic Keynote speaker about accessibility for the next GUADEC
  75 15:36:14 <API> jjmarin, ?
  76 15:36:19 <jjmarin> #idea I think is good idea to propose a keynote speaker for the next GUADEC from the accessibilty world.
  77 15:36:37 <jjmarin> #idea Someone who can give a interesting talk about the topic that can help to promote accessibility inside the GNOME community.
  78 15:36:48 <jjmarin> what do you think ?
  79 15:37:02 <jjmarin> do you know a good candidate ?
  80 15:37:42 <joanie> #info Joanie thinks that keynote speakers are typically chosen because they are seen as awesome/important/whatever by the entire community.
  81 15:38:28 <API> about that joanie info
  82 15:38:31 <joanie> #info Joanie thinks, therefore, that unless you can get someone like Stevie Wonder this will not be a good -- or doable -- idea
  83 15:38:32 <API> thats true usually
  84 15:38:49 <API> but, sometimes you get a keynote from people out GNOME
  85 15:39:04 <API> in that aspect, although Richard Stallman is a relevant figure
  86 15:39:22 <API> I wouldn't say that is the most involved person on GNOME
  87 15:39:34 <jjmarin> #info In fact, the keynote speaker are chosen by recommendation from people from the community
  88 15:39:37 <API> is more a GNU guy watching GNOME and giving advices
  89 15:39:49 <API> anyway, about my opinion
  90 15:40:15 <API> #info API thinks that if there is only one keynote, it wouldn't worth to have a specific accessibility keynote
  91 15:40:41 <API> #info API in the same way, we usually have talks about accessibility approved, so anyone could go there
  92 15:40:55 <bnitz1> /me is thinking of the kid whose father submitted a patch shortly before the father died (ALS?)
  93 15:41:19 <jjmarin> #info there is a keynote speaker every core day
  94 15:41:34 <API> #info if there is just one keynote, and it is about accessibility, we are in danger of keep being seen as a "different thing"
  95 15:42:03 <API> jjmarin, how many core days this year?
  96 15:43:19 <jjmarin> four days July 26 to 29
  97 15:43:26 <API> jjmarin, ok thanks
  98 15:43:47 <jjmarin> according to http://www.guadec.org/
  99 15:44:14 <jjmarin> Some example of keynote speakers http://guadec.expectnation.com/public/content/keynotes
 100 15:45:47 <API> as people suddenly become silent
 101 15:45:52 <bnitz1> #info Adrian Hands is the person I was thinking of, suffered from ALS but submitted a patch for a 9 year old GNOME bug via morse code https://bugzilla.gnome.org/show_bug.cgi?id=78514#c19
 102 15:45:52 <tota11y> 04Bug 78514: enhancement, Low, ---, eog-maint, RESOLVED FIXED, copy item in edit menu
 103 15:45:53 <API> #info API is not sure
 104 15:47:26 <joanie> It's an intersting idea bnitz1. But keynote speakers need to be good speakers (imho). So we'd need to find out of his son is.
 105 15:47:29 <API> bnitz1, thanks for the link
 106 15:48:08 <bnitz1> Yes, just thought I'd mention it.  I don't know Ian Hands at all.
 107 15:48:14 * joanie nods
 108 15:48:33 <jjmarin> bnitz1: yes, the story is good, but we don't know how good the son is as a speaker
 109 15:49:13 <API> anyway, thats just partially answer question 2) from jjmarin about which speaker
 110 15:49:23 <API> what do you think about questions 1) ?
 111 15:49:31 <API> <jjmarin> #idea I think is good idea to propose a keynote speaker for the next GUADEC from the accessibilty world.
 112 15:49:39 <API> all agrees that it is a good idea?
 113 15:50:09 <jjmarin> (I restrain to agree with me)
 114 15:50:10 <joanie> I'm not convinced it is, no.
 115 15:50:19 <bnitz1> I agree.
 116 15:50:39 <joanie> I would need to know more about who is proposed, what the days are, who the other keynotes are, etc.
 117 15:52:01 <heidi> I think that it would be good to have an accessibility speaker, as long as they are engaging and interesting.
 118 15:52:33 <heidi> Having an accessibility speaker just to raise awareness might backfire if the speaker, ummm, isn't a positive representative.
 119 15:53:19 <API> well, lets say then that there are still some info to get
 120 15:53:33 <API> and that we can't just answer question 1) without knowing more about 2)
 121 15:53:40 <jjmarin> I guess there should be a good speaker about accessibility. I can do some research
 122 15:53:40 <API> as the meeting is finishing
 123 15:53:52 <API> yes
 124 15:54:03 <API> I mean, lets say that we need more research before
 125 15:54:08 <joanie> jjmarin: quiet research without approaching any possible speakers
 126 15:54:08 <jjmarin> #action Juanjo will look for candidates as keynote speakers
 127 15:54:14 <jjmarin> yes
 128 15:54:19 <joanie> thank you :)
 129 15:54:25 <jjmarin> of course
 130 15:54:37 <API> jjmarin, joanie had other doubts, so could you research for the other doubts too?
 131 15:54:46 <jjmarin> joanie: are you a good speaker ;-)
 132 15:55:00 <jjmarin> yes
 133 15:55:05 <API> jjmarin, ok thanks
 134 15:55:05 <joanie> nice try ;)
 135 15:55:13 <API> so as the meeting if finishing
 136 15:55:19 <API> lets go for the favourite section
 137 15:55:25 <API> #topic Miscellaneous time
 138 15:55:37 <API> something not included on the agenda that you want to mention?
 139 15:57:07 <jjmarin> the end of the year is coming ;-)
 140 15:57:29 <API> really?
 141 15:57:33 <API> I didn't notice
 142 15:58:48 <jjmarin> hehe
 143 16:00:19 <API> well, no one is using misc time in a really useful way
 144 16:00:22 <API> sorry jjmarin  ;)
 145 16:00:26 <API> so lets conclude the meeting
 146 16:00:29 <API> #endmeeting