Collecting requirements for a KDE-wide instant messaging solution (was: Re: radical proposal: move IRC to Rocket.Chat)

[Martin Klapetek]

On Wed, Aug 9, 2017 at 2:20 PM, Thomas Pfeiffer <thomas.pfeiffer at kde.org>
wrote:

>
> > On 09 Aug 2017, at 20:00, Boudewijn Rempt <boud at valdyas.org> wrote:
> >
> > On Wed, 9 Aug 2017, Thomas Pfeiffer wrote:
> >
> >> So unless someone can give me an example of an organization younger
> than 10
> >> years, with predominantly people younger than 25,
> >
> > Is there any such organization at all?
> >
>
> Sure there is! Look at the tech startup scene, or the games industry.
> But okay, let’s say “predominantly younger than 30” to make it an easier
> task.
>

Can confirm. I work in a tech startup less than 10 years
old with people predominantly younger than 30. We use
emails internally only for announcements (max 2 per week).
For everything else we use instant messaging. In fact, we
have all the tooling hooked up to the IM, so even new code
review or failed CI pings you on the IM. Heck, we even hooked
the main door lock to the IM, so you can open doors with
a simple message (has proper auth and everything).

>From seeing other startups in the neighbourhood, I can
tell you that all of those I've seen are like that - using whatever
is the latest hip IM client because startups have to be "cool".
And that raised a generation of engineers that take it for granted
that orgs they'd be potentially interested in use some 21st
century chat stack (but not only, GitHub is another great example).
If they don't, they're automatically less interested.

I agree with Thomas. If this is the kind of talent we'd like to
attract, we need evolve.

Cheers
--
Martin Klapetek
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/kde-community/attachments/20170809/67168709/attachment.htm>