blob: 82c2a085b4741f9475a3f2df0b25637efb5e7453 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
|
OsmoCon 2018 Outlook
====================
:author: Harald Welte <laforge@gnumonks.org>
:copyright: 2018 by Harald Welte (License: CC-BY-SA)
:backend: slidy
:max-width: 45em
== OsmoCon 2017 Preparation
* Planning started in October
** http://lists.osmocom.org/pipermail/openbsc/2017-October/011332.html
* Schedule planning in December, with little particiopation
** http://osmocom.org/issues/1887
* event announcement too late (Feb 01)
* travel grant funding arrived way too late (March 27)
* 14 days ahead of the event we were about to cancel
** almost no registrations until that point
* talk submissions came in way after schedule was full
== OsmoCon 2017 Experience
* venue was full, actually overbooked
* talks were good
* recordings were excellent
* strong sysmocom presence, but some diversity
** Fairwaves, Facebook, On-Waves, Rhizomatica
== OsmoCon 2017 Feedback
Attendees informed us
* one day is too short
* very uni-directional, not much interaction
* schedule too full
** consequence of talk submissions too late
** consequence of only one day
== OsmoCon 2017 Retrospective
* I didn't like the venue too much
** hard to get air into the room
** to crowded with no separate room during breaks
** non-functional WiFi
** no-frills, 1990ies FOSS community feeling may not appeal to everyone
* OsmoCon + OsmoDevCon back-to-back
** is lots of stress
** leaves no time to meet up with OsmoCon attendees one day aftewards
** caused OsmoDevCon to be one day shorter
== OsmoCon 2018 Changes
* larger venue
* not a youth hostel but a real hotel
* two days instead of one
* not together with OsmoDevCon but 6 months later
* early-biard pricing should make people order tickets sooner
* formal CfP process with submission deadline, ...
== EOF
End of File
|
