14:51:31 <API> #startmeeting
14:51:31 <tota11y> Meeting started Thu Nov  3 14:51:31 2011 UTC.  The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot.
14:51:31 <tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
14:51:43 <API> #topic hackfest update
14:52:03 <API> #info in the end space was also a issue on Brno
14:52:27 <API> #info in fact there are doubts about having enough space just for gtk folks
14:52:39 <API> #info so, although we will kill sinergies
14:52:48 <API> #info right now we are activating plan c)
14:52:55 <API> #info January, Coruña, Igalia offices
14:53:07 <desrt> do you have more specific ideas about the date?
14:53:26 <API> desrt, my plan was asking people about availability
14:54:01 <desrt> all other things equal, i'd push for 'early'
14:54:33 <desrt> W1 may be trouble for people who are finishing up holidays, but W2 perhaps?
14:55:09 <joanie> API, three kings is on friday this year it looks like.
14:55:21 <joanie> do people take more time off after or just come back to work on Monday?
14:55:23 <joanie> (typically)
14:55:25 <clown> "three kings"?
14:55:27 <API> well, I was thinking more on w3
14:55:45 <API> I think that in america you say "three wise men"
14:55:57 <API> 6 is also a holiday in spain
14:55:58 <joanie> clown http://www.spanish-fiestas.com/spanish-festivals/christmas-in-spain.htm
14:56:27 <clown> ah, three kings/wise-men is  a spanish holiday.  that's what I was missing — thanks.
14:56:58 * clown is impressed with joanie's new cultural knowledge :-)
14:57:22 <API> I was thinking on w3 instead of w2 to avoid coming for a hackfest just after holidays
14:57:24 <clown> API:  I'm probably available, and I recently learned that the university gives $1000/year to staff for "professional development".
14:57:48 <clown> So, I have to convince the powers that be that his qualifies as professional development.
14:58:08 <clown> but, I also have to decide if this is the best way to spend the money for 2012.
14:58:43 <clown> where can I look for more information about this hackfest, again?
14:58:48 <joanie> clown, if it's a one shot deal, maybe wait until we have the proper hackfest as I *think* we're looking at a follow-up ATK/AT-SPI2 hackfest
14:58:59 <joanie> in january I mean (the follow-up)
14:59:13 <joanie> and then some other event for the full team later in the year
14:59:28 <clown> the followup  is in january?, or later in the year?
14:59:49 <clown> whatever, actually. it sounds like the followup is a better place to spend the funds.
15:00:17 <joanie> the follow-up AT-SPI/ATK is in January
15:00:26 <joanie> (right API??)
15:00:48 <API> yes, thats the idea
15:00:57 <API> idea is:
15:01:14 <API> atk/at-spi2 followup at the begining of the year
15:01:34 <API> accessibiliy hackfest just before/after or during GUADEC, probably more general purpose
15:01:52 <API> anyway, focusing again
15:02:03 <API> imho, both w1 and w2 are bad due holidays and so on
15:02:21 <API> so I was thinking on w3, w4
15:02:28 <API> now we need to ask about availability
15:02:35 <API> of people
15:02:46 <API> but as we already said, we don't have all the people
15:02:47 <API> here
15:02:54 <API> btw, hi jjmarin
15:02:59 <jjmarin> hi !
15:03:02 <clown> time for an email, API.
15:03:13 <API> jfyi, today is a "slim" meeting, as we started missing a lot of people
15:03:15 <API> clown, right
15:04:25 <API> #action API will sent a summary mail, also asking about availability
15:04:31 <API> so, anything else here?
15:04:34 <API> questions, doubts?
15:04:37 <clown> so, joanie, were you recommending the better place for me to use the funds is at GUADEC?
15:05:03 <joanie> clown, I'm not going to far as "recommend" but that is what I was suggesting for your consideration
15:05:41 <joanie> but perhaps waiting until we have an official agenda for the event
15:05:45 <clown> okay, I think I understand the schedule, and what each meeting is about.  I'll take that into consideration.
15:05:46 <joanie> before deciding for sure
15:05:56 <clown> makes sense.
15:06:29 <API> ok, so as we have some people now,
15:06:33 <API> lets move on with the agenda
15:06:37 <API> #topic GNOME 3.4 Feature Proposal Status
15:06:47 <API> #info no new activity on the thread
15:07:00 <API> #info release-team meeting was scheduled next saturday
15:07:05 <API> #info 5-Nov
15:07:20 <API> #info I guess that we will talk about those feature proposals there
15:07:24 <API> questions, doubts?
15:07:38 <joanie> not from me
15:08:03 <jjmarin> Any idea of what features are approved ?
15:08:12 <clown> there has been some progress on zoom options dialog, but I'm not sure it's enough to talk about. Hmm...
15:08:49 <API> jjmarin, it is just about feelings
15:08:57 <API> and as I said no new feedback since then
15:09:04 <API> but about my feelings
15:09:21 <API> imho, all features proposed by clown would be accepted
15:09:27 <API> probably also dots
15:09:49 * clown oh joy!  lots of work for me!
15:09:52 <API> dasher will not be included as a feature, but I would like dasher to be included again as a moduleset
15:10:13 <API> I will use again that example
15:10:19 <API> inkscape is included on GNOME modulesets
15:10:27 <API> and it is not integrated and blah blah
15:10:34 <API> it is just a cool app, as dasher
15:10:45 <API> so next steps would be check how integrate dasher
15:10:59 <API> and finally eviacam will not be included
15:11:04 <API> not as feature
15:11:13 <API> not as new module on moduleset
15:11:33 <API> but as I said when we were debating which features propose
15:11:45 <API> now we know more about what it is required to be accepted
15:12:01 <API> so, imho, it was worth of our time
15:12:13 * joanie nods
15:12:23 <API> more questions, doubts?
15:12:44 <API> btw, as I said, previous statements are just my "feelings"
15:12:53 <API> but as we started late, lets move on the meeting
15:13:03 <API> #topic Marketing and Fundraising
15:13:04 <API> jjmarin, ?
15:13:10 <jjmarin> ok
15:14:50 <jjmarin> #info This is my propsal for the FoG goal
15:15:03 <jjmarin> #Info https://live.gnome.org/Accessibility/Marketing/FoG#preview
15:16:01 <jjmarin> I received some feedback/corrections, but I'd like to be sure all the a11y team agrees
15:16:42 <jjmarin> Can we validate in the meeting ?
15:16:48 <API> how area you interacting with marketing folks?
15:16:51 <API> meetings, mails?
15:17:24 <jjmarin> Well, the marketing team is waiting for this wording and they will
15:17:31 <jjmarin> validate as well
15:17:55 <jjmarin> We need to update our Roadmap as well
15:18:09 <joanie> jjmarin, I know. On my list.
15:18:44 <jjmarin> joanie; I will help you
15:18:48 <joanie> :)
15:18:52 <joanie> thank you :)
15:19:24 <joanie> jjmarin, is there a deadline?
15:19:34 <API> about feedback/corrections, lets do that after the meeting (just 10 minutes anyway)
15:19:50 <jjmarin> No, but I'd like to do it ASAP
15:20:28 <jjmarin> Anyway, I'll try to check what marketing folks thinks in advance in the IRC
15:21:09 <jjmarin> joanie: do you think we can have it done for the next week ?
15:21:21 <joanie> we can try
15:21:27 <jjmarin> :-)
15:21:30 <joanie> at least get a draft out for API to consider
15:21:43 * clown notes that quarterly reports are also due ASAP.
15:21:47 <API> ok, seems a plan
15:21:52 <joanie> not ASAP, the 11th
15:21:54 <joanie> ;)
15:21:57 <API> clown, yes, this is next topic ;
15:22:06 <API> less that 10 minutes
15:22:07 <jjmarin> #action Juanjo will ask for the next steps for the FoG campaign
15:22:12 <clown> joanie:  almost ASAP?
15:22:24 <joanie> :)
15:22:46 <API> jjmarin, ok thanks
15:22:51 <API> anything else?
15:22:53 <API> questions, doubts?
15:22:54 <jjmarin> another thing
15:23:40 <jjmarin> #Info Allan Bell want to revice the a11y planet
15:23:53 <jjmarin> wants to revive
15:24:05 <clown> s/revice/revive/
15:24:26 <joanie> freudian slip perhaps
15:24:34 <clown> indeed.
15:24:39 <jjmarin> Our position was we don't have enough activity for a gnome a11y planet
15:25:01 <jjmarin> but maybe is a good idea to participate in a free desktop a11y planet
15:25:12 <joanie> btw....
15:25:19 <joanie> before it was not gnome a11y planet
15:25:23 <joanie> it was bigger than that
15:25:25 <API> well, it was also, "our hands are full with other stuff"
15:25:28 <joanie> but something we were doing
15:25:36 <API> I mean that when we discussed it
15:25:58 <joanie> brb door
15:26:02 <API> it was both "we don't blog so often" and also "creating a planet a11y means more work, now and after that, due maintenance"
15:26:11 <API> so
15:26:19 <API> if Alan Bell wants to create a planet-a11y
15:26:31 <API> obviously, we are not against
15:26:37 <API> and I will join
15:26:55 * joanie is back
15:27:12 <jjmarin> API: +1
15:28:25 <API> well, as we don't have too much time now
15:28:27 <API> in summary
15:28:36 <jjmarin> So we agree that we will participate in a a11y planet if Allan is willing to create one
15:28:42 <API> exactly
15:28:44 <API> thanks ;)
15:29:30 <jjmarin> Do we need to put in a Info command ?
15:29:38 <jjmarin> or in action ?
15:29:51 <joanie> info please
15:30:02 <jjmarin> #Info We agree that we will participate in a a11y planet if Allan is willing to create one
15:30:13 <jjmarin> copy/paste ;-)
15:30:20 <API> ok, so just to conclude
15:30:33 <API> #topic Team Quarterly Reports (Q3)
15:30:36 <API> another reminder
15:30:46 <API> #info please, fill Q3 report
15:30:54 <API> #info limit 11-11-2011
15:31:00 <API> s/limit/deadline
15:31:09 <API> #topic miscellaneous time
15:31:10 <clown> interesting date:  11-11-11
15:31:32 <API> someone want to add something not included on the agenda?
15:32:24 <jjmarin> Who are the one in charge of the Q3 report ?
15:32:37 <joanie> jjmarin, individuals all write their parts
15:32:45 <joanie> I turn it into a summary with pretty english
15:32:46 <jjmarin> ok
15:32:48 <joanie> API approves
15:32:54 <joanie> API and I submit
15:33:05 <clown> whenever I commit on the Q3 wiki page, I'm told that a message has been sent to joanie (and possibly API).
15:33:05 <jjmarin> thanks !
15:33:07 <joanie> really I submit it, but officially it's both of us ;)
15:33:35 <joanie> jjmarin, so if you have marketing content to add to the q3, go for it
15:33:42 <joanie> but it's no obligation
15:34:06 <jjmarin> ok
15:34:23 <jjmarin> but this Q3 there is nothing worth to mention
15:34:30 * joanie smiles
15:34:35 <jjmarin> from the marketing side :-)
15:36:45 <jjmarin> API: from the eviacam proposal, it is good idea to have very good idea about what we should do to integrate in the future
15:37:08 <API> yes,  makes sense
15:37:15 <jjmarin> I mean, Cesar made a question about if a service can manage the mouse
15:37:48 <jjmarin> and nobody gave no clue
15:38:00 <jjmarin> no clue / clue
15:38:10 <jjmarin> .... tip
15:38:17 <API> ah, thats true
15:38:39 <API> probably it is something to include on "what we should do ..."
15:38:48 <API> * investigate if a service is a valid answer
15:38:51 <clown> jjmarin: is this like asking is there a dbus service for mouse operations?  something like that?
15:39:08 <API> clown, or if you can create it
15:39:56 <API> ok
15:40:00 <API> well, ten minutes over time
15:40:04 <clown> I thinks GOK did it somehow.  That is control the mouse using an onscreen keyboard.
15:40:11 <API> so lets conclude the meeting
15:40:14 <clown> but I don't know how GOK did it.
15:40:18 <clown> sure, let's conclude.
15:40:23 <API> but GOK was an application
15:40:27 <API> that was Cesar doubt
15:40:28 <jjmarin> Additionally, one detail to take into account is that to send mouse commands and provide visual feedback (i.e. dwell time countdown and other hints) it is necessary to have a Display handler. Can a service have access to a Display?
15:40:39 <API> anyway, this is off-topic for a meeting
15:40:43 <clown> API, yes an app, but how did it do it under the hood?
15:40:45 <jjmarin> ok
15:40:50 <clown> did it use CORBA?
15:41:03 <clown> dunno.
15:41:22 <API> #info need to investigate service/app and mouse operations. Literature: GOK and others
15:41:25 <API> #endmeeting