Wiki - Projects
Trello
A place where you can put some ideas down and play with cards as if they were Post-Its ... Trello.com
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. Some of those stories are currently written down at Act Voyage API
- Vagrant image for Act - Should be available before the hackathon: trmjoa(Interesting in getting hold of one if it exists) Theo van Hoesel (vanHoesel) the Base file is finished, the Voyager-Provisioning script needs some love
- Registration usability: sjn
- Better documentation/tools for Act template designers. Which data / method is available for template designers?
- Database for Community Events (aka Conferences)
- currently all 'settings' are in .ini files
- conf_id is being used all over the place
- most data is related to the context of a community-event
- DBIx::Class can not build relations based on a scalar
- capability of reading .ini-files into the database
- capability of writing .ini-files from the database
Act Feature requests
- 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
Dernière modification : 22/11/14 22h17 par Theo van Hoesel (vanHoesel)
Accueil | Modifier cette page | Modifications récentes | Historique