Wiki - Projects

Topics for the Act hackathon

Password handling security review: Joakim T (‎trmjoa‎)
REST API design: Lars Dɪᴇᴄᴋᴏᴡ (‎daxim‎), Theo van Hoesel (‎vanHoesel‎), user: trmjoa, Salve J. Nilsen (‎sjn‎)
- A document containing rough notes and suggestions http://pad.hackeriet.no/p/act-rest-api-1
- daxim will not attend in person, but is interested in working with c via vanhoesel on IRC in fleshing out the REST service. A prerequisite for this is some thinking about user stories, defining which user roles will want to read/write which kind of data, and how the data relate to each other.
Vagrant image for Act - Should be available before the hackathon: trmjoa(Interesting in getting hold of one if it exists)
Registration usability: sjn
Better documentation/tools for Act template designers. Which data / method is available for template designers?

Possibility of attaching a presentation / file to a talk submission ?
Improving the "product" features in Act: sjn
- Set max of available products (e.g. for limited access tickets)
- Product aliases (e.g. for distinguishing sub-events, co-located conferences or events organized by other communities)
New default templates, with a nice modern look that supports mobile devices out-of-the-box.
Being able to define customfields pr user pr conference. Conference organizers should be able to define customfields that users can provide when they sign up for a conference. These fields would solve hotel/tshirt/food/etc fields that is stated in the ACT todolist. Such a generalized custom fields system would make act very flexible for organizers in terms of which data they collect from their users

version 4 saved on 20/11/14 19:04 by Joakim T (‎trmjoa‎)