Differences between revisions 1 and 16 (spanning 15 versions)
Revision 1 as of 2012-10-23 10:29:41
Size: 5717
Editor: MarcAndreLemburg
Comment: wiki restore 2013-01-23
Revision 16 as of 2014-02-26 20:50:43
Size: 7554
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
Line 4: Line 3:

The Python events calendar is a group of Google calendars maintained by volunteers and published on the following sites:
The ''Python events calendar'' is a combination of Google calendars maintained by the Python Calendar Team and published on the following sites:
Line 11: Line 8:
<<TableOfContents()>>
Line 12: Line 10:
If you would like to get new events listed on these calendars, please write to events@pycon.org mentioning the name of the event, the dates/times and a URL. For recurring events, please also include the recurrence information. == Submitting an Event ==
Line 14: Line 12:
If you would like to get new events listed on these calendars, please write to events@python.org mentioning:
Line 15: Line 14:
If you'd like to embed the calendar into your site, please ping us at the above address before doing so.  * the name of the event (including the user group name for user group events)
 * type of event (conference, bar camp, sprint, user group meeting, etc.)
 * focus on Python and approximate size (number of attendees)
 * the location (venue address, including city and ''country'')
 * the dates/times (including the time zone)
 * a URL with more details for the event (using the format "<a href="http://url/">name of the event</a>")
Line 17: Line 21:
For recurring events, please also include the recurrence information.
Line 18: Line 23:
== Available calendars == /!\ Please leave ''at least a week notice'' when submitting events. The calendar team is volunteer driven. While we try to add new events swiftly, we cannot guarantee response times.
Line 20: Line 25:
== Available Calendars ==
Line 27: Line 33:

Line 30: Line 34:
Line 35: Line 38:
Line 37: Line 39:
Line 42: Line 43:
== Twitter Feed ==
Line 43: Line 45:
== Administration ==  * [[https://twitter.com/PythonEvents|@PythonEvents]]
Line 45: Line 47:
 This Twitter account automatically gets all new entries from both calendars as tweets. The triggering is setup using [[https://ifttt.com/|IFTTT]]. Note that changes to the calendar entries are not reported on the Twitter feed. This appears to be a limitation of the IFTTT trigger.

== Embedding Calendars ==

If you'd like to embed the calendar into your site, please ping us at events@python.org before doing so. We'd like to keep a list of sites where the calendars are displayed.

You can find the embedding code further below on this page.

=== Known sites embedding the calendars ===

 * http://python.org/ - in the side bar of the site
 * http://pycon.org/ - on the front page
 * http://dehradunpython.com/

== Python Calendar Team ==
Line 47: Line 64:
Line 53: Line 69:
 * Skip Montanaro
Line 55: Line 72:
=== Mailing List ===

The team uses the python-events mailing list for discussion and to process events. The events@python.org address is an alias for the python-events mailing list.

 * https://mail.python.org/mailman/listinfo/python-events
Line 58: Line 80:
Line 60: Line 81:
Line 67: Line 87:
Line 73: Line 94:

All calendar admins can invite more people as calendar admins. When doing so, please add the new admins to the above list and ping the team by writing to events@pycon.org (also to get their email address added to the events@ alias).
All calendar admins can invite more people as calendar admins. When doing so, please add the new admins to the above list and ping the team by writing to events@python.org (also to get their email address added to the python-events mailing list).
Line 79: Line 98:
Line 82: Line 100:
Line 84: Line 101:
Line 89: Line 105:
 * The calendars should only list the events themselves. CFP deadlines, registration openings or similar announcements should not be listed in the calendars.
Line 93: Line 109:

* Python Events Calendar: This calendar should only receive entries for conferences of at least around 100 attendees, which at least around a 3rd non-local attendees. Smaller events such as sprints may also be added to this calendar if they are scheduled as separate event and will have a significant impact.
 * Python Events Calendar: This calendar should only receive entries for conferences of at least around 100 attendees, which at least around a 3rd non-local attendees. Smaller events with at least around 30 attendees such as sprints, barcamps or smaller unconferences may also be added to this calendar if they are scheduled as separate event, will have a significant impact and reach out to larger regions.
Line 97: Line 112:

* Python User Group Calendar: This calendar is meant for user group activities which are open to Python people from outside the group (new prospective members and visitors from out of town). It is not meant for user group internal events. Examples: monthly local user group meetings, project sprints that are open for non-group members
 * Python User Group Calendar: This calendar is meant for user group activities which are open to Python people from outside the group (new prospective members and visitors from out of town). It is not meant for user group internal events.
Examples: monthly local user group meetings, project sprints that are open for non-group members.
Line 103: Line 117:
Line 106: Line 119:

 .
Line 115: Line 126:

Line 119: Line 128:

* [[https://developers.google.com/google-apps/calendar/v2/reference|Google Calendar API v2 Atom Reference]]
  
. This describes the available RSS feed options available on the Google calendar feed links.
 * [[https://developers.google.com/google-apps/calendar/v2/reference|Google Calendar API v2 Atom Reference]]. This describes the available RSS feed options available on the Google calendar feed links.

Python Events Calendar

The Python events calendar is a combination of Google calendars maintained by the Python Calendar Team and published on the following sites:

Submitting an Event

If you would like to get new events listed on these calendars, please write to events@python.org mentioning:

  • the name of the event (including the user group name for user group events)
  • type of event (conference, bar camp, sprint, user group meeting, etc.)
  • focus on Python and approximate size (number of attendees)
  • the location (venue address, including city and country)

  • the dates/times (including the time zone)
  • a URL with more details for the event (using the format "<a href="http://url/">name of the event</a>")

For recurring events, please also include the recurrence information.

/!\ Please leave at least a week notice when submitting events. The calendar team is volunteer driven. While we try to add new events swiftly, we cannot guarantee response times.

Available Calendars

iCal Downloads

RSS Feeds

Twitter Feed

  • @PythonEvents

    This Twitter account automatically gets all new entries from both calendars as tweets. The triggering is setup using IFTTT. Note that changes to the calendar entries are not reported on the Twitter feed. This appears to be a limitation of the IFTTT trigger.

Embedding Calendars

If you'd like to embed the calendar into your site, please ping us at events@python.org before doing so. We'd like to keep a list of sites where the calendars are displayed.

You can find the embedding code further below on this page.

Known sites embedding the calendars

Python Calendar Team

The following people currently have admin rights to the calendars:

  • Richard Jones
  • Mike Müller
  • Tarek Ziade
  • Tetsuya Morimoto
  • Skip Montanaro
  • Marc-Andre Lemburg

Mailing List

The team uses the python-events mailing list for discussion and to process events. The events@python.org address is an alias for the python-events mailing list.

Notes regarding calendar entries

Some notes regarding entries for the admins:

  • Please add the conference/event year to the title, if available. For user group meetings or other events that occur more often that's probably not necessary.
  • For conferences I use "All day" events, for user group events I add the start time and end time, if known.
  • Please include the location as "City, Country".
  • Please add a link to the event as description. I found that using HTML links works well, e.g. <a href="http://www.pycon.fr/2012/>PyCon FR 2012</a>

  • I've always used "Show me as: Available" for new entries. No idea whether that matters or not.
  • Please select "Privacy: Default" for new entries. This makes the entries public, since that's the default setting.

All calendar admins can invite more people as calendar admins. When doing so, please add the new admins to the above list and ping the team by writing to events@python.org (also to get their email address added to the python-events mailing list).

Guidelines for entries

In order to make the decision of whether to add an event and where to add it easier, we've setup a few guidelines:

General Requirements

  • Events have to have some focus on Python: The event should either target Python, a project written in Python, or showcase Python in some form.

    Examples are Python conferences, conferences which have a Python track or tutorial, conferences at which Python is presented in some form. The same goes for conferences which target a project written mostly in Python (e.g. Plone, Django, OpenStack, etc.) and for other events such as sprints.

  • The calendars should only list the events themselves. CFP deadlines, registration openings or similar announcements should not be listed in the calendars.

Calendar Choice

  • Python Events Calendar: This calendar should only receive entries for conferences of at least around 100 attendees, which at least around a 3rd non-local attendees. Smaller events with at least around 30 attendees such as sprints, barcamps or smaller unconferences may also be added to this calendar if they are scheduled as separate event, will have a significant impact and reach out to larger regions.

    Examples: PyCon conferences, OSCON, Django conferences, Plone conference, Need-for-speed sprints, Python BarCamps/Unconferences/etc.

  • Python User Group Calendar: This calendar is meant for user group activities which are open to Python people from outside the group (new prospective members and visitors from out of town). It is not meant for user group internal events. Examples: monthly local user group meetings, project sprints that are open for non-group members.

Calendar embedding code

This iframe code is used on pycon.org to display the calendar:

  • <iframe src="https://www.google.com/calendar/embed?showTitle=0&amp;showCalendars=0&amp;height=400&amp;wkst=2&amp;bgcolor=%23FFFFFF&amp;src=j7gov1cmnqr9tvg14k621j7t5c%40group.calendar.google.com&amp;color=%23125A12&amp;src=3haig2m9msslkpf2tn1h56nn9g%40group.calendar.google.com&amp;color=%232F6309&amp;ctz=Europe%2FLondon" style=" border-width:0 " width="800" height="450" frameborder="0" scrolling="no">
      <a href="https://www.google.com/calendar/ical/j7gov1cmnqr9tvg14k621j7t5c%40group.calendar.google.com/public/basic.ics">Python Events iCal Calendar</a><br/>
      <a href="https://www.google.com/calendar/ical/3haig2m9msslkpf2tn1h56nn9g%40group.calendar.google.com/public/basic.ics">Python User Group iCal Calendar</a>
    </iframe>

Resources

PythonEventsCalendar (last edited 2020-02-27 09:18:53 by MarcAndreLemburg)

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