Hello everyone! I am new to the group and new to python programming. I love the idea of a pycon seattle, I want to help out where I can. What about a talk for newbies. Something like "What to do after the basics", "GUI programming in PyQT or something like it" "Python for the web" "Top 10 things You must know to be a pro python programmer". Some advanced topics Computational photography with python, drone piloting with python, "Merry Christmas it's raspberry pi, python and your Christmas lights". I am excited to meet every one at the next seapig meeting.
On Wed, May 1, 2013 at 2:51 PM, <[email protected]>wrote: > Send seattle-python mailing list submissions to > [email protected] > > To subscribe or unsubscribe via the World Wide Web, visit > http://lists.seapig.org/mailman/listinfo/seattle-python > or, via email, send a message with subject or body 'help' to > [email protected] > > You can reach the person managing the list at > [email protected] > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of seattle-python digest..." > > > Today's Topics: > > 1. Proposal for discussions on Python day. (Was Re: > seattle-python Digest, Vol 109, Issue 2) (Jeff Silverman) > 2. Re: NW Python Day 2013? (Kevin LaTona) > 3. Northwest Python Day planning requirements (Mike Orr) > 4. Re: NW Python Day 2013? (Mike Orr) > 5. Re: NW Python Day 2013? (James Thiele) > 6. Re: NW Python Day 2013? (Lion Kimbro) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 01 May 2013 13:41:16 -0700 > From: Jeff Silverman <[email protected]> > To: [email protected] > Subject: [SEAPY] Proposal for discussions on Python day. (Was Re: > seattle-python Digest, Vol 109, Issue 2) > Message-ID: <[email protected]> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > I could do a discussion of how to build a client or a server that speaks > both IPv4 and IPv6. Alternatively, I could do a discussion about how to > build a RESTful server. > > > Jeff Silverman > > > On 05/01/2013 12:00 PM, [email protected] wrote: > > > > ------------------------------ > > Message: 2 > Date: Wed, 1 May 2013 14:14:48 -0700 > From: Kevin LaTona <[email protected]> > To: Seattle Python Interest Group <[email protected]> > Subject: Re: [SEAPY] NW Python Day 2013? > Message-ID: <[email protected]> > Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes > > > > We are starting to get a few sparks going here. > > > Besides AWS, Google and Microsoft what about all the startups we have? > > One good way for all these companies to insure they have Python geeks > to work for them. > > Is to help foster and support such an event locally. > > > I wonder if any of them have a developer or community relations person > that SeaPig could work with to make this happen? > > > I am would think the Python Software Foundation might support it on > some level or other. > > -Kevin > > > > > > > > ------------------------------ > > Message: 3 > Date: Wed, 1 May 2013 14:28:00 -0700 > From: Mike Orr <[email protected]> > To: Seattle Python Interest Group <[email protected]> > Subject: [SEAPY] Northwest Python Day planning requirements > Message-ID: > <CAH9f=uoJgzNSpL=+ > [email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > The first thing we need for a Northwest Python Day is an overall > coordinator. This would require at least 20 hours of planning/executing > work, assuming an event like the last one (at Seattle Central CC). The > coordinator would need to keep track of what is/isn't being done, delegate > tasks as appropriate, and have somebody standing by for any last-minute > problems (e.g., a Macintosh video-plug converter for the projector). The > main coordinating tasks: > > - How many attendees? Larger venues generally cost more and require > booking a month or more in advance. The first Python Day was 25 people (at > Construx), the second (and third?) were 66 (in the UW's Allen room), the > last was 110 (at Seattle Central CC). We consistently get 50% more > attendees than expected. I think the SCCC room had a capacity of 150? In > any case, we should target break-even at 90 and maximum at 150 or 200. > > - Venue? SCCC's Computer Science administrator offered us a nice deal last > time. I think it was $450 for a Saturday, including a donation to the CS > program, and she took care of the college approvals and coordination. So we > might want to consider that again. > > - Registration fee? So far it's been free. The first several days were > no-cost, and the rent was paid by a Lexus/Nexus sponsorship. There was a > donation to cover supplies. > > - One day or two days? We have always done one day and not called it a > "conference", to keep it simple and less work. For two days we'd need to > round up hosts for out-of-towners. > > - Schedule? The past ones have been lightning talks + regular talks. How > long should the talks be? > > - Solicit talk proposals, vet them, and schedule them. Finding speakers has > never been a problem, because you can only fit eight or so talks into one > day. > > - Follow up on the venue contract and logistics. > > - Food, posters, amenities? > > - Publicity/marketing? > > - Setup/takedown work? > > - List of parking and transit options to get to the venue? > > - List of restaurants within walking distance for lunch? If it's in an > isolated location, you'll have to carpool to a mall unless you want to do a > potluck or catering. But bringing potluck items in the morning and > refrigerating/heating them all at once may be difficult, especially for > out-of-towners. Some venues may require their expensive caterer and forbid > outside food. SCCC does, but since the campus is closed on Saturdays they > made an exception for us. > > - Wireless Internet? Some places may charge for this. SCCC normally does > but it was waived because of the CS department sponsorship. Capacity may be > a problem because programmers tend to use the Internet more than other > groups. > > -- > Mike Orr <[email protected]> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.seapig.org/pipermail/seattle-python/attachments/20130501/70851dba/attachment-0001.html > > > > ------------------------------ > > Message: 4 > Date: Wed, 1 May 2013 14:30:49 -0700 > From: Mike Orr <[email protected]> > To: Seattle Python Interest Group <[email protected]> > Subject: Re: [SEAPY] NW Python Day 2013? > Message-ID: > <CAH9f= > [email protected]> > Content-Type: text/plain; charset="iso-8859-1" > > On Wed, May 1, 2013 at 2:14 PM, Kevin LaTona <[email protected]> wrote: > > > > > > > I am would think the Python Software Foundation might support it on some > > level or other. > > > > The PSF has sometimes offered grant money for things like this. I think > last time around we were going to ask for a grant for supplies and never > got around to finalizing the request. > > -- > Mike Orr <[email protected]> > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.seapig.org/pipermail/seattle-python/attachments/20130501/10386942/attachment-0001.html > > > > ------------------------------ > > Message: 5 > Date: Wed, 1 May 2013 14:30:54 -0700 > From: James Thiele <[email protected]> > To: Seattle Python Interest Group <[email protected]> > Subject: Re: [SEAPY] NW Python Day 2013? > Message-ID: > < > cabsnl97dqbowx-wmwlyov19gixfsd7zwwpwzdwiqrq7odnt...@mail.gmail.com> > Content-Type: text/plain; charset="iso-8859-1" > > It won't need a lot of money. Here's an email I dug up: > Northwest Python Day is tomorrow at 9am. Details at > http://seapig.org/NWPD10 . Bring snacks. > > There are $70 in expenses for supplies. There will be a donation box > at the door to cover them. > > > On Wed, May 1, 2013 at 2:14 PM, Kevin LaTona <[email protected]> wrote: > > > > > > > We are starting to get a few sparks going here. > > > > > > Besides AWS, Google and Microsoft what about all the startups we have? > > > > One good way for all these companies to insure they have Python geeks to > > work for them. > > > > Is to help foster and support such an event locally. > > > > > > I wonder if any of them have a developer or community relations person > > that SeaPig could work with to make this happen? > > > > > > I am would think the Python Software Foundation might support it on some > > level or other. > > > > -Kevin > > > > > > > > > > > > > > > -- > Some radio waves were modulated in the creation of this email. > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.seapig.org/pipermail/seattle-python/attachments/20130501/4c2f7243/attachment-0001.html > > > > ------------------------------ > > Message: 6 > Date: Wed, 1 May 2013 14:51:54 -0700 > From: Lion Kimbro <[email protected]> > To: Seattle Python Interest Group <[email protected]> > Subject: Re: [SEAPY] NW Python Day 2013? > Message-ID: > < > caemwhsgc8cwvdcf-ib67yct20ywdhjfqnket1bdoo0mjdtn...@mail.gmail.com> > Content-Type: text/plain; charset="utf-8" > > If this happened, I would be in a deep battle within myself about whether > to spend all my time giving talks, or spending all my time going to talks. > I would need 5 days to begin to reach an equilibrium with my desires... > > Talks & Events I would love to give: > * Improvisational Visionary Programming -- giving life to ideas with Python > * Everyone Can Make a Programming Language in Python -- (Forth > implementations in Python) > * Tkinter is Easy if you Have a Cheat Sheet -- with cheat-sheets included > -- brief lecture, and then obstacle course to try your chops > * String Processing in Python -- strategies for working with strings > * Creating Serialized Object Systems in Python > * How to Debug Python Code -- pdb, emacs > * Write Small Things -- an apology for globals, functions (not objects), > short names, conventions, small modules, demonstrated with a live tear-down > of a module, cutting it's code by 90% > * ... > * ... > > Honestly, if I were to spend a focused hour on this, I think I could create > x60 different talks for this. > > Events that I want to see: > * Mob Programming > * WTF w/ Package Management > > Also: Maybe something like: Men and Women in Python and Programming -- > With a single day's event, it's quite impossible to go deep, and the > subject IS deep, but it is possible for people to give some time to one > another to express something, in a personal albeit limited way, of their > care and thoughts on the subject. > > I think it would be good for there to be a touchstone here, a hint and > recognition of deeper things beneath the surface. I think that if people > can feel some sense of togetherness and connection, that it might help > prevent things like the Donglegate disaster. Perhaps a wall collage would > be a good thing as well, where people can anonymously (or not) write > something of their sentiment. It's a touchy subject, but I think an > important one to give some address to it, too. If it works, it might > become a model for future events in the software world. > > > > On Wed, May 1, 2013 at 11:58 AM, Blibbet <[email protected]> wrote: > > > >> we aren't at the getting people to show level yet -- we're at > > >> the getting someone to find the bandwidth to organize it. > > > > Given the region, perhaps getting MSFT to organize/host it might be an > > option? > > > > 1) They have a fresh new Open Source division, looking for excuses to > > issue PR about good deeds they've involved with. > > > > 2) They have both A) IronPython, B) Python Tools for Visual Studio, and > C) > > Python SDK for Azure, so it is now partially in their interests to > showcase > > their Pythonic goodness. > > > > 3) They have lots of hosting locations, usually with catering and other > > amenenties. :-) > > > > Perhaps some lurking MSFTie could ask (the Open Source division, and/or > > the teams that fund IronPython or PyTools@CodePlex) for some resource > > help? ...Unless others here think that'd be a bad idea. > > > -------------- next part -------------- > An HTML attachment was scrubbed... > URL: < > http://lists.seapig.org/pipermail/seattle-python/attachments/20130501/206f3e48/attachment.html > > > > End of seattle-python Digest, Vol 109, Issue 3 > ********************************************** >
