We need to store transaction data for

1. PayPal
   • store the @details_response
2. Checks we receive for mailed payments
   • name
   • address on check
   • bank drawn on
   • check number
   • amount
   • date on check
   • memo
   • signer's name if legible
   • who entered by (current_user)
3. Walk-in payments
   • amount
   • who entered by (current_user)

Require features in initial implementation:

1. Admin permissions to moderate (delete posts, ban users, no editing)
2. Automatically linkify links

Nice to have features, may be filed as Enhancements if not in initial implementation:

1. Profanity filter (really, just a filter) - Must be configurable and have "good defaults"
2. URL shortening for links using bit.ly or some locally-hostable product - Mad props for implementing shortening in PLAS
3. Upvote/downvote or agree/disagree buttons (anonymous)
4. Markdown syntax accepted

This would be a great project for someone just getting their feet wet in Rails.

Output information suitable for import into various calendaring systems.

Allow registered users to file tech support tickets. These are simple requests and need only be seen by users who are a part of the tech support group. Provide for a subject, description, source (hardware/software/don't know) and severity/priority.

It might be another useful feature to have some way to allow users to join this group themselves.

Severities/Priorities:

Critical (I can't play in an official tournament)
High (I can't play in an unofficial tournament)
Medium (I can't play a game I want to play)
Low (I don't know how to do something)
Trivial (I have a question)

Groups:

Tech Support Admins
Tech Support Users

Permissions:

support.open
support.close
support.administrate
support.view

Received this today:

Hi colindean,

I found a potential bug in your GitHub project, https://github.com/colindean/plas/

I'm a PhD student in computer security of the University of California, Santa Barbara, and I'm researching Execution After Redirect (more information here: http://adamdoupe.com/overview-of-execution-after-redirect-web-appl) vulnerabilities. I created a tool to analyze Ruby on Rails applications for EAR vulnerabilities and it found EARs in your project plas.

Here's the output from the tool:

Regular EAR found in ./app/controllers/registrations_controller.rb:82.
With the call graph: redirect_to
Severe EAR found in ./app/controllers/registrations_controller.rb:105.
With the call graph: redirect_to
Severe because of ./app/controllers/registrations_controller.rb:137.
Severe EAR found in ./app/controllers/users_controller.rb:81.
With the call graph: redirect_to
Severe because of ./app/controllers/users_controller.rb:85.
Regular EAR found in ./app/controllers/users_controller.rb:102.
With the call graph: redirect_to

Quick EAR overview:
Calling redirect_to doesn't end execution of a controller. It is possible that other, unintended, methods can be called after a redirect_to.

The easy fix for this is to add a "return" after the redirect_to (or after a function that calls redirect_to).

The tool is open-source and is hosted on GitHub at https://github.com/adamdoupe/find_ear_rails

I would appreciate it if you could give me any feedback about the tool.

Thanks for your help, and feel free to email me with any questions!

• @adamdoupe

Many LAN parties require attendees to sign waivers.

Ideally, this system would allow for an administrator to supply an HTML template with certain variables (full name, address, birthdate, etc.). The user could then print it and bring it signed with a signature of themselves or their parents/guardians.

Bonus points/future enhancements:

• The user should be able to "sign" the form by confirming it via email, or have a parent "sign" it by confirming it via email.

https://github.com/apotonick/apotomo

Use this for inspiration:

http://fuelyourcoding.com/set-rails-logging-on-fire/

When I created Ticket, I used price as the storage for the price of the ticket. I realize now that I'd rather have price be an instance of Money.

What needs to happen is write a migration to movetickets.price to tickets.cents and create a column tickets.currency to store the currency. Then, modify and uncomment the composed_of :price code and point Ticket.prix at Ticket.price, logging a deprecation message until prix no longer exists.

We don't do any validation because we have trusted, trained users doing it. We should still validate something, at least the price such that all of the registrations add up correctly and the amount paid is the amount due.

Read this inspiring article on disalienation if you wonder why.

Plus, PLAS already has several suggested ones, but it would simplify the code to just use text.

Hello again,

Now that I have the app running, I am running into an issue when signing up (presumably for the admin account, but I'm not sure).

Navigating to localhost:3000, I'm presented with the splash page, and clicking around on any of the navigation links work (though I obviously don't have any users or events yet). When I click sign up, I get the signup page to load correctly, but once I enter my information, I am presented with the following error text.

The error seems to be "Permission code payments.accept does not exist".

Thanks in advance for any help!

https://github.com/mintdigital/asset_hat/blob/master/README.rdoc

Your assets are covered.

With Rails’ default asset caching, CSS and JS are concatenated (not even minified) at runtime when that bundle is first requested. Not good enough. To make your pages load faster, AssetHat can automatically:

Easily minify and bundle CSS and JS to reduce file sizes and HTTP requests. Do this on deploy, and avoid any performance hit at runtime.
Load popular third-party JS (like jQuery, YUI, and Ext JS) from Google's CDN when in production, or from localhost in development. It’s as simple as <%= include_js :jquery %> to load straight from Google.
Force image URLs in your CSS to use CDN subdomains (including SSL support), not just the current host.
Add an image’s last Git commit ID to its CSS URLs to bust browser caches (e.g., /images/foo.png?ab12cd3).

Ala: http://somerandomdude.com/articles/design-technology/font-embedding-icons/

Each event should have a Schedule of Tournaments and SubEvents. The Schedule should be displayed on the Event's dashboard page in chronological order, with things highlighted if currently in progress and crossed out as they end.

Tournaments and SubEvents need not know their time -- that's the job of the Schedule and its ScheduleItems.

Really Tournaments are a subclass of SubEvent, and anything which is a SubEvent is a Schedule-able. Anything Schedule-able can be a ScheduledItem.

They were once scary and strange, and now, they're too useful not to use!

Steps:

1. create an event
2. click create ticket so the url looks like [host]/events/1/tickets/new
3. put a number like 600 in the cost field
4. put something like "over 9000" in the Available field
5. click "create ticket"

You get the following:

NoMethodError in Tickets#create

Showing /home/dmotles/code/plas/app/views/tickets/_form.html.erb where line #1 raised:

undefined method `model_name' for NilClass:Class
Extracted source (around line #1):

1: <%= form_for ([@event, @ticket])  do |f| %>
2:   <% if @ticket.errors.any? %>
3:     <div id="error_explanation">
4:       <h2><%= pluralize(@ticket.errors.count, "error") %> prohibited this ticket from being saved:</h2>
Trace of template inclusion: app/views/tickets/new.html.erb

Rails.root: /home/dmotles/code/plas

Application Trace | Framework Trace | Full Trace
app/views/tickets/_form.html.erb:1:in `_app_views_tickets__form_html_erb__3302624983022953928_39195520_3150842096570869018'
app/views/tickets/new.html.erb:3:in `_app_views_tickets_new_html_erb___1007846872533634996_39238320__3039767047594116635'
app/controllers/tickets_controller.rb:62:in `block (2 levels) in create'
app/controllers/tickets_controller.rb:57:in `create'
lib/rack/firebug_logger.rb:9:in `call'
lib/rack/firebug_logger.rb:9:in `call'
Request

Parameters:

{"utf8"=>"✓",
 "authenticity_token"=>"S5fZlj8+6u5+FXwWAj9nkxs/chCR16+CsRnnu5rEjds=",
 "ticket"=>{"name"=>"Registration for one person",
 "cents"=>"600",
 "available"=>"over 9000",
 "date_open(1i)"=>"2011",
 "date_open(2i)"=>"6",
 "date_open(3i)"=>"28",
 "date_open(4i)"=>"00",
 "date_open(5i)"=>"54",
 "date_closed(1i)"=>"2011",
 "date_closed(2i)"=>"6",
 "date_closed(3i)"=>"28",
 "date_closed(4i)"=>"00",
 "date_closed(5i)"=>"54"},
 "commit"=>"Create Ticket",
 "event_id"=>"1"}
Show session dump

Show env dump

Response

Headers:

None

Hello,

I'm relatively new to Github so I'm not sure if this is the best way to write down this issue, but I wanted to try out PLAS, so I followed all the steps:

• got RVM set up with three rubies: 1.8.7, 1.9.2, and ruby-head
• git cloned PLAS into home directory on a Mac
• cd'd to the directory, accepted rvm's trust prompt for the .rvmrc file
• bundle install worked as expected
• rake db:migrate worked as expected
• rails server came up with the following error:
  https://gist.github.com/982397

Again, sorry if I could've explained this better. I'd be happy to share any more information you might need to fix this issue.

They're not as hard as notices (see issue #31) but they should be more visible.

Everything just has a title of "Pittco" right now. We need to use content_for and yield where appropriate in the header and in each view.

Jeff Adams from Pittco suggested a survey system.

These surveys can be filled out at registration time, mandatory on next visit, or optional polls.

This would be useful for asking things like

• What pizza place should we get pizza from?
• What game do you want to play next in Roulette?
• Whose performance in karaoke was best?
• vi or emacs?

It's currently on each page where it could be needed. It should be really in layouts/_masthead or the like.

I'm sure there's an easy way to do this.

It's ever present. Likely not testing for if notice actually has something in it.

Keep it there except when the page is longer than one screen.

Use ALP's system as inspiration.

Super low priority.

Output all events in iCal format suitable for importing into Google Calendar, iCal, and the like.

http://harvesthq.github.com/chosen/

• PLAS needs to have a robust way to control who is able to do what
• Groups are Administrators and Users
  • More added later (Checkin staff, tournament admins, shoutbox moderators, etc.)

It's quite common in PHP apps to have a Config static class or global object which accesses key-value configurations in the database or an ini file. I need to uncover what is the "Ruby way" of doing this, that is, if it's any different.

http://www.kernel.org/pub/software/scm/git/docs/git-submodule.html
http://chrisjean.com/2009/04/20/git-submodules-adding-using-removing-and-updating/
https://git.wiki.kernel.org/index.php/GitSubmoduleTutorial

Import it as a submodule in doc/wiki, commit the .gitmodules, and write a rake task or bash script which will cd and clone.

A user who is not signed in is presented the shoutbox form. When they write a shout and submit, nothing happens. On the backend, there's a 500 error because current_user is nil.

• Create master tickets for purchase per event
• Tickets can come in packs of N for $M per ticket
• Use PayPal or allow for mailed checks or pre-registered walk-in payments
• Tickets are never deleted, can be transferred between events (although that will likely never be done)
• User can purchase N tickets
• User can assign tickets to other folks

It's not blueish, and the lower nav is half on top of the subtitle. The body contents are pushed up, as well.

This screenshot shows it well.

I'm sure there's an easy way to do this.

Dwolla charges only 25¢ per transaction, compared to PayPal's 2.9%+30¢ cost.

Displays to a user or emails them when they've received a ticket or there's a new event, tournament, etc.

This is in Webkit and a Firefox extension adds it there. Official Firefox support is unlikely to arrive before Firefox 5.

• Demo
• Webkit Spec
• W3C Spec

We're going to be a JSON app.

Something so that people can print out stickers or something with a QRcode on them in order to track them as being theirs.

Pittco has never had a theft, so this is of somewhat limited use and priority for us. However, other LANs might benefit from it not only as an attendee asset tracking system, but as an organizational asset tracking system for network equipment, power strips, and more.

Possibly using Challonge! API

Right now, it'll show everything and take up the whole page. It should show only the most recent 100 and they should be in a scrolling box that autoscrolls to the bottom.

Using https://github.com/brady8/thumbs_up, we can upvote anything we want...

There's no reason to show them, as I estimate that they will be rarely used. Show them only on a 1 second delay hover, and slide them in.

and ask for a full name, nickname, and pronunciation.

Administrative users should be able to create and manage events. Events have a location, start/end datetime, and a name.

They are really bland and hard to see. I can't tell when something has gone wrong!

See this presentation for more information and examples.

steam-condensor is a multi-language library for querying the Steam Community, Source and GoldSrc game servers as well as the Steam master servers. Currently it is implemented in Java, PHP and Ruby.

We can use it to update stats, etc. for Pittco Roulette servers.