| | 1 | = CTPUG Planning Meeting 2009/11/28 minutes = |
| | 2 | |
| | 3 | Present: nitwit, jerith, hodgestar, confluence, edward, davidfraser |
| | 4 | |
| | 5 | == Now == |
| | 6 | |
| | 7 | * Talks |
| | 8 | * !PyWeek |
| | 9 | * Bug Days |
| | 10 | * Euler Problems |
| | 11 | |
| | 12 | == Next Year == |
| | 13 | |
| | 14 | * World cup |
| | 15 | * Tutorials |
| | 16 | |
| | 17 | == Tutorials == |
| | 18 | |
| | 19 | * Workshops rather than courses |
| | 20 | * SudoRoom calendar - up to 6 people per course |
| | 21 | * Spaces should be used by people who need to learn, rather than people who already know |
| | 22 | * Instructors offer various topics, decide charge per seat |
| | 23 | * SudoRoom will take 40% of income (including if it's a free course) |
| | 24 | * Edward will set up payment gateways, handle that whole thing |
| | 25 | |
| | 26 | === Topics === |
| | 27 | |
| | 28 | * How do you find out what people want? |
| | 29 | * Schedule and scope dependent on instructors |
| | 30 | * Python for non-Python programmers - could be run regularly |
| | 31 | * Perhaps a rolling schedule or 4 lessons etc? |
| | 32 | * Basic syntax |
| | 33 | * Topics for target implementation - C, Java, .NET, PHP/Perl people |
| | 34 | * Standard library/modules - Web / DB / GUI |
| | 35 | * Python for non-programmers - how to program, using Python |
| | 36 | |
| | 37 | === Format === |
| | 38 | |
| | 39 | * Introduction |
| | 40 | * Choose three little tasks people want to do (e.g. web form to email) |
| | 41 | * Give people scope to do one or more of them |
| | 42 | * Instructor helps people through the material |
| | 43 | |
| | 44 | == Bug Days == |
| | 45 | |
| | 46 | * Something we should keep doing |
| | 47 | * Success rate is not great |
| | 48 | * But some fixes did get in |
| | 49 | * We had fun |
| | 50 | * It helps to have commit access to what you're going to hack on, somebody who's actually a developer |
| | 51 | * !ElementTree bug day - needed tests added - main developer has his own entire branch, so got stonewalled |
| | 52 | * Should hook up with Stefan van der Walt on scipy stuff |
| | 53 | * Could potentially do Bitten bug day - both davidfraser and Hodgestar have commit access |
| | 54 | |
| | 55 | == Talks == |
| | 56 | |
| | 57 | * Interesting problem + solution |
| | 58 | * Interesting library |
| | 59 | * After-talk discussion |
| | 60 | * Recent events in the Python world (maybe better as after-talk discussion) |
| | 61 | |
| | 62 | == !PyWeek == |
| | 63 | |
| | 64 | * Probably not the first one next year (February/March), perhaps the next one |
| | 65 | |
| | 66 | == Advocacy == |
| | 67 | |
| | 68 | * How to advertise the Python community a bit more? |
| | 69 | * Piggy back on CLUG? |
| | 70 | * How do you find the people who might be interested but aren't part of the community yet? |
| | 71 | * What about Windowsy Python people |
| | 72 | * Python talks in other forums |
| | 73 | * e.g. [http://www.spin.org.za/ SPIN] |
| | 74 | * Microsoft developers |
| | 75 | * Find other groups |
| | 76 | * Process - group development of talks (even if single presenter) - collective expertise |
| | 77 | * University students? engineering / physics / comp sci / bioinformatics / drama |
| | 78 | * Corporates? |
| | 79 | |
| | 80 | == Web site == |
| | 81 | |
| | 82 | * Upfront Systems could continue to host but would keep us on Plone, and none of those present can maintain this |
| | 83 | * Nitwit would rather have CTPUG hosting with someone we can easily get hold of |
| | 84 | * We have offer of hosting space with Edward - small Linode box |
| | 85 | * Domain name ctpug.org.za |
| | 86 | * Feeling is we should give everyone at this meeting admin access for everything |
| | 87 | * davidf to set up fsvs |
| | 88 | * mailing list notification on changes |
| | 89 | |
| | 90 | Basic plan: |
| | 91 | * Set up version control + trac specifically for use on bug days |
| | 92 | * wiki, overview etc |
| | 93 | * Need to set up layout for version control |
| | 94 | * Distributed version control? |
| | 95 | * options are mercurial, bzr, git |
| | 96 | * best to setup with bare repository |
| | 97 | * mercurial is what Python will be using |
| | 98 | * bzr is what launchpad uses |
| | 99 | * we need multiple repository support in trac - easiest to do this with multiple projects |
| | 100 | * bug days don't need as much support from trac |
| | 101 | * if all working in a room, makes more sense to have repository local |
| | 102 | * trac + single svn repository would be simple for filesystem to keep code in |
| | 103 | * way of sending mail out - notifications etc |
| | 104 | * calendar would be useful - probably best with a calendar plugin |
| | 105 | * probably need spam editing |
| | 106 | |
| | 107 | == Other ideas == |
| | 108 | |
| | 109 | * Conferences - PyCON 2010 (Atlanta in February - nah), EuroPython (Birmingham?), PyCon Asia Pacific (June Singapore) |
| | 110 | * Evening discussions - smaller group in coffee shop? (e.g. Touch of Madness) |
| | 111 | * Shootouts of equivalent libraries - web frameworks, database, etc |
| | 112 | |
| | 113 | == Effort targeting == |
| | 114 | |
| | 115 | * Tutorials - complaints on the list about talks being too high-level |
| | 116 | * Bug days - but make them focused |
| | 117 | * Replace normal meetings with a bug day / talk to another group |
| | 118 | * Meeting where main purpose is to talk to Python developers + something else happening |
| | 119 | * Talk on a topic |
| | 120 | * Planning for a presentation to another group |
| | 121 | * Could have open mic python meetings where there's space to discuss planning etc |
| | 122 | * Talks provide for an excuse for people to come to a meeting |
| | 123 | |
| | 124 | |
| | 125 | ''Minutes by David Fraser'' |
