addressalign-toparrow-leftarrow-rightbackbellblockcalendarcameraccwcheckchevron-downchevron-leftchevron-rightchevron-small-downchevron-small-leftchevron-small-rightchevron-small-upchevron-upcircle-with-checkcircle-with-crosscircle-with-pluscrossdots-three-verticaleditemptyheartexporteye-with-lineeyefacebookfolderfullheartglobegmailgooglegroupshelp-with-circleimageimagesinstagramFill 1linklocation-pinm-swarmSearchmailmessagesminusmoremuplabelShape 3 + Rectangle 1ShapeoutlookpersonJoin Group on CardStartprice-ribbonShapeShapeShapeShapeImported LayersImported LayersImported Layersshieldstartickettrashtriangle-downtriangle-uptwitteruserwarningyahoo

Re: [dfwPython] DFW Python mtg schedule Sat May 8

From: Sheila A.
Sent on: Sunday, May 16, 2010 3:15 PM
Some notes from the last Sat meeting:

* There were 10 attendees
* Jeremy L. gave a great introductory presentation on Eclipse + pydev
(this may be repeated or expanded upon for the upcoming DFW Python
'Editor/IDE tools day'.
* During the "User Group Business" segment, we discussed several things:
    -- Some members at the meeting indicated that they joined due to
the presence on, but were unaware of the main DFW Python
mailing list. Jeff now has a to-do item to correct that on the meetup
site, by making the mailing list more prominent.
    -- Jeremy L. wants to lead a group project to create a DFW Python
user group website with some dynamic features. After discussing
requirements with the group, he is putting together a spec. This is
probably going to be a Django site, since the largest number of group
members are enthusiastic about working in Django. Several members
present said they would participate if Jeremy would lead the project.
Stay tuned for more discussion about the features planned for the
    -- Everybody seemed to agree that the current DFW Python wiki has
become a bit of a mess. Managing a wiki requires an active community,
and our DFW Python website requirements seem more oriented toward
advertising the meetings and community links. A wiki may not be the
best fit. However, it's what we have today, and Rusty agreed to help
do some cleanup to get it in order as a short term solution for the
    -- We decided to split the "tools day" meeting into two separate
meetings, one day for editors/IDEs and one day dedicated for debugging
tools. We set June 12 as the tentative for 'Editor day', to give
everyone plenty of time to polish their talks. 'Debugger day' has not
yet been set.

Our Sponsors

People in this
Meetup are also in:

Sign up

Meetup members, Log in

By clicking "Sign up" or "Sign up using Facebook", you confirm that you accept our Terms of Service & Privacy Policy