libre graphics meeting

LGM2019_meeting_log_2019_03_06

2019-03-06 21:00:06<houz> hi
2019-03-06 21:02:03* a-l-e[m] (alematrixo@gateway/shell/matrix.org/x-qbrijpefkrqzknxi) has joined
2019-03-06 21:02:04<a-l-e[m]> Hi houz ... the header sayz that the next meeting is next week...
2019-03-06 21:02:25<houz> last meeting we said today
2019-03-06 21:02:39<houz> to finalize the schedule
2019-03-06 21:03:39<franktrampe> That is true.
2019-03-06 21:04:41<a-l-e[m]> Maybe... : - )
2019-03-06 21:04:55<houz> from our local side there was just one open question: did probono reply to you, a-l-e[m]?
2019-03-06 21:05:05<houz> i pinged him on irc last week and reminded him
2019-03-06 21:05:38<a-l-e[m]> ... no but I can ping him... he is back in town...
2019-03-06 21:06:22<houz> oh, and that one indian student we accepted, he had to cancel because lgm clashes with his exams. so the 1st slot on sunday will be free, too.
2019-03-06 21:07:04* a-l-e (~a-l-e@pool1-28.cgn.as8758.net) has joined
2019-03-06 21:11:00<houz> then there is a question that came up in our internal discussions: how were t-shirts planned in the past? people didn't pre-order them, right? so was there just some lucky guessing about how many are needed and in what sizes?
2019-03-06 21:12:33<franktrampe> There was no solicitation on the mailing list, certainly.
2019-03-06 21:13:29<franktrampe> Nobody here from the Seville team?
2019-03-06 21:15:13<houz> doesn't seem so
2019-03-06 21:15:29<pippin> different approaches have been taken, the most creative perhaps - was on demand, self serve/helped printing on-site
2019-03-06 21:15:57<houz> we thought about something like that, too. we are in the arts academy after all, so screen printing might be possible
2019-03-06 21:16:19<houz> but so far that's just ideas
2019-03-06 21:18:44<a-l-e> we had some pre-ordering, some on site printing, some guessing and i think one time some big stop left over...
2019-03-06 21:18:53<a-l-e> sevilla iirc asked for a pre-order.
2019-03-06 21:19:05<franktrampe> That's what I thought, but I couldn't find the e-mail.
2019-03-06 21:20:49<houz> right, i remember that there was a list on the table, but i have no memory of how i got on there :-/
2019-03-06 21:22:35<pippin> if we had facebook integration we could just query fool_id.shirts_size
2019-03-06 21:23:22<franktrampe> It's amazing what one can infer from pictures and click habits.
2019-03-06 21:24:09<houz> :-)
2019-03-06 21:24:25<pippin> houz: maybe the tshirt meta-data has the same origin as the nationalities? ;)
2019-03-06 21:24:59<houz> ah right, the random assignment of people
2019-03-06 21:26:12<houz> so, do we feel like having a final look over the schedule and ratifying it?
2019-03-06 21:27:54<franktrampe> Were we going to try to find fillers for the empty spots?
2019-03-06 21:29:27<houz> there are no empty spots. we added an orga meeting to the first day as requested
2019-03-06 21:29:42<franktrampe> Ah, okay.
2019-03-06 21:30:08<houz> that gives people the opportunity to discuss things early on, and in the final orga meeting before closing lgm those things can be brought up again
2019-03-06 21:30:45<houz> the draft is here: https://docs.google.com/spreadsheets/d/1TJF4_w09xCkG6aOfZQxsyw7WzYwrfGX6R9e9dnZXj2M/edit#gid=1835886334
2019-03-06 21:31:04<houz> make sure you are on the first spreadsheet "LGM Schedule aktuell"
2019-03-06 21:32:18<franktrampe> I'm no expert, but it looks good to me.
2019-03-06 21:32:21<pippin> more than one orga meeting, lets the earlier ones focus on past|present|future, while letting the one before closing be more about future/next year/get people involved
2019-03-06 21:32:32<houz> +1
2019-03-06 21:32:42<a-l-e> i don't think that finishing with an orga meeting is a good idea...
2019-03-06 21:33:13<franktrampe> No matter how hard we try, we always end up with unfinished business at the end.
2019-03-06 21:33:17<houz> we always had that in the end. call it orga meeting or meta-discussion or whatever
2019-03-06 21:33:45<franktrampe> Obviously, we will try to make the most out of the earlier meeting, but I am certain that we will be thankful that there is one at the end.
2019-03-06 21:34:13<a-l-e> and i'm never been happy with it : - )
2019-03-06 21:34:33<a-l-e> you separate the organizers from the rest of the group just as people are saying goodbye to each other...
2019-03-06 21:35:10<houz> i see that "orga meeting" as a public thing. it's in the same slot as "lgm 2020" after all
2019-03-06 21:35:59<franktrampe> Yes. We got some flak last year or the year before for having a classist structure.
2019-03-06 21:36:13<franktrampe> That's why we try to conduct all business on the main mailing list now.
2019-03-06 21:36:29<houz> and why i provide meeting logs
2019-03-06 21:36:38<franktrampe> Indeed.
2019-03-06 21:37:23<franktrampe> I think that we ought to try, per pippin's suggestion, to get as much administrivia tied down at the first meeting as possible so that we can use the closing meeting to rope people into helping with 2020.
2019-03-06 21:37:33<pippin> that end-orga meeting can well be shorter now that there is more than one slot for such talk
2019-03-06 21:38:33<franktrampe> If it wraps up earlier, we can say goodbye early. I think that we can make it engaging enough that people won't be waiting for the "Goodbye" time slot to come back into the room.
2019-03-06 21:39:24<franktrampe> We also might want to save some time for the Rennes team to present.
2019-03-06 21:39:52<a-l-e> well, i will repeat my opinion next yeara then : - )
2019-03-06 21:40:47<franktrampe> I think that most of us share your concerns. If we play this right, the closing "organizational" meeting will not split off the casual attendees.
2019-03-06 21:41:34<a-l-e> well, there are good chances that i won't be able to join on sunday afternoon, since the good train connection is at 12:00
2019-03-06 21:41:38<pippin> when it comes to the schedule, I suspect we have some new faces that speak on the last/second-to last day - it would nice if we could promoted them to appear in front of others earlier
2019-03-06 21:41:52<a-l-e> after 16:00 it gets hard to still get home, if i have a bicycle with me.
2019-03-06 21:42:02<houz> yes, i see it more as a view back at the lgm that is about to end so that people can say what they liked or didn't like so that things can be done better next year. for me it's not so much about planning the organizational structure lgm has
2019-03-06 21:42:22<a-l-e> anywaay, i like the starting much better.
2019-03-06 21:42:44<houz> pippin: which ones for example?
2019-03-06 21:43:04<a-l-e> and i don't see big issues, except that it will be hard to get people at 10:00 on sunday... but any time in the AM would be hard...
2019-03-06 21:43:07<houz> i mean, there are several new speakers
2019-03-06 21:43:19<franktrampe> I hope so!
2019-03-06 21:44:01<pippin> houz: with the current spreadsheet breakdown, confirming suspicion would take more time - but I think the majority of FT on the last day might fall into this category
2019-03-06 21:45:48<franktrampe> pippin, does that actually translate into too many people missing the talks? I know that the first morning and the last afternoon suffer somewhat, but the place is never empty.
2019-03-06 21:45:56<a-l-e> probono on sunday as first is a bit hard... but since he is not replying...
2019-03-06 21:46:11<houz> ok, i'll talk to aude tomorrow. do we need another meeting then, or can we announce it once we moved some regulars back a little?
2019-03-06 21:46:45<houz> a-l-e: the first slot is hard for everyone
2019-03-06 21:47:02<houz> that he's in that slot is pure coincidence
2019-03-06 21:47:18<pippin> franktrampe: having them talk at earlier days makes the hallway track *a lot* more interesting to the new faces, as others have/know topic to talk with them about
2019-03-06 21:47:22<a-l-e> i understand that : -)
2019-03-06 21:47:24<franktrampe> Ah.
2019-03-06 21:47:37<a-l-e> and since he is not replying i will not even try to change that...
2019-03-06 21:48:03<franktrampe> Okay. If it isn't too much trouble, I think that that would be a nice adjustment (moving the new people up).
2019-03-06 21:49:51<houz> i marked some of them
2019-03-06 21:50:44<houz> we have to take care to not rip apart the clustering of similar topics though
2019-03-06 21:51:05<franktrampe> So many constraints in this optimization problem.
2019-03-06 21:51:41<franktrampe> Well, let's do what we can.
2019-03-06 21:53:15<houz> will do
2019-03-06 21:53:27<houz> again, do we need another meeting afterwards?
2019-03-06 21:54:06<franktrampe> I don't know how this was handled previously. Probably enough just to send to the mailing list for final comments.
2019-03-06 21:56:45<houz> me neither, i was never part of the schedule team. pippin?
2019-03-06 21:57:02<a-l-e> well, it looks like that at the end it will only be 4 days...
2019-03-06 21:57:05<a-l-e> ooops...
2019-03-06 21:58:57<houz> about that, on wednesday there will be something but i am not really up to date of what is planned exactly. there will be some (german) talks but i am unsure about the details
2019-03-06 21:59:30<a-l-e> ah, ok...
2019-03-06 21:59:57<houz> i would have been fine with the regular schedule spread over 5 days, but it's not my call, i am just helping with organizing, i am not deciding or planning
2019-03-06 22:01:35<pippin> the photowalk would also be on the wednesday
2019-03-06 22:01:41<houz> yes
2019-03-06 22:05:48<houz> so, anything else? i would try to finalize the schedule tomorrow with aude and then send a mail to the people involved for final approval sans a meeting. is that fine for everyone?
2019-03-06 22:06:17<a-l-e> ok
2019-03-06 22:07:34<pippin> yep
2019-03-06 22:07:39<houz> franktrampe: btw, thanks for taking care of the api application!
2019-03-06 22:07:55<houz> *spi
2019-03-06 22:08:03<franktrampe> I pinged Martin today to see if it was discussed and accepted. No news yet. But I'm hopeful.
2019-03-06 22:08:37<franktrampe> I can't think of any other business today.
2019-03-06 22:09:05<houz> great, let's wrap it up then. thank you all for your time
2019-03-06 22:09:20<franktrampe> And thanks for all your work on the schedule.
2019-03-06 22:09:37<franktrampe> Oh, wait.
2019-03-06 22:09:43<franktrampe> Are we still meeting next week?
2019-03-06 22:09:57<houz> i'd say so
2019-03-06 22:10:29<franktrampe> Okay. I may not be able to come, but I'll catch up from the logs if necessary.
2019-03-06 22:10:36<franktrampe> Does that work for everybody else?
2019-03-06 22:10:42<franktrampe> March 13th.
2019-03-06 22:11:11<houz> there might be a new venue, but that's currently being discussed. apparently we can't get internet to the place, so we might have to move to the arts academy. but that's not final, we'll keep you informed
2019-03-06 22:11:54<houz> after all, who wants to have an lgm without internet? :-D
2019-03-06 22:12:28<franktrampe> I can survive an hour or so without water, but surely not Internet!
2019-03-06 22:12:56<houz> the three kinds of death: brain dead, heart dead and off the internet
2019-03-06 22:13:33<a-l-e> well, no chairs is ok... but no internet? aaaaargh!
2019-03-06 22:13:51<franktrampe> Exactly!
2019-03-06 22:14:10<a-l-e> but nowadays most of the people attending will be having 4G...
2019-03-06 22:14:14<houz> in the end people have to listen to the talks instead of sitting in the audience and staring at the laptop
2019-03-06 22:14:38<houz> a-l-e: for non-europeans that might be harder
2019-03-06 22:14:54<a-l-e> of course...
2019-03-06 22:15:12<a-l-e> that's why i'm writing "most"... i won't have it, since i'm no real european.
2019-03-06 22:15:31<houz> ah, we'll get you a prepaid sim card
2019-03-06 22:16:09<a-l-e> well, i can live with wifi, no worries!
2019-03-06 22:16:22<franktrampe> Well let's hope we have WiFi then.
2019-03-06 22:16:23<houz> we'll do our best
2019-03-06 22:17:03<a-l-e> and, otherwise, i'll take a pigeon with me, with a usb key attached to it...
2019-03-06 22:17:24<franktrampe> High bandwidth, but very high latency.
2019-03-06 22:17:50<houz> rfc 1149
2019-03-06 22:18:13<houz> oh, there is even rfc 2549 now
2019-03-06 22:18:27<a-l-e> i'm not in a hurry.
2019-03-06 22:19:31<franktrampe> The best way to live life.

download raw logfile: LGM2019_meeting_log_2019_03_06.txt