Pinax is an open-source platform built on the Django Web Framework.

• Things are suggested in python3 porting guide. https://docs.djangoproject.com/en/1.8/topics/python3/
  1. adding from django.utils.encoding import python_2_unicode_compatible
  2. __str__ instead of __unicode__ https://docs.djangoproject.com/en/1.8/topics/python3/#str-and-unicode-methods
  3. Adding from __future__ import unicode_literals at the top of your Python modules https://docs.djangoproject.com/en/1.8/topics/python3/#unicode-literals
  4. Removing the u prefix before unicode strings; https://docs.djangoproject.com/en/1.8/topics/python3/#unicode-literals
• also closed #66

Signed-off-by: Hiroshi Miura [email protected]

r"^sessions/$" was changed to r"^sessions/all/$" for the purpose of avoiding a conflict with r"^([\w-]+)/$". It raised "Page not found" (404) error.

Fixes #148

Hi there!

I was just trying out symposion and found it quite nice. I've seen that there are quite a few more projects (like reviews and schedule) than are visible in the admin interface.

How can those pieces be put together? Otherwise it looks like there is not much use for the "proposals". Am I missing something?

Thanks for your help, Björn

As a reusable application, symposion should be mostly independent against UI part. It has already archived when dropping all templates from symposion and introduce pinax-project-symposion.

There is another dependency that is MarkItUp widget.

Some user prefer to use TinyMCE (or other widget such as MarkEdit as in PyCon), but it is quite difficult to change without forking and modifying symposion code base itself.

Can we drop MarkItUp dependency from, at least, models?

Changing from MarkupField to TextField, then developer may be able easily to add their preferable widget to their templates.

• i18n-ed form's label and model's verbose_name
• import unicode_literals for compatibility
• add python_2_unicode_compatible() decorator and replace unicode

The /admin URI doesn't work because username logins don't work (settings.py only allows email logins, from /account/login). But /account/login (or anything other than /admin for that matter) won't load and throw a stack trace because there's no conference defined.

If the initial_data.json is going to have a site defined, it should probably also have a conference defined.

Thanks!

Created account during syncdb, logged in, clicked on settings and got error:

DoesNotExist at /account/settings/ Account matching query does not exist.

Likely fixed in upstream django-user-accounts.

This change is based on the PyOhio fork located at: https://github.com/PyCon/pycon/search?utf8=%E2%9C%93&q=twitter_username

The PyOhio forks has tests and other features which might be worth adding but that's probably a larger design decision.

c0402575475e481d9d4dfdc64bf6f9e0cf90ad2b added a "name" field to schedule slots. At the time it was written, symposion did not include migrations. This commit creates a migration that adds the field to the database table and automates the generation of the slot name (by re-saving all existing slots).

This fixes a database error that happens when accessing schedule slots:

ProgrammingError: column symposion_schedule_slot.name does not exist
LINE 1: SELECT "symposion_schedule_slot"."id", "symposion_schedule_s...

• forms for labels and helps
• views for success or warning messages
• apps and models verbose_names for admin

Signed-off-by: Hiroshi Miura [email protected]

Symposion has proposal kind model in proposals app

class ProposalKind(models.Model):
    """
    e.g. talk vs panel vs tutorial vs poster
    Note that if you have different deadlines, reviewers, etc. you'll want
    to distinguish the section as well as the kind.
    """

It is not used in pinax-project-symposion sample project. because it defined several *Proposal models such as TalkProposal, TutorialProposal and use its forms. https://github.com/pinax/pinax-project-symposion/blob/master/project_name/proposals/forms.py

It is duplicated feature.

Symposion can drop proposal kind from its model.

Bumps html5lib from 0.9999999 to 0.999999999.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

There are small typos in:

• CONTRIBUTING.md
• symposion/reviews/utils.py
• symposion/sponsorship/models.py
• symposion/static/tabletools/js/TableTools.js

Fixes:

• Should read there rather than ther.
• Should read separate rather than seperate.
• Should read namespace rather than namesapce.
• Should read incomplete rather than incomplate.

Semi-automated pull request generated by https://github.com/timgates42/meticulous/blob/master/docs/NOTE.md

This adds an option in ProposalSection to switch on Anonymous Review.

This allows blind review to be achieved in multiple ways:

• In symposion.reviews, returning proxied ProposalBase objects where .speaker() and .speakers() properties will return an object that is not the actual speaker, but will still display information in templates.
• By inspecting .anonymous_review() on a proposal, which can be used to completely hide fields referring to speakers whilst anonymous review is switched on.

The proxy object approach is somewhat of a blunt instrument, but it means that templates do not need to be correct in order to suppress the identities of speakers.

In at least one conference I've worked on, we needed to fork Symposion to remove the description field on ProposalBase, as we didn't use it.

This PR makes description, abstract, and additional_notes blankable, and adds a convenience mixin for ModelForm that lets you make these fields required again.

This preserves original functionality, and also makes it possible to customise/disable fields from BaseProposal without needing to fork Symposion.