amsterdamphp / meetup-raffle-machine Goto Github PK

Since PHP 5.5 is EOL, the PPA is also deprecated.
If we upgrade PHP, should we upgrade to PHP 7 ?

dev :: /vagrant » php -v
PHP 5.5.37-1+deprecated+dontuse+deb.sury.org~trusty+1 (cli) (built: Jun 24 2016 08:29:49) 
Copyright (c) 1997-2015 The PHP Group
Zend Engine v2.5.0, Copyright (c) 1998-2015 Zend Technologies
    with Zend OPcache v7.0.6-dev, Copyright (c) 1999-2015, by Zend Technologies
dev :: /vagrant » 

We should re-enginner the site to use OAuth authorization, that way we do not need to worry about admin-only API calls as the meetup api will do that.

Since the current MeetupAPI client does not accept oAuth or POST, we may need a better library before doing this.

It would make managing the raffle easier if we could add the prizes that will be raffled off and have this shown in the interface when we do a raffle.

Add option to remove users who were wrongly added or not there.
Either remove or just disable.

In the last meetup it seems the random number generator returned numbers out of the range, i.e 35, 36 with only 34 people.

Add a deployer setup for deploys.

Fix the page title

Since we no longer have an API to authenticate with key only, we need Oauth2 in this.

It means finding a new library to talk to Meetup since DMS no longer supports its library nor proper Oauth2.

Running gulp in VM got me this, does not break anything but i guess image is not optimized?

Unhandled rejection Error: Command failed: /vagrant/node_modules/optipng-bin/vendor/optipng -strip all -clobber -force -fix -o 3 -out /tmp/f3ba4d5b-9557-4623-b6b8-bb7aafbf7db2 /tmp/0bde165e-f2a1-42c8-ba6f-4fe62d72ed54
/vagrant/node_modules/optipng-bin/vendor/optipng: 1: /vagrant/node_modules/optipng-bin/vendor/optipng: Syntax error: "(" unexpected

    at ChildProcess.exithandler (child_process.js:213:12)
    at emitTwo (events.js:87:13)
    at ChildProcess.emit (events.js:172:7)
    at maybeClose (internal/child_process.js:854:16)
    at Socket.<anonymous> (internal/child_process.js:330:11)
    at emitOne (events.js:77:13)
    at Socket.emit (events.js:169:7)
    at Pipe._onclose (net.js:487:12)

Use the API's "checkin" option to filter out and show only the people who have checked-in to the meeting.

This way we avoid any no-shows and I'm pretty sure that even people on the waiting list can check in if they are at the venue.

Currently when doing the raffle on-screen we use the browser zoom to reduce the size of the icons and fit everything on the page.

It would be ideal if the CSS would adjust everything according to the screen size: thumb size, logo size and winner image/text size.

The amazing code written by @rdohms during the talk to get the raffler working does not set a TTL on the cache so it never expires, this needs to be adjusted and tweaked.

Meetup has deprecated support for "checkins", so our raffle system now has nothing to use but go back to the old RSVP system.

One of the discussed solutions was to offer a self-hosted solution with local storage to simulate checkins. This would be the same screen offered in the checkin PR (#8) but anyone would be able to select "this is me" and check themselves in.

Abuse of this would not be effective, since you still require to be present in the meeting to receive the raffle prize. Any false positives we can flag down and take further action from a UG point of view.

Simplest storage solutions include simpleDB or Redis. Its a shame that this now eliminates the possibility of having a "stateless" app that could run from anywhere, but Meetup has given us no choice.

Seems the current API call includes even negative RSVP's, these should be removed

I would like to see this raffler me used by other UGs, for this we should clean up a bit and make the look/feel more configurable.

• Make vars for colors
• Make vars for logo
• Make a cleaner, smaller header
• Make a powered by logo/footer

The raffle engine now looks very "bootstrap." It needs to have proper AmsterdamPHP branding and style designed to it.

Implement Whoops for error handling.

Double check logs.