why?

[afknapping]

what is the reasoning behind spending resources on this?! there are tons of solutions out there for ticketing.

[AnneGilles]

because we want to do it our way. and according to our standards. we learn incredibly much during the process.

we do like to learn from good examples out there, so don't hesitate to point out other approaches you know.

[afknapping]

another apporach for selling tickets? Maybe just use ti.to? or eventbrite? (do not use amiando, though :)

Look, i am all for DIY, but writing your own ticketing app is totally out of the c3s scope, makes the whole project look childish and is actually a bit embarrassing.

resources are scarce so please start doing throw-away prototypes on the software you set out to deliver. that would make sense, because there would be something we can give feedback to and you could work that in the the next-from-scratch iteration of the main software.

If members of the project personally want to write their own ticketing app, fine. but please do that outside the c3s context and do not put this project on arbitrary dependencies. Just open an account on tito and start selling the tickets.

PS: it would also be nice to keep this ticket open until more people had the chance to leave their opinion...

[emrox]

+1 @ @filtercake

[thomiel]

Tito says in their privacy policy "We never share organiser information with any third party without consent." -- but no word about the information attendees may submit... Might there be a reason the company resides in the EU country with the weakest data privacy law? I don't know... At least I could find some lines on privacy there -- not so on Eventbrite.

I feel relieved that the C3S doesn't give data from hundreds of persons to third parties, just to organize events.

[emrox]

as I received a ping from this a thought came to my mind: a good solution could be to use a own instance of https://github.com/pretix/pretix
It's also used by CCC for the Chaos Communication Congress and IMHO it would be great to collaborate.

[unDocUMeantIt]

https://github.com/pretix/pretix

looks great. no idea though what it would take to adjust pretix to our needs (like, for instance, talk to our membership database, send individual invitations for two different classes of members, only show one class of tickets to members and another class publicly, etc.). if all that can be done with fewer resources, it might be worth looking at next year.