[wp-meta] [Making WordPress.org] #4162: CampTix QR Code Feature

[Making WordPress.org]

#4162: CampTix QR Code Feature
-------------------------------------+---------------------
 Reporter:  usmankhalid              |       Owner:  (none)
     Type:  enhancement              |      Status:  new
 Priority:  normal                   |   Milestone:
Component:  WordCamp Site & Plugins  |  Resolution:
 Keywords:                           |
-------------------------------------+---------------------

Comment (by casiepa):

 After discussion on slack #meta-wordcamp (starting from
 https://wordpress.slack.com/archives/C08M59V3P/p1566495258147700) the
 following steps were identified for Phase I:
 1.1 Identify a QR code generator that is very popular, has unit tests, is
 actively maintained, etc
 Something that gives a lot of signals that it won't have security
 vulnerabilities or bugs. And that has a composer package, because then
 we’d get automatic notifications from GitHub about security updates
 1.2 Create as an enhancement for the existing camptix-attendance plugin
 (https://github.com/WordPress/wordcamp.org/tree/production/public_html/wp-
 content/plugins/camptix-attendance)
 1.3 add the QR code to the Notify feature, so that orgs could send out an
 extra email a couple days before the camp, telling people to save the
 email and bring it with them for registration on their phone or tablet
 1.4 have the QR code hook into the attendance check in to mark an attendee
 as checked in. Volunteer needs to be logged in and URL could then be
 https://2019.narnia.wordcamp.org/wp-admin/?camptix-
 checkin=1&attendee_id=1234

 For consideration:
 2.1 For the QR string, if the full URL could not be used, {site
 ID}-{attendee ID} might be a bit better than {partial site slug}-{attendee
 ID}; it'd be easier to parse out
 2.2 The volunteer would need to be editor or something on the WordCamp
 site. It's worth considering the implications of that. We could
 potentially do somewhere where, if a user opens the existing hidden check-
 in URL, they get a cookie or something that lets them also open that new
 check-in URL

-- 
Ticket URL: <https://meta.trac.wordpress.org/ticket/4162#comment:4>
Making WordPress.org <https://meta.trac.wordpress.org/>
Making WordPress.org