[LGM] Schedule

[Gregory Pittman]

I've already made hotel/travel arrangements, arriving a day ahead and leaving the second day after. All the same, I would rather have full days start to finish, perhaps finishing a little early the last day.

Greg 

On 2/15/19 11:44 AM, Pat David wrote:
> I can second this from experience traveling around the US for meetings.  I should also be local well in advance of the meeting, but Nates points are (uhm...) on point.
> 
> We were also hoping to host a photowalk again this year, but I don't recall if I submitted it as an actual event or not - can we possibly get that into the agenda consideration?  It's been quite fun in the past to get out and stroll around with people and their cameras. :)
> 
> pat
> 
> On Fri, Feb 15, 2019 at 8:58 AM Nathan Willis <nwillis at glyphography.com <mailto:nwillis at glyphography.com>> wrote:
> 
>     Well, I haven't seen a lot of discussion about the format question, but now that acceptances have evidently started going out to presenters, I do want to chip in my two cents' worth.
> 
>     From my POV, one thing that really did *not* work about the 2018 schedule was having the two 'half days' at the beginning and end -- the starting in the evening on day one, and ending with a partial day at the end.
> 
>     The primary trouble with this is that if anyone is coming from further away than a commuter train -- which is a lot of people -- the two half days mean that the attendee still actually loses both full days. You can't get from North America, South America, Asia, or even the remoter corners of Europe between morning and the start of a late-afternoon/evening program. Especially when you factor in checking in at hotels/accommodations. And, likewise, you can't get home leaving in the afternoon. So you are forced to come a day earlier and leave a day later, losing those days to travel entirely.
> 
>     That said, I know people do generally arrive the evening before the program begins, and it's great to have something for everyone to do. But I submit that it would be better to organize a social / get-together / cooperative-meal hunt for that arrival evening than to have program material start then. Many levels of possibility there, from something that is actually organized to leaving a wiki-space open for attendees themselves to suggest and plan possible meet-ups.
> 
>     So that's my main take away. For the record, this year I will actually be in Europe already when the event starts, so I hope everyone understands that this comment is not of the "be convenient for me personally" nature. It really is harder on people who travel greater distances to lose that extra time, and I think we want to make LGM easy to attend whenever we have an opportunity to do so.
> 
>     Thanks,
>     Nate
> 
>     On Tue, Dec 11, 2018 at 4:41 PM Soenke Zehle <soenke at kein.org <mailto:soenke at kein.org>> wrote:
> 
>         Hi all,
> 
>         we would start working from the 2018 model:
> 
>         https://libregraphicsmeeting.org/2018/program/
> 
>         Before we (program committee plus local K8 team) do that - what
>         worked, what didn't work 2018 as far as the number of talks /
>         workshops was concerned?
> 
>         best,
> 
>         Soenke
>         Am Di., 11. Dez. 2018 um 17:32 Uhr schrieb Nathan Willis
>         <nwillis at glyphography.com <mailto:nwillis at glyphography.com>>:
>         >
>         > Hiyo. So I just saw the official dates on the 2019 web site.
>         >
>         > It says "May 29 to June 2" which is five days. Can we get some more specificity about what the program breakdown is? Namely, how many (and which) days we are planning to schedule talks and which we are planning to use for other types of content?
>         >
>         > That can be an important detail for anyone who can't take off five contiguous days for an event, and it's never too early to get the information out there.
>         >
>         > It would also probably be useful for any teams who are wanting to arrange hackathon / meetup / sprint time for multiple folks coming in....
>         >
>         > Thanks,
>         > Nate
>         >