pyconuk / documentation Goto Github PK

Running the preview command has suddenly stopped working for me. (By "suddenly", I mean "sometime in the last week and I don't think I've done anything silly".)

Here's the output I get:

11:30:47 ~/pyconuk/internaldocs $ tox -e preview
preview create: /Users/peteringlesby/pyconuk/internaldocs/.tox/preview
preview installdeps: -r/Users/peteringlesby/pyconuk/internaldocs/requirements.txt
preview installed: alabaster==0.7.7,argh==0.26.1,Babel==2.2.0,docutils==0.12,Jinja2==2.8,livereload==2.4.1,MarkupSafe==0.23,pathtools==0.1.2,Pygments==2.1,pytz==2015.7,PyYAML==3.11,six==1.10.0,snowballstemmer==1.2.1,Sphinx==1.3.1,sphinx-autobuild==0.5.2,sphinx-rtd-theme==0.1.9,tornado==4.3,watchdog==0.8.3,wheel==0.26.0
preview runtests: PYTHONHASHSEED='3886976382'
preview runtests: commands[0] | make preview
sphinx-build -b dirhtml -d build/doctrees   source build/dirhtml
Running Sphinx v1.3.1
loading pickled environment... failed: build environment version not current
building [mo]: targets for 0 po files that are out of date
building [dirhtml]: targets for 5 source files that are out of date
updating environment: 5 added, 0 changed, 0 removed
reading sources... [ 20%] 2015-in-numbers
reading sources... [ 40%] dates
reading sources... [ 60%] index
reading sources... [ 80%] publicity
reading sources... [100%] wash-up-meeting-report

looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [ 20%] 2015-in-numbers
writing output... [ 40%] dates
writing output... [ 60%] index
writing output... [ 80%] publicity
writing output... [100%] wash-up-meeting-report

generating indices... genindex
writing additional pages... search
copying static files... WARNING: html_static_path entry '/Users/peteringlesby/pyconuk/internaldocs/source/_static' does not exist
done
copying extra files... done
dumping search index in English (code: en) ... done
dumping object inventory... done
build succeeded, 1 warning.

Build finished. The HTML pages are in build/dirhtml.
sphinx-autobuild -b dirhtml -d build/doctrees   source build/dirhtml
Traceback (most recent call last):
  File "/Users/peteringlesby/pyconuk/internaldocs/.tox/preview/bin/sphinx-autobuild", line 11, in <module>
    sys.exit(main())
  File "/Users/peteringlesby/pyconuk/internaldocs/.tox/preview/lib/python3.5/site-packages/sphinx_autobuild/__init__.py", line 280, in main
    server.watch(srcdir, builder)
  File "/Users/peteringlesby/pyconuk/internaldocs/.tox/preview/lib/python3.5/site-packages/livereload/server.py", line 203, in watch
    self.watcher.watch(filepath, func, delay, ignore=ignore)
TypeError: watch() got an unexpected keyword argument 'ignore'
make: *** [preview] Error 1
ERROR: InvocationError: '/usr/bin/make preview'
_________________________________________________________________________________________________ summary __________________________________________________________________________________________________
ERROR:   preview: commands failed

Here's the version of tox I'm using:

11:36:16 ~/pyconuk/internaldocs $ tox --version
2.3.1 imported from /usr/local/lib/python3.5/site-packages/tox/__init__.py

This happens with a clean .tox directory.

The code of conduct we've used in previous years has lacked guidelines about how reports of problems will be dealt with.

It would be pragmatic to make use of a code of conduct that's battle-tested, and so I would like us to adopt PyCon US's code of conduct

For attendees (and potential attendees) to contact the committee, we should have an address that's separate to the pyconuk-adm one.

There a number of reasons for this:

• It'll allow us to keep all queries in one place, rather than
• Not everybody on the pyconuk-adm list needs/wants to keep track of every attendee request
• Some of the correspondence with attendees might not be suitable for a list with a distribution as wide as pyconuk-adm.

I suggest [email protected].

The Django Girls team have asked whether they can get t-shirts, posters, etc delivered to the venue. Sponsors will want to do the same.

For sending out as-is to departments, and specialising for individuals that we know.

The website says this we'll do this by May 1st, so we'd better do it by then!

We've promised we'd do this on the diversity/accessibility/inclusion page.

This should include section about financial aid.

We've used linkchecker in the past but it was very cumbersome.

We should use the questions identified by @Lukasa here.

We should also ensure that people are notified by email that we have received their submission. I have some App Script code to do this.

This follows a discussion on the mailing list.

Assigning to @Lukasa who brought up the issue originally.

Tasks for PyCon UK committee:

• Earmark room(s) for workshop
• Ensure room is adequately equipped with tables of four, power sockets, and a projector
• Link to application form from website
• Provide booth space for Django Girls
• Publicise workshop in Cardiff area
• Help find coaches

First, add page to internal docs documenting questions asked.

We need a page on the website about the teachers' day.

@evildmp has been working on this at PyconUK/2016.pyconuk.org#2.

As per https://github.com/nonprofit

See PyconUK/2016.pyconuk.org#6 (comment).

Start with the hotels at http://2015.djangocon.eu/welcome/accommodation/.

We need to be able to track:

• Sponsor/potential sponsor's name
• Who we've been in contact with (name and email address)
• Who's leading discussions on our end
• The current status of discussions -- one of:
  • Contacted
  • Not sponsoring
  • Sponsorship agreed
  • Sponsorship received
• Date of last contact
• The agreed sponsorship package
• Any extra notes

Alternatively, we could investigate using a CRM for this (and I'd be happy for us to pay for the right one) but we need to get this set up soon.

To be assigned to Paul when he joins the GitHub team.

People are already asking about what's going to be happening on each day. We need to set expectations appropriately, particularly with regard to the Thursday and Monday.

@evildmp, with your programme hat on, could you make a PR to add this to the front page?

To be done once hotels have been contacted. See #66.

First, add page to internal docs documenting questions asked.

It would be brilliant if we could support a charity within PyCon

With Chloe: Short presentation to get a poll on which charity to support next year
Charities in list for poll so far: BlackGirlsTech, Myton Hospice, Cancer Research

John Pinner Memorial Fund
This year, support Myton Hospice

Possible suggestions:

• Have a charity booth (Contact charity for this?)
• Optional donation for tea/coffee (Just buckets left at tables with refreshments)
• Ability to donate via dinner ticket through Tito (Attendee to specify amount, suggested amount £3)

This is what we should be linking to when we start to publicise the conference.

We need a page on the website about the Code4Research track. It should act as a landing page for the track.

We will link to the page from the homepage.

It should include links to the tickets page, to the CFP, and to the financial aid page.

I suggest it goes at 2016.pyconuk.org/code4research.

Currently this doesn't work.

I think only @zeth can do this, but we need to make sure that at least somebody else (@ghickman?) has access to these settings.

Mock up form using ti.to that has these questions.

Where did we get the debug duck from? Can we get a debug dragon?

So far, we've promoted the conference via the python-uk and pyconuk mailing lists, and on Twitter.

Where else should we be promoting?

Please add suggestions, via pull request, to this page

@hawkz is working to the design spec.

Assigned to @doismellburning, but you should work with Paul (who's not yet part of the GitHub team).

@drvinceknight asked: "I have 3 undergrads here that the University is going to pay for tickets for. Would it be possible to put 3 tickets together on Tito for them and invoice my School? Any other preferred way of doing this?"

There are two parts to this:

• Put together workflow for tracking status of invoices. @doismellburning is the person to do this.
• Work out how to create "secret tickets" on Tito. This should be easy, but I'm not sure whether we need to create a separate ticket type for this.

There's a lot of minutiae popping up with making sure the repos/sites are in order, just keeping track of them in one place:

• Roll pyconuk.org repo back to 22833ca (pre 2016 banner)
• change CNAME in pyconuk.org repo to point to 2015.pyconuk.org
• copy 2016 holding page changes from pyconuk.org repo to 2016.pyconuk.org repo
• check pyconuk.org and 2016.pyconuk.org both resolve to the 2016 website (separate to #37)
• Move pyconuk.org repo to 2015.pyconuk.org
• email mailing list about changes to repos
• document repo naming in internaldocs
• investigate why 2015.pyconuk.org repo isn't building gh-pages correctly

This page will be linked to from the homepage, from the CFP, and from the tickets page.

@evildmp has suggested that we use a email address for contacting suppliers etc. This sounds like a good idea!

We'll need to host DNS with DNSimple so we can make use of a URL record.

To future me: see if you have access to pyconuk.net in 123-reg.