Project

General

Profile

OsmoDevCon2016 » History » Version 42

tnt, 04/22/2016 01:35 PM

1 17 laforge
{{>toc}}
2 1 laforge
3
This page is used to plan and coordinate regarding the Osmocom Developer Conference 2016
4
5
6 37 laforge
h1. Osmocom Developer Conference 2016 "Transgressive Infrastructuring"
7 17 laforge
8
9
Ths Osmocom Developer Conference 2016 ([[OsmoDevCon2016]]) is an event *by project members for project members*.
10 1 laforge
As such, the primary audience is people who have been contributing to the project.
11
12 17 laforge
It is *not targetted at users*.
13 1 laforge
14
Attendance requires registration (see below) and notification of acceptance.  There number of participants
15
is limited to about 20.
16
17
18 17 laforge
h2. When
19 1 laforge
20 17 laforge
21 18 laforge
*April 21 through April 24, 2016*
22 17 laforge
23
Time: We will *start at 10am* in the morning, will take *lunch break from 1pm to 3pm* and have an open
24 1 laforge
end at night.  We have a key to IN-Berlin to come and go as we please.
25
26
27 17 laforge
h2. Where
28 1 laforge
29 17 laforge
30
In the rooms of "IN-Berlin e.V.":http://www.in-berlin.de/, Lehrter Str. 53, 10557 Berlin, Germany, the Universe.
31
32 1 laforge
The meeting / seminar / conference room at IN-Berlin is located on ground floor and has windows facing east.
33
In front of those windows is a road + sidewalk which is directly in north-south direction,
34 17 laforge
i.e. it _may_ be possible to set up some (GPS, Thuraya, etc.) antennas on the sidewalk, if required.
35 1 laforge
Some kind of pole+stand is required, though.
36
37
38 17 laforge
h2. Format
39
40
41 1 laforge
The format of this workshop is not primarily formal lectures/talks.  It's more like "guided discussions", i.e. there are
42
topics and each topic will get an "owner" who should introduce the topic and lead the discussion related to it.
43
44
45 17 laforge
h2. Who
46
47
48 1 laforge
(if you want to attend, please add your name below ASAP, no later than February 28, 2016):
49 2 laforge
50 17 laforge
h3. Confirmed
51
52 18 laforge
# laforge
53
# kevin
54
# chemeris
55
# kostanbaev
56
# steve-m
57
# Hoernchen
58
# horizon
59
# Dieter
60
# tnt
61
# nion
62
# zecke
63
# daniel
64
# jacob
65
# sec
66
# schneider
67 1 laforge
# ismagom
68 19 laforge
# neels
69 35 msuraev
# max
70 25 laforge
# pablo
71 30 laforge
# peter
72
# saurabh
73 1 laforge
74
h3. Requested
75
76
[please add your name if you would like to request attending the event]
77
78
h2. Schedule
79
80
81
TBD.  We will get two keys to the rooms and will be permitted access 24 hours per day.
82
83
We intend to start at 10am on Thursday, and finish around 3pm on Sunday.
84
85
h3. Talks/Discussions
86
87 40 tnt
|_.Who|_.What|_.How long|When|
88
|neels|from [[OsmoNITB:]] to OsmoCSCN with IuCS|30min|Thursday|
89
|laforge|OsmoBTS update (phy_link, more bts models)|30min|Thursday|
90
|kevin|Paging traffic|15m|Thursday|
91
|tnt|AMBE update|15min|Thursday|
92
|lazlo|end-to-end regression testing setup with 96 modems and 16 BTSs|45min|Thursday|
93
|zecke|Formalizing development process, gap between hobbyists and professionals, tool support|?|Thursday|
94 41 tsaitgaist
|daniel|Osmo-IUH demo|30min|Friday|
95 1 laforge
|spaar, kevin|Iuh Femtocell hacking status|30min|Friday|
96 42 tnt
|chemeris,kostanbaev|Introducing [[UmTRX:]]v3 - new SDR hardware for 2G/3G/4G|15min|Friday|
97
|jacob|libosmocore stat report||Friday|
98
|chemeris,kluchnikov,kostanbaev|Adding external interfaces for LUR/SS/USSD/SMS to [[OsmoNITB:]]|?|Friday|
99
|jacob?/max|EDGE PCU Implementation + status|?|Friday|
100
|ismagom|srsUE + srsLTE internals||Friday|
101
|chemeris|fairvawes startup experience||Friday?|
102
|daniel|[[OsmoSGSN:]] with IuPS|30min|
103 38 tnt
|laforge, zecke|Osmocom website + documentation update|30min|
104 41 tsaitgaist
|laforge|OsmoNITB async HLR/VLR (finally!)|30min|
105 20 laforge
|sec,schneider|Iridium decoding update|?|
106 18 laforge
|tnt|[[OsmocomGMR:]] update|30min|
107 1 laforge
|zecke|SMSC and SS7 core project update|30min|
108 41 tsaitgaist
|laforge?|LTE network architecture + protocol stacks ovewview|60min|
109 1 laforge
|laforge?|Using asciidoc + mscgen + graphviz + packetdiag toolchain for writing documentation|30min|
110 29 Hoernchen
|?|re-starting the use of doxygen in (at least) libosmo*|15min|
111 1 laforge
|hoernchen|more sdrangelove, android|20-30m|
112 41 tsaitgaist
|steve-m|Globalstar introduction|20-30m|
113
|kevin+nico|TacDB|? m|
114 39 tnt
115 17 laforge
116
h3. Workshop / Hacking
117
118 1 laforge
119 23 laforge
|_.Who|_.What|_.How long|
120 1 laforge
|?|Let's try to use srsUE|?|
121 35 msuraev
|max?|patchwork migration - let's cleanup leftover patches|?|
122 17 laforge
123
h3. Avoiding dehydration during the day
124
125 1 laforge
126
IN-Berlin has a fridge with a selection of cold beverages (lemonades, club mate, water, beers) available to be purchased
127
at extremely low prices (about 1 EUR / bottle).  There are tea and coffee-making facilities.  They also carry some candy-bar
128
type snacks.  There are several supermarkets within walking distance from the venue, if you'd like to bring your own.
129
130
h3. Lunch
131 17 laforge
132 1 laforge
133 32 laforge
Lunch catering will be brought into IN-Berlin every day.  Sponsoring is provided by "sysmocom GmbH":http://sysmocom.de/.
134 1 laforge
135 34 laforge
|_.Date|_.Supplier|_.Type of Food|
136 32 laforge
|April 21st|Seerose|Moussaka with Eggplant and Parmiggiano; Fried Vegetables; Basmati Rice; Penne with dried tomatoes, champignons, pine nuts, ruccola and Parmiggiano|
137
|April 22nd|Aapka|Shahi Bengan; Butter Chicken; Lamb Khumbi|
138
|April 23rd|Essen statt Kochen|Salads; Chicken breast with Raclette-Cheese; Pepper - Onion - fresh cheese ragout; Pasta; Rhubarb Crumble|
139
|April 24th|Partyservice Rohde|Various Salads, Roast Pork, Roast Beef, Potato Gratin|
140 1 laforge
141 32 laforge
Lunch catering will typically arrive 12.30 to 12.45, allowing us to start lunch at about 1pm.
142 17 laforge
143
h3. Dinner
144
145 1 laforge
146 33 laforge
Three is no dinner catering so far.
147 17 laforge
148 1 laforge
h2. Travel
149
150
151
152
h3. Airports
153
154 17 laforge
155
Berlin still has two active airports during [[OsmoDevCon]]2016: Tegel (TXL) and Schoenefeld (SXF).  TXL is closer to the venue.
156
157
158
h3. Train
159
160
161
You can take long distance trains to _Berlin Hauptbahnhof_ (main station), which is only 15mins walking (or 3 bus stops) from the venue.
162
163
164
h3. Public Transport
165
166 1 laforge
167
Check http://www.bvg.de/ for maps, fares, etc.
168
169 17 laforge
170
h3. Car
171
172 1 laforge
173
There is some public parking in Lehrter Str., where IN-Berlin is located, but it is quite crowded.  Parking your car might
174
not be easy.
175
176 17 laforge
177
h2. Accomodation
178
179 1 laforge
180
Berlin has tons of options, from very cheap to plush and expensive.  Pick your favourite.
181 17 laforge
182 1 laforge
The closest low-end option in walking distance (about 7 mins) is the "A&O Hostel Berlin-Hauptbahnhof":http://www.aohostels.com/en/berlin/berlin-hauptbahnhof/.
183 17 laforge
184 1 laforge
A more expensive alternative within 15 minutes of walking is "Motel One Berlin-Hauptbahnhof":http://www.motel-one.com/en/hotels/berlin/hotel-berlin-hauptbahnhof/#t=hotelinfo
185
186
h2. Who brings what kind of equipment/supplies?
187 17 laforge
188 24 laforge
|_.Qty|_.Description|_.Who|
189 18 laforge
|-|Coffee, Coffee Filters|laforge|
190
|-|Milk (for coffee)|laforge|
191 1 laforge
192 17 laforge
193 1 laforge
194 17 laforge
h3. Technical Equipment
195 1 laforge
196 24 laforge
|_.Qty|_.Description|_.Who|
197 18 laforge
|3|power strips with 10 outlets|laforge|
198
|1|Fan-less 16-port Ethernet switch for main table|laforge|
199
|plenty|Ethernet cabling in various length|laforge|
200
|1|Duct Tape|laforge|
201
|?|Various RF/SDR gear on request|tnt|
Add picture from clipboard (Maximum size: 48.8 MB)