> > One could even structure it further and say we have one user day, oneWell, the topics are invariably different. A user (aka "operator")
> > public 'Osmocom cellular developer day' and then the closed 'OsmoDevCon
> > classic', maybe reduced from 4 days to 3 or even 2 days only?
>
> Not sure why public developer part can't be a part of the public user
> part? Lets just find a good name for it which doesn't contain word
> "user". :)
cares about configuration + running + monitoring [the software], while a
developers care about code architecture, interfaces, testing, etc.
In general, there is not much overlap betwene those two groups,
particularly not as their respective orgaization gets larger.
Hence my proposal to split the two. Of course it could e a
"morning/afternoon", a "day 1/day 2" or a "2 tracks in parallel" split