|
Size: 2423
Comment:
|
Size: 1928
Comment:
|
| 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 7: | Line 6: |
| My prototype of the advocacy site has been fully ported over the advocacy.python.org and checked into svn.python.org. The site is up and down as I'm working on it, however I have established a clone of the site at advocacy.dfwpython.org. The clone will be the development site and advocacy.python.org will be the production site, with a subversion check-in/check-out cycle used to catch the production site up with development. I'm not happy with the colors and layout of the advocacy site but decided to put further tweaking aside and focus on getting all the pieces working so people have something to critique, and so we can start adding content to it. |
|
| Line 14: | Line 9: |
| * Add support for filterable documents to the advocacy site, and come up with a decent presentation layout for said documents. * Establish a subportal under advocacy.python.org for those who want to help promote Python. * 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 19: | Line 24: |
| Existing Challenges: | Existing Challenges (most recent at top): |
| Line 21: | Line 26: |
| * 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 24: | Line 31: |
| Future Tasks: * 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 43: | 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 [http://www.python.org/psf/grants/advocacy/revised-tasks.pdf 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 [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.
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 [http://mail.python.org/mailman/listinfo/advocacy Advocacy mailing list] and visit the [http://advocacy.python.org/getinvolved Advocacy - Get Involved!] site.