Project

General

Profile

Bug #1889

Event website + announcement

Added by laforge almost 2 years ago. Updated over 1 year ago.

Status:
Closed
Priority:
High
Assignee:
Target version:
Start date:
12/20/2016
Due date:
12/20/2016
% Done:

100%


Description

Once we have determined the format and have a preliminary schedule (for the public part), we will need to
  • create a proper homepage about the event (could still be in the wiki, or maybe a separate website? with
    • schedule information
    • venue information
    • travel information
    • contact information (-> sysmocom RT)
    • registration form (and fee/payment info?)

Related issues

Follows Osmocom Conferences (OsmoDevCon + OsmoCon) - Feature #1886: Venue for the 'user' part of OsmoDevConClosed2016-12-19

Follows Osmocom Conferences (OsmoDevCon + OsmoCon) - Bug #1887: Work out a schedule for public user day of OsmoCon 2017Closed2016-12-19

History

#1 Updated by laforge almost 2 years ago

  • Due date set to 12/20/2016
  • Start date changed from 12/19/2016 to 12/20/2016
  • Follows Feature #1886: Venue for the 'user' part of OsmoDevCon added

#2 Updated by laforge almost 2 years ago

  • Follows Bug #1887: Work out a schedule for public user day of OsmoCon 2017 added

#3 Updated by laforge almost 2 years ago

  • Status changed from New to In Progress
  • % Done changed from 0 to 10
Options:
  • use OSEM (overkill, but looks really nice from using the demo site they provide)
    • seems like they only have one payment provider, which we'd have to use and integrate in our accounting :/
  • use Odoo website_event (but then, we really don't want to give access to Odoo to the general public for security reasons)
  • a static website built with nikola (maybe even simply on sysmocom.de) and add the tickets simply to the sysmocom webshop.
  • use some web-based service like eventbee (but they all seem to be based in the US, and we generally don't like SaaS for philosophical reasons)

OSEM would have the advantage that we can also manage the event schedule there, as well as a CfP etc. It might be a bit of an overkill, but soemhow I like it. should be future-proof, too.

#4 Updated by laforge almost 2 years ago

  • % Done changed from 10 to 40

I have created OsmoCon2017 in the wiki here for the time being. Let's collect more information there and then decide if we simply stick with the wiki or go for OSEM.

#5 Updated by laforge almost 2 years ago

  • Assignee set to laforge
  • Priority changed from Normal to High

#6 Updated by laforge almost 2 years ago

  • % Done changed from 40 to 50

Finally managed to get osem running in a lxc container on my internal network. Looks quite nice, I entered all the events we currently have planned for OsmoCon2017, aligned them in the schedule, defined a ticket, etc.

There's no built-in feture to change the speker of a talk (speaker is always the submitter), but this should be possible to change in the sql (in the worst case). I'll have to test the payment integration and e-mail interface, but after that it's more or less ready to go public.

#7 Updated by laforge almost 2 years ago

  • Status changed from In Progress to Resolved
  • % Done changed from 50 to 100

we decided to go with a wiki page and a mailman based newsletter announcement for the time being.

#8 Updated by laforge over 1 year ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)