Skip to content

Latest commit

 

History

History
70 lines (51 loc) · 2.49 KB

README.md

File metadata and controls

70 lines (51 loc) · 2.49 KB
Raw

PyConUKSociety

This repository contains the constitution, AGM agendas and minutes for the PyCon UK Society.

What is the PyCon UK Society?

The PyCon UK conference is organised using an open mailing list for all the crew to join. If you wish to volunteer to help with PyCon UK 2016, we welcome you! Please feel free to join the conference organiser mailing list.

The PyCon UK Society is the formal organisation behind the UK Python community. The Society exists to promote the Python language in the UK, particularly by organising the PyCon UK conference and associated events, and the Society is legally and financially responsible for those events.

Every year the Society holds an Annual General Meeting, to elect its officers and plan events for the coming year.

The AGM is normally held during the PyCon UK conference, to make it easier for as many people as possible to attend and everyone is welcome.

The committee is a only subset of the organising crew. You do not have to join the committee to be involved in running PyCon UK, however we are particularly keen to have new people join the Society committee.

The current committee

  • Zeth Green (Chair)
  • Mary Mooney (Treasurer)
  • Luke Stanley
  • Sarah Mount
  • Nicholas Tollervey
  • Peter Inglesby
  • Colin Moore-Hill
  • Martin Hellwig
  • Michael Foord

The last AGM

The last AGM was held on 21 September 2014 at The Innovation Centre, Coventry. Minutes of the last AGM are available. The financial statement from the 2014 conference is also available.

The next AGM

The next AGM will be held on Saturday 19th September 2015 14:00 (2pm) at PyCon UK. The agenda for the next AGM is available.

How to contribute

We welcome pull requests for AGM agenda items or corrections to the minutes. Please see CONTRIBUTING.md for details.

Please use the following process to submit changes:

  • Fork this repository.
  • Create a descriptive branch name for the change you are proposing.
  • Make your changes.
  • Push your changes in your local branch back to your remote GitHub repository.
  • In GitHub, create a pull request from your branch against our upstream repository.
  • Someone (usually the Chair or Secretary) will check the change and either merge it or add comments for further changes or a reason for rejection.

That's it!

:-)