Differences between revisions 27 and 29 (spanning 2 versions)
Revision 27 as of 2006-12-05 15:56:14
Size: 3987
Editor: adsl-68-95-132-152
Comment: added link to a new page I'm creating re writing guidelines
Revision 29 as of 2006-12-07 09:44:42
Size: 4781
Editor: JeffRush
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Greetings! I'm the PythonAdvocacyCoordinator. You can reach me via email at [[MailTo(advocate AT python DOT org)]]. I'm always glad to hear ideas or corrections.

Want to help with some writing? Check out our list of whitepaper/flyer AdvocacyWritingTasks or magazine ArticleIdeas.
Line 7: Line 11:
 * PythonAdvocacyCoordinator === Python Advocacy Kits ===

 * [wiki:/CollegeStudentKit College Student's Python Advocacy Kit] (being developed)
 * [wiki:/ItDepartmentKit IT Department Python Advocacy Kit] (being developed)
 * [wiki:/UniversityEducatorKit University Educator's Python Advocacy Kit] (being developed)
 * [wiki:/K12EducatorKit K-12 Educator's Python Advocacy Kit] (being developed)
 * [wiki:/ResearchLabKit Research Lab Python Advocacy Kit] (being developed)

=== Teaching Materials ===

 * [wiki:/SlidePresentations Excellent Slide Presentations]
 * [wiki:/ClasHandouts Class Handouts]

=== Other Resources ===
Line 9: Line 27:
 * AdvocacyWritingGuide - styleguide for authoring advocacy materials
 * ArticleIdeas
Line 21: Line 37:
Please send me (advocate at python dot org) any files that might be useful for giving out at user groups or business meetings. Please send me [[MailTo(advocate AT python DOT org)]] any files that might be useful for giving out at user groups or business meetings.


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.


Greetings! I'm the PythonAdvocacyCoordinator. You can reach me via email at MailTo(advocate AT python DOT org). I'm always glad to hear ideas or corrections.

Want to help with some writing? Check out our list of whitepaper/flyer AdvocacyWritingTasks or magazine ArticleIdeas.

Advocacy Resources

Python Advocacy Kits

Teaching Materials

Other Resources

Please send me MailTo(advocate AT python DOT org) any files that might be useful for giving out at user groups or business meetings.

Existing material appears (also) at ["evangelism_support_materials"] and PromotingPythonBof. Note [http://psf.pollenation.net/cgi-bin/trac.cgi/ticket/160].

General Notes

Advocacy is the process of letting people know what Python is good at, and drawing them into using the language. The most effective forms of advocacy lure users to the language by impressing them with results, rather than brow beating or lecturing them on language design.

Published articles that answer the question "how do I solve X with Python?" are a good way to get people interested.

One goal for writing articles might be to develop a library of How-Tos for Python. Much information exists, but it has not been collected for convenient access from python.org (or another central location), and there are certainly gaps in covering key strengths of Python.

A collection of [http://python.org/about/success Python Success Stories] already exists. These are also useful, usually by helping engineers convince their bosses that Python is worthy of attention. But success stories tend to be lean on "how-to" style information, so they do not offer a convenient path to get new users working with Python.

Since the goal for advocacy is to highlight Python's strengths, [http://wingware.com/python this Key Strengths list] may be useful.

We would like to focus on those magazines outside the Python community, in order to reach those who don't know about us. Also there are many magazines that accept press releases that do not accept articles. We need those that welcome articles.

Electronic Magazines that Accept Technical Articles

CategoryAdvocacy

Advocacy (last edited 2009-10-30 02:22:47 by panix3)

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