|
Size: 2536
Comment:
|
← Revision 17 as of 2008-11-15 14:00:14 ⇥
Size: 1936
Comment: converted to 1.6 markup
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| In mid-2006, the PSF agreed to hire JeffreyRush for full-time work on ["Advocacy"]. |
In mid-2006, the PSF agreed to hire JeffreyRush for full-time work on [[Advocacy]]. The contract was renewed for another six months starting March 15, 2007, along with a [[http://www.python.org/psf/grants/advocacy/revised-tasks.pdf|list of tasks to tackle]]. |
| Line 5: | Line 4: |
| ["AdvocacyAccomplishments"] | [[AdvocacyAccomplishments]] |
| Line 10: | Line 9: |
| * Migrate over the prototype portal from advocacy.dfwpython.org to advocacy.python.org. * Establish a subportal under advocacy.python.org for those who want to help promote Python. * Gain access to the correct portion of Python SVN to hold my creations, both software and content. * Make announcment re advocacy onto CLP and CLPA. |
* Produce more "5-Minutes with Python" screencasts -- I've produced nine screencasts so far (not all 5-min though). * Python, Numbers and Array Processing * Python and Strings * Python and the Imaging Library * Python and Relational Databases * Python and Object Databases * Python and Scientific Computing * Work on "Starting and Running a Successful Python User Group" paper, with select members of the Usergroup Support Committee who have volunteered to help. * Hold another online meeting of the Usergroup Support Committee. * Use the [[http://www.dfwpython.org:8000/|www.python.org mockup area]] to test some proposed changes, re a "spotlight" topic and a "get involved" feature, and get feedback from the community. * Decide how to create a "spotlight" box on www.python.org, in consultation with the pydotorg group. * Decide how to create a "get involved" box on www.python.org, in consultation with the pydotorg group. |
| Line 16: | Line 24: |
| Existing Challenges: | Existing Challenges (most recent at top): |
| Line 18: | Line 26: |
| * Consider which versions of software to use on the site; there is some push to use Python 2.5 as well as the just-released Zope 3.3.0, except that Zope3 doesn't work with 2.5 without patches (and maybe more). There are also version issues to resolve re psycopg1 vs psycopg v2, and which SVN revision of psycopgda to bridge between Zope3 and psycopg. And last there is a question of which version of Nabu to use, the last release of Dec 2005 or a more recent snapshot from subversion. * Consider the correct directory and subversion layout to achieve separation of content from software written specifically for advocacy. * Consider whether to style the advocacy site exactly like www.python.org or to vary it either slightly (like us.pycon.org) or significantly. A quiet look is good for those who come to a site frequently but something a bit louder can be useful to excite those who show up for the first time. The louder site may tend to annoy those who must see it again and again. |
* crunching a talk down into only 5-minutes - it is surprisingly difficult * figuring out why threads I start re advocacy and usergroups die out, lacking persistence. * why no response pretty much at all to the repeated calls for podcasts and screencasts -- why is the community so averse to multimedia? |
| Line 25: | Line 31: |
| Future Tasks: * Put out call for !PyCon talk and tutorial ideas; post my suggestion list. * Ping pydotorg for site statistics, if they already exist. * Further restyling of us.pycon.org website * Install the python api for subversion, so I can directly manipulate repositories, as needed. * Figure out how to integrate Nabu with subversion, such that documents maintain an audit trail. * Finish processing the audio recordings from past !PyCons. * Encourage adoption of a standard presentation template for !PyCon. * For !PyCon: * rename Apache rewrite rule from "apps" to "apps06". * rename fastcgi start/stop scripts to have "06" in them. * rename the django/pycon directory to django/pycon06 * update the sudo config for the renamed files. * help Doug chg password for the pycon06 DB. -------- For active discussion on advocating for Python, please join the mailing list at [http://mail.python.org/mailman/listinfo/advocacy] |
For active discussion on advocating the use of Python, please join the [[http://mail.python.org/mailman/listinfo/advocacy|Advocacy mailing list]] and visit the [[http://advocacy.python.org/getinvolved|Advocacy - Get Involved!]] site. |
| Line 45: | Line 33: |
| CategoryAdvocacy | CategoryAdvocacy CategoryAdvocacy |
In mid-2006, the PSF agreed to hire JeffreyRush for full-time work on Advocacy. The contract was renewed for another six months starting March 15, 2007, along with a list of tasks to tackle.
Current Tasks:
- Produce more "5-Minutes with Python" screencasts -- I've produced nine screencasts so far (not all 5-min though).
- Python, Numbers and Array Processing
- Python and Strings
- Python and the Imaging Library
- Python and Relational Databases
- Python and Object Databases
- Python and Scientific Computing
- Work on "Starting and Running a Successful Python User Group" paper, with select members of the Usergroup Support Committee who have volunteered to help.
- Hold another online meeting of the Usergroup Support Committee.
Use the www.python.org mockup area to test some proposed changes, re a "spotlight" topic and a "get involved" feature, and get feedback from the community.
- Decide how to create a "spotlight" box on www.python.org, in consultation with the pydotorg group.
- Decide how to create a "get involved" box on www.python.org, in consultation with the pydotorg group.
Existing Challenges (most recent at top):
- crunching a talk down into only 5-minutes - it is surprisingly difficult
- figuring out why threads I start re advocacy and usergroups die out, lacking persistence.
- why no response pretty much at all to the repeated calls for podcasts and screencasts -- why is the community so averse to multimedia?
For active discussion on advocating the use of Python, please join the Advocacy mailing list and visit the Advocacy - Get Involved! site.