Differences between revisions 34 and 40 (spanning 6 versions)
Revision 34 as of 2007-08-20 14:12:45
Size: 2060
Editor: 202
Comment:
Revision 40 as of 2008-11-15 13:59:54
Size: 1968
Editor: localhost
Comment: converted to 1.6 markup
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
The idea of connecting Python developers on [http://www.linkedin.com/ LinkedIn] originated in a message sent by Tennessee Leeuwenburg to the python advocacy mailing list. Here are Tennessee's words: The idea of connecting Python developers on [[http://www.linkedin.com/|LinkedIn]] originated in a message sent by Tennessee Leeuwenburg to the python advocacy mailing list. Here are Tennessee's words:
Line 3: Line 3:
"One way to help spread Python would be to have a strong presence of Python developers in various online networks. One that springs to mind is [http://www.linkedin.com/ LinkedIn], a job related social networking site. "One way to help spread Python would be to have a strong presence of Python developers in various online networks. One that springs to mind is [[http://www.linkedin.com/|LinkedIn]], a job related social networking site.
Line 5: Line 5:
If we could encourage Python developers to start adding each other to their [http://www.linkedin.com/ LinkedIn] network, then we shoud be able to create a well-connected developer network with business and industry contacts. This should benefit everyone -- both people looking for Python developers, and also people looking for work." If we could encourage Python developers to start adding each other to their [[http://www.linkedin.com/|LinkedIn]] network, then we should be able to create a well-connected developer network with business and industry contacts. This should benefit everyone -- both people looking for Python developers, and also people looking for work."
Line 7: Line 7:
Here is a list of Python developers who have a presence on [http://www.linkedin.com/ LinkedIn]: The best solution would be to create a [[http://www.linkedin.com/|LinkedIn]] Group (http://www.linkedin.com/static?key=groups_faq) for python developers, rather than indidually adding dozens or hundreds of people (which is not really an option anyway for those who prefer to use [[http://www.linkedin.com/|LinkedIn]] to organize people they have actually met).
Line 9: Line 9:
 * Tennessee Leeuwenburg
 * Grig Gheorghiu (grig at gheorghiu dot net)
 * Peter Kropf
 * Mark Ramm
 * Stephan Deibel
 * Bugra Cakir
 * Henrik Lied
 * Graham Higgins
 * Michael Foord (fuzzyman at voidspace dot org dot uk - also on Facebook)
 * Alessandro Iob (alessandro dot iob at dlevel dot com)
 * Stephen Vermeulen
 * Lutz Horn
 * Victor Ng
 * Lawrence Oluyede
 * Simon Wittber
 * Dorai Thodla
 * Mark Mc Mahon
 * Noah Kantrowitz
 * Mayowa Akinyemi (mayowa at g m a i l dot com)
 * James Tauber
 * Calvin Spealman (ironfroggy . g mail @ com)
 * Ian Sparks
 * Florent Aide (florent d-o-t aide a_t gm ail d_ot com)
 * Kent Johnson
 * Pim Van Heuven
 * Siddharta Govindaraj
 * Tom Vergote
 * Jesse Noller ( jnoller a_t gma il do*t com)
 * Stephane Martin (stephane dot martin at m4x dot org)
 * John Clark (clajo04 a_t mac do*t com)
 * Jeremy Cantrell (jmcantrell at gmail dot com)
 * Scott Schwab (scott.schwab at gmail dot com)
 * Anand Balachandran (abpillai at gmail dot com)
LinkedIn for Groups is not currently adding any more groups. One alternative is to add "Python Community" to your "Groups and Associations" in the Additional Information part of your profile. You can then be found within LinkedIn by searching for people associated with the "Python Community."
Line 43: Line 11:
If you are a Python developer with a [http://www.linkedin.com/ LinkedIn] profile, please add yourself to the list and invite the other people on the list into your connection network. But if you prefer to add individuals there is a list of LinkedInPythonIndividuals.

'''UDPATE:'''

You can now join the [[http://www.linkedin.com/e/gis/25827/3B50BC189075|LinkedIn Group "Python Community"]]. This makes it easier to separate Python individuals (some maybe less or unknown to you) from your "personal" contacts. See also the [[http://www.linkedin.com/static?key=groups_faq|LinkedIn Groups Members FAQ]] and [[http://www.linkedin.com/static?key=groups_faq_administrators|LinkedIn Groups Admin FAQ]] - (Danny W. Adair)

The idea of connecting Python developers on LinkedIn originated in a message sent by Tennessee Leeuwenburg to the python advocacy mailing list. Here are Tennessee's words:

"One way to help spread Python would be to have a strong presence of Python developers in various online networks. One that springs to mind is LinkedIn, a job related social networking site.

If we could encourage Python developers to start adding each other to their LinkedIn network, then we should be able to create a well-connected developer network with business and industry contacts. This should benefit everyone -- both people looking for Python developers, and also people looking for work."

The best solution would be to create a LinkedIn Group (http://www.linkedin.com/static?key=groups_faq) for python developers, rather than indidually adding dozens or hundreds of people (which is not really an option anyway for those who prefer to use LinkedIn to organize people they have actually met).

LinkedIn for Groups is not currently adding any more groups. One alternative is to add "Python Community" to your "Groups and Associations" in the Additional Information part of your profile. You can then be found within LinkedIn by searching for people associated with the "Python Community."

But if you prefer to add individuals there is a list of LinkedInPythonIndividuals.

UDPATE:

You can now join the LinkedIn Group "Python Community". This makes it easier to separate Python individuals (some maybe less or unknown to you) from your "personal" contacts. See also the LinkedIn Groups Members FAQ and LinkedIn Groups Admin FAQ - (Danny W. Adair)

LinkedInPythonNetwork (last edited 2008-11-15 13:59:54 by localhost)

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