Going to swing by shortly after juggling at 19:00. See you there Cheers, Matt Chung blog[1] | github[2] | twitter[3] | linkedin[4] On Mon, May 30, 2016, at 04:37 PM, Ian Lee wrote: > Grabbed room B116 tonight (Monday) at 19:00 — > https://twitter.com/IanLee1521/status/737424964131770368 > > ~ Ian Lee | [email protected] > >> On May 30, 2016, at 12:16, Ian Lee <[email protected]> wrote: >> >> With the lightning talks at 08:30 tomorrow morning, I’d like to >> suggest, if folks are available and interested, in doing an open >> space this evening. >> >> I was thinking I could put a card up on the board with a plan for >> 19:00 this evening (after the lightning talks) if anyone wanted to >> join. Maybe we could spin that off to go find food as well >> afterwards. >> >> Would anyone else be interested in this? If I hear from at least one >> person, I’ll get a room picked during the lunch break. >> >> Cheers, >> >> ~ Ian Lee | [email protected] >> >>> On May 25, 2016, at 15:05, Ian Cordasco <[email protected]> >>> wrote: >>> >>> Yeah and maybe avoid picking that one table in that one part of the >>> room that I hate ;) >>> >>> On Wed, May 25, 2016 at 2:35 PM, Eric Casteleijn >>> <[email protected]> wrote: >>>> alright, let's coordinate a place to meet once we know the lay of >>>> the land. >>>> >>>> On Wed, May 25, 2016 at 11:57 AM, Ian Cordasco >>>> <[email protected]> >>>> wrote: >>>>> >>>>> Sounds great to me. This should allow more people to come, >>>>> especially if >>>>> they're budget doesn't quite allow anything else and makes >>>>> scheduling easy. >>>>> >>>>> On May 25, 2016 1:29 PM, "Ian Lee" <[email protected]> wrote: >>>>>> >>>>>> How about breakfast on Tuesday? That way we avoid any confusion >>>>>> Monday as >>>>>> everyone is checking in? >>>>>> >>>>>> On Wed, May 25, 2016 at 10:59 AM, Eric Casteleijn >>>>>> <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>> Frank's Noodle House is pretty close, but a breakfast meeting >>>>>>> works for >>>>>>> me too. >>>>>>> >>>>>>> On Wed, May 25, 2016 at 5:37 AM, Ian Cordasco >>>>>>> <[email protected]> wrote: >>>>>>>> >>>>>>>> Maybe it makes sense to not inconvenience people going to >>>>>>>> tutorials? >>>>>>>> Should we change the day/meal. Since PyCon provides breakfast, >>>>>>>> we could do a >>>>>>>> breakfast meetup during PyCon. That should be free of conflicts >>>>>>>> >>>>>>>> On May 24, 2016 11:23 PM, "Ian Lee" <[email protected]> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> Looks like the tutorials end at 12:20 and start back up at >>>>>>>>> 13:20. I'm >>>>>>>>> ok leaving a little early, but I'd personally like to be back >>>>>>>>> in time for >>>>>>>>> the start of them at 13:20. >>>>>>>>> >>>>>>>>> I don't know the good places, but how about we plan on >>>>>>>>> something close >>>>>>>>> to the venue at 11:45? That should give us until 13:00 or so >>>>>>>>> and plenty of >>>>>>>>> time for those of us with afternoon tutorials to make it back. >>>>>>>>> Objections? >>>>>>>>> Recommendations on a place to eat? >>>>>>>>> >>>>>>>>> On Thu, May 19, 2016 at 9:38 PM, Dan Wandschneider >>>>>>>>> <[email protected]> wrote: >>>>>>>>>> >>>>>>>>>> Lunch on Sunday makes sense. >>>>>>>>>> >>>>>>>>>> On Thu, May 19, 2016 at 6:58 AM, Ian Lee >>>>>>>>>> <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>>> >>>>>>>>>>> I would prefer lunch (between the tutorials) over dinner, as >>>>>>>>>>> there >>>>>>>>>>> is the opening reception on the evening of the 29th (which >>>>>>>>>>> as you might >>>>>>>>>>> guess, I'm planning to attend.) >>>>>>>>>>> >>>>>>>>>>> https://us.pycon.org/2016/events/reception/ >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> On Wednesday, May 18, 2016, Eric Casteleijn >>>>>>>>>>> <[email protected]> >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> 29th works for me, either lunch or dinner. Frank's noodle >>>>>>>>>>>> house is >>>>>>>>>>>> close to the Pycon venue, and probably has most of the >>>>>>>>>>>> dietary options >>>>>>>>>>>> covered, but Portland's pretty easy to get around, so if >>>>>>>>>>>> people have >>>>>>>>>>>> specific hankerings and are willing to take a bus, I'd be >>>>>>>>>>>> happy to come up >>>>>>>>>>>> with other suggestions. >>>>>>>>>>>> >>>>>>>>>>>> On Wed, May 18, 2016 at 9:02 AM, Ian Cordasco >>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>> >>>>>>>>>>>>> We didn't really decide on a time. >>>>>>>>>>>>> >>>>>>>>>>>>> I think we'll all be around on the 29th though. Would >>>>>>>>>>>>> lunch or >>>>>>>>>>>>> dinner >>>>>>>>>>>>> on the 29th sound appealing to anyone? >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, May 18, 2016 at 12:34 AM, Matt Chung >>>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>>> Hey All, >>>>>>>>>>>>>> Just following up here. @Ian, Has a date been >>>>>>>>>>>>>> established ? >>>>>>>>>>>>>> I'll be at >>>>>>>>>>>>>> Pycon between the 27th and 31st so hopefully it falls >>>>>>>>>>>>>> between >>>>>>>>>>>>>> there :) >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> Matt Chung >>>>>>>>>>>>>> blog | github | twitter | linkedin >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Apr 11, 2016, at 12:55 PM, Eric Casteleijn wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hey, so I meant to reply, and then spaced on it, but: I'd >>>>>>>>>>>>>> be >>>>>>>>>>>>>> happy to >>>>>>>>>>>>>> suggest locations, once we have a date, and a sense of >>>>>>>>>>>>>> dietary >>>>>>>>>>>>>> and other >>>>>>>>>>>>>> requirements/desires of attendees, if we plan for it to >>>>>>>>>>>>>> include >>>>>>>>>>>>>> food/drinks. >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Mar 28, 2016 at 3:53 PM, Ian Cordasco >>>>>>>>>>>>>> <[email protected]> >>>>>>>>>>>>>> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> On Mon, Mar 28, 2016 at 4:22 PM, Eric Casteleijn >>>>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>>>> I will be at Pycon, and would love to attend such a >>>>>>>>>>>>>>> meeting, >>>>>>>>>>>>>>> though I >>>>>>>>>>>>>>> realize I've only been lurking here so far. I'd like to >>>>>>>>>>>>>>> contribute more >>>>>>>>>>>>>>> though. I live in Portland, so any date is likely to >>>>>>>>>>>>>>> work for >>>>>>>>>>>>>>> me. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Don't worry about being a "lurker". :-) You'll likely be >>>>>>>>>>>>>> our >>>>>>>>>>>>>> source of >>>>>>>>>>>>>> a location to head to if we can't get a BoF space (which >>>>>>>>>>>>>> I think >>>>>>>>>>>>>> will >>>>>>>>>>>>>> suit us well). >>>>>>>>>>>>>> >>>>>>>>>>>>>> I look forward to seeing you, Matt, Ian, and whomever >>>>>>>>>>>>>> else >>>>>>>>>>>>>> comes. :-) >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers, >>>>>>>>>>>>>> Ian >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> -- >>>>>>>>>>>>>> - eric casteleijn >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> -- >>>>>>>>>>>> - eric casteleijn >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> -- >>>>>>>>>>> >>>>>>>>>>> ~ Ian Lee | [email protected] >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> _______________________________________________ >>>>>>>>>>> code-quality mailing list >>>>>>>>>>> [email protected] >>>>>>>>>>> https://mail.python.org/mailman/listinfo/code-quality >>>>>>>>>>> >>>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>>>> >>>>>>>>> ~ Ian Lee | [email protected] >>>>>>>>> >>>>>>>>> _______________________________________________ >>>>>>>>> code-quality mailing list >>>>>>>>> [email protected] >>>>>>>>> https://mail.python.org/mailman/listinfo/code-quality >>>>>>>>> >>>>>>>> >>>>>>>> _______________________________________________ >>>>>>>> code-quality mailing list >>>>>>>> [email protected] >>>>>>>> https://mail.python.org/mailman/listinfo/code-quality >>>>>>>> >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> - eric casteleijn >>>>>> >>>>>> >>>>>> >>>>>> >>>>>> -- >>>>>> >>>>>> ~ Ian Lee | [email protected] >>>> >>>> >>>> >>>> >>>> -- >>>> - eric casteleijn > _________________________________________________ > code-quality mailing list > [email protected] > https://mail.python.org/mailman/listinfo/code-quality
Links: 1. http://blog.itsmemattchung.com/ 2. https://github.com/itsmemattchung 3. https://twitter.com/itsmemattchung 4. https://www.linkedin.com/in/matt-chung-32792354
_______________________________________________ code-quality mailing list [email protected] https://mail.python.org/mailman/listinfo/code-quality
