Differences between revisions 6 and 7
Revision 6 as of 2006-11-13 12:38:06
Size: 2807
Editor: adsl-68-95-132-152
Comment:
Revision 7 as of 2006-12-04 18:30:38
Size: 2971
Editor: adsl-68-95-132-152
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"].
Line 12: Line 11:
 * Put candidate PyCon slogans onto poll site and let the community vote.
 * Participate in final selection of PyCon talks and timeslot assignment.
 * Write up authoring guidelines, for web content, whitepapers
   and flyers, so as others contribute documentation, it is
   consistent in appearance and tone.
Line 15: Line 15:
 * Get vector format of PyCon logo to the graphic designer.
Line 19: Line 18:
Existing Challenges: Existing Challenges (most recent at top):
Line 21: Line 20:
 * I have been spending (too much) time on PyCon and need to refocus on other forms of advocacy.
 * I have found a huge amount of really great Python material scattered on sites and am trying to organize/link it into the advocacy site. A good situation to be in but a lot of reading and evaluating.
Line 22: Line 23:
 * I have found a huge amount of really great Python material scattered on sites and am trying to organize/link it into the advocacy site. A good situation to be in but a lot of reading and evaluating.
Line 25: Line 25:
Future Tasks: Future Tasks (in order of priority, from most urgent to least):
Line 31: Line 31:
 * Further restyling of us.pycon.org website
 * Install the python api for subversion, so I can directly manipulate repositories, as needed.
 * Finish processing the audio recordings from past !PyCons.
Line 34: Line 33:
 * Finish processing the audio recordings from past !PyCons.
Line 41: Line 39:
    * 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]
 * Further restyling of us.pycon.org website
 * Install the python api for subversion, so I can directly manipulate repositories, as needed.
Line 47: Line 43:
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.
----

In mid-2006, the PSF agreed to hire JeffreyRush for full-time work on ["Advocacy"].


["AdvocacyAccomplishments"]

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.


Current Tasks:

  • Write up authoring guidelines, for web content, whitepapers
    • and flyers, so as others contribute documentation, it is consistent in appearance and tone.
  • Add additional content to the advocacy site re answering common questions from the perspective of various audiences.
  • Get my installation of Pyramid working and begin adding links from www.python.org to the advocacy site.


Existing Challenges (most recent at top):

  • I have been spending (too much) time on PyCon and need to refocus on other forms of advocacy.

  • I have found a huge amount of really great Python material scattered on sites and am trying to organize/link it into the advocacy site. A good situation to be in but a lot of reading and evaluating.
  • An Apache process on ximinez.python.org machine was leaking memory and swapping like crazy, slowing everything considerable. Sean R. changed Apache from a threading to a process model and the problem has not reoccurred.


Future Tasks (in order of priority, from most urgent to least):

  • Refine component for organizing advocacy files; collapse documents in different formats into one entry with format icons; provide an upload link into a quarantine area, provide for searching for tagged files re all slide presentations, all flyer handouts, etc.
  • Implement a component to establish a database of user groups,
    • with an RSS feed and searchable by geographic location.
  • Ping pydotorg for site statistics, if they already exist.
  • Finish processing the audio recordings from past PyCons.

  • Figure out how to integrate Nabu with subversion, such that documents maintain an audit trail.
  • 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.
  • Further restyling of us.pycon.org website
  • Install the python api for subversion, so I can directly manipulate repositories, as needed.


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.


CategoryAdvocacy

PythonAdvocacyCoordinator (last edited 2008-11-15 14:00:14 by localhost)

Unable to edit the page? See the FrontPage for instructions.