klepas / votie Goto Github PK

• Auto-search for duplicates

At the moment we have only one conference per instance. Add the ability to have multiple conferences:

• A conference has: name, title, description (eg. "bcc2011", "BarCamp Canberra 2011", "blah blah blah...")
• The current model hierarchy will be attached to a single conference
• The home page will show all conferences, with the most recent at top
• After selecting a conference, the user experience will be pretty much identical to the current one

Hide in production

Currently response messages to actions (e.g. adding a new talk) are in p#flash but are hidden, presumably by one of the divs. Fix and make pretty.

For the 1.0 release, the readme file needs some love. It needs:

• a quick summary
• install instructions
• a quick howto on using
• licensing
• copyright
• …?

We need an admin panel for a few things, and one should be the ability to lock a votie instance from further talk submissions (submission lock) and complete lock (no more voting). We could handle the latter by just removing the ability to sign-in, but I think adding it as an actual feature, signed-in or otherwise makes sense (imagine an admin wanting to sign-in to a completely locked instance to re-open it for voting).

So:

• ability to lock arbitrarily (e.g. checkbox);
• ability to lock addition of further talks with voting left open;
• ability to lock completely — no adding of talks, no voting (admins can still log-in to admin panel and make reversing changes though);
• ability to lock via start and end dates for a conference/event (e.g. at set-up of the instance start and end dates for the event are entered and a type of lock is specified).

A lot of markup is currently being duplicated between the views (Pascal’s fault — I didn’t realise the nature of the layout and views at first). Most the duplicate content includes the header, nav, and secondary nav.

Gonna need some help turning this stuff from haml back into Ruby code.

Symbols such as &, <, >, etc. in user input are not converted to HTML character entities.

For example: the & glyph needs to be replaced by the HTML entity & in the titles of presentations.

Currently when no URL is entered into the text box for the slides a link to votieapp.org is made instead. When no URL is entered by the submitter, no slide link should be added or perhaps ‘No slide link available’ note should be added?

Currently the talk data is just being stuck into divs with classes. These need to be placed into span tags and paragraph tags and then styled appropriately.

Move the BCC2010 instance to another destination on the votieapp.org domain (votieapp.org/bcc2010 or bcc2010.votieapp.org). Also lock the instance from further edits.

When there's too many items, the menu wraps under the rat image, shifting the hero text down with it.

This can be seen by comparing the layout on the site home page (http://votieapp.org) with that of a hosted instance (http://bcc2010.votieapp.org).

• Each talk has a time and a room (no date for this release)
• Schedule page for viewing the whole schedule
• Show current talks on event home page

Should we add this? Not sure — there was one guy at BCC2010 who didn’t use Twitter, and when I mentioned we were thinking of adding identi.ca and OpenID support he mentioned he didn’t use either of those either. Just a thought?

It would be really cool to have a table or one line per talk view that displays the current voting stats. So you can really easily see which talks are most popular at a glance.

Fixes the CSRF security hole.

.

Basecamp-style would suffice:

• Add a logo
• Change the colour scheme
• Custom domain/subdomain?

On the ‘Update my details’ page there’s a bit of CSS work to do on the user forms (sign up, sign in, edit details).

Peeps at BCC2010 had some auth issues (reload the call-back, or add/remove www from the URL and related oddities). Check into.

For conferences home, talks, vote, presenters page, show a message if there are no items to display.

eg. "There are no conferences yet. Go ahead and make one!"

A one- or two-step install UI would be awesome — perhaps something akin to the installer for WordPress? Stuff I would foresee that would be part of the UI:

• name of instance/event;
• administrators for the instance (e.g. Twitter or identi.ca nicks, OpenID email addresses, …);
• start and end dates for the event with ability to set a type of lock at event closure automatically;
• instance DB info?;
• event logo?

When submitting talks with no content entered the error pages are present but unfriendly; make friendly. :)

The markup and code for this is currently in app/views/talks/index.html.haml, and then implement login functionality via the the secondary nav (the top-bar).

We should add an admin panel for administrators to log in. I’m thinking of something similar at first to how WordPress installs, which is as simple as possible to get an instance going, and then allows you to administrate the instance where needed (e.g. locking).

Stuff we might want to enhance with a dabble of JS:

• Adding a talk — e.g. clicking ‘submit a talk’ from the nav pushes the page content down with the submit talk text entry fields appearing; submitting clears the data and adds it to the page (if applicable).
• Voting on talks — adding a vote to a talk ticks the current votes up by one without a page reload.
• Hovering on ‘Sign-in’ would give a :hover dialog popup near the element with info on auth’ing via Twitter, and likewise for signing out. For an example see how GitHub does hovers on the gravatars.
• …?

The submitter omitted http:// and the URL now points to http://votieapp.org/www.makehackvoid.com. We need to provide labels and example content to guide user input when submitting their talks — see issue #17.

Currently, we use an around_filter, when we could:

class ApplicationController<  ActionController::Base
  rescue_from CanCan::AccessDenied do |exception|
    redirect_to root_url, :alert =>  exception.message
  end
end

The p.hero text currently explains what votie is. This should ideally go into a hero text on a static page for votie.com, and be removed from the instance itself. Instead, this text needs to be quickly editable and essentially say what conference/BarCamp the instance is for.

Have a pretty slider/tabular layout of the current hour and all the tracks and their current slotted talks (with an option to add a talk for a slot in a track if it is empty) presented akin to a calendar’s rolling timeline of the day.

Perhaps autogenerate #hashtags for each talk for easy tracking on Twitter (#votie-bcc2010-123), or let users specify a hashtag to use. Obv. an extension of that would be to pull such marked tweets into the Votie interface.