Attachment '20120105_log.txt'

Download

   1 15:05:25 <API> #startmeeting
   2 15:05:25 <tota11y> Meeting started Thu Jan  5 15:05:25 2012 UTC.  The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot.
   3 15:05:25 <tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
   4 15:05:31 <API> #topic Hackfest update
   5 15:05:50 <API> #info People were notified about the hotel room and that Igalia will do a group reservation
   6 15:06:10 <API> #info DBUS developer contacted by Benjamin Otte confirmed that he is not coming
   7 15:06:41 <API> #info after the meeting I will talk with Company about that, although it will be unlikely to find a backup
   8 15:06:53 <mgorse> Is that Simon?
   9 15:07:01 * API checking the name
  10 15:07:25 <API> mgorse, yes, was Simon
  11 15:07:37 <API> did you already talk with him in the past?
  12 15:07:50 <mgorse> no; just remember Ben saying that he might contact him
  13 15:07:56 <mgorse> or not about the hackfest anyway
  14 15:08:57 <API> mgorse, well, Benjamin contacted him when Ryan confirmed his non-presence
  15 15:09:10 <API> and as I said, Simon also confirmed his non-presence
  16 15:10:52 <API> anyway
  17 15:10:59 <API> questions, doubts about the hackfest?
  18 15:11:25 <API> #action API will talk with Benjamin about DBUS developer involvement (unlikely to find a backup at this moment)
  19 15:12:34 <API> a lot of silence, so I guess that no
  20 15:12:39 <API> #topic Marketing and fundraising
  21 15:12:42 <API> jjmarin?
  22 15:12:48 <jjmarin> yep
  23 15:12:57 <jjmarin> #info It looks like we've gotten a fairly weak response for the FoG campaign (less than $2K)
  24 15:13:52 <jjmarin> #info Marketing is trying to fix this: install the progress bar and more articles in media
  25 15:16:00 <jjmarin> #info Bryen proposed to the marketing team to nominate GNOME a11y to the computerworld award  http://cwhonors.org/nominations/
  26 15:16:08 <API> I think that I already asked you privately, but in order to be public
  27 15:16:19 <API> there is any way to know how "quick" was previous FoG?
  28 15:16:24 <API> that sysadmin FoG
  29 15:16:31 <API> in order to compare
  30 15:16:42 <jjmarin> in one day they did $1K
  31 15:16:42 * API wonders if he is interrumpting jjmaring
  32 15:17:03 <jjmarin> no interrupting :-)
  33 15:17:22 <API> ok, anyway, as I said
  34 15:17:31 <clown> the current FoG compaign is about 2 weeks in comparison?
  35 15:17:33 <API> probably starting that in typical holiday season
  36 15:17:40 <API> affected it
  37 15:17:43 <clown> good point, API
  38 15:17:54 <jjmarin> We are trying to re-launching
  39 15:18:19 <jjmarin> this time with the progress bar and maybe a new testimonial
  40 15:18:48 <jjmarin> and I think is all I remember that is new :-)
  41 15:19:13 <jjmarin> questions, suggestions ?
  42 15:20:36 <jjmarin> tic tac
  43 15:20:46 <jjmarin> :-)
  44 15:21:24 <API> well, it seems that there is no questions ;)
  45 15:21:29 <API> but good work
  46 15:21:38 <API> lets see what happens in the following months
  47 15:21:47 <API> jjmarin, can I move to next topic?
  48 15:21:57 <jjmarin> thanks, of course
  49 15:22:31 <API> well, this was becoming a quick meeting
  50 15:22:32 <API> as
  51 15:22:38 <API> #topic miscellaneous meeting
  52 15:22:46 <API> I will be one starting
  53 15:23:00 <API> #info as we have some features proposed to 3.4
  54 15:23:14 <API> #info instead of waiting a release team meeting to "how that feature is going"
  55 15:23:25 <API> #info probably it would be good to check on the #a11y-meetings
  56 15:23:39 <API> #info not on each meeting, but in some of them
  57 15:23:59 <API> and that was my contribution to miscellaneous time
  58 15:24:19 * API realizes that topic is miscellaneous *meeting* , ups
  59 15:24:25 <API> so, Im done
  60 15:24:39 <API> anyone wants to say anything not scheduled on the agenda?
  61 15:26:29 * clown hears crickets.
  62 15:27:01 <clown> when is the next release team meeting API?
  63 15:27:34 <API> clown, we don't have a fixed schedule
  64 15:27:39 <API> like we have on a11y
  65 15:27:53 <API> it is more frederic peters saying "it would be good to have a meeting due X"
  66 15:28:06 <API> this is the reason I proposed that,
  67 15:28:14 <clown> so… you don't know when you will be checking about 3.4 a11y features at this meeting ?  :-)
  68 15:28:26 <API> as we have a more fixed schedule, and some or last meetings are somewhat empty
  69 15:28:44 <API> clown, yes, this is the reason Im proposing to do that ;)
  70 15:28:53 <API> instead of arriving at the release meeting and say
  71 15:28:59 <API> ok, I don't know the status of the others
  72 15:29:08 <API> we will talk about that on next meeting
  73 15:29:14 <API> Im proposing to add that to the agenda
  74 15:29:17 <clown> okay
  75 15:29:18 <clown> cool
  76 15:29:25 <API> so at the un-scheduled release team I could say
  77 15:29:36 <API> "we talked about that on last/two meetings ago, and ..."
  78 15:30:39 <clown> sure.
  79 15:32:33 <API> well, it seems that people doesnt' need to use this miscellaneous time ;)
  80 15:32:49 <API> so if nobody says anything I will end this meeting at XX:35
  81 15:35:10 <jjmarin> done !
  82 15:35:33 <clown> thanks API.
  83 15:35:50 <API> #endmeeting

Attached Files

To refer to attachments on a page, use attachment:filename, as shown below in the list of files. Do NOT use the URL of the [get] link, since this is subject to change and can break easily.
  • [get | view] (2021-02-25 09:41:56, 4.8 KB) [[attachment:20120105_log.txt]]
 All files | Selected Files: delete move to page copy to page

You are not allowed to attach a file to this page.