On Monday 16 December 2013 15:22:51 Henne Vogelsang wrote:
Hey,
On 16.12.2013 14:13, Jos Poortvliet wrote:
On Thursday 12 December 2013 13:11:09 Henne Vogelsang wrote: <snip> Back on topic, the business track would be a place where we collect business related talks - about deploying Kolab or typo3 for example. Stuff most home users won't find interesting. Just like most business aren't terribly interested in Steam.
Thanks for one example. Deploying enterprise collaboration software. Anything else? I'm asking because everything I can come up with is equally interesting for businesses as it is for advanced users/admins. Examples from oSC13:
* Icinga, Puppet, Rails workshop * The GNU/Linux knowledge certification value * Introduction to MySQL Security. What's new in 5.6 * Logical Volume Manager * HA with open source
all not very interesting for Steam-Users while very interesting for businesses AND power users. So where do you draw the line?
Same way you always divide subjects in tracks - the wet-thumb method we call it in Dutch ;-) It isn't like people are only allowed to visit one track or have to pay for each track or something... Much of the ones you mention are indeed very sys admin specific, perhaps asking for business proposals will bring in something that seems quite clearly separate? If not, rename it to business and big iron track or something. Look, for me, this is as much about messaging as it is about the content. If we SAY we have a business track, we're more likely to get business proposals. Then we put them together and business people see there's something specific for them and they come. Would we have been able to have the same subjects without the track? Yes. Would we have been able to have business people join the event? Yes. But both things are easier and stronger if you make them explicit. It's about perception and communication - do we consider business an important thing for oSC? Do we want to attract business people? Then let's do this. If not, fair enough, we don't do it.
What is business related and what isn't?
Kolab is, games are not.
[...]
I'd leave it up to the CfP committee to figure out the details.
Yeah thanks. BTW you're not in the CfP team right? I am.
I'm not, atm. If you want me to - I'd be happy to help out.
Let's avoid bikeshedding, please. The question Svebor had is not about every single possible detail, but if we think it makes sense to have a business track.
Dude you're not serious, how can we decide on such a question with details on the level of "Kolab-not-Steam"?
Because it's a matter of principle. Dividing things between tracks is ALWAYS complicated - overlap is the norm, not the exception. So we have to decide if we want to try and provide a track for business, or not. We have some examples and a long mail detailing pro's and con's. If we can't decide on the big picture, the color of the shed is immaterial.
Henne