so regarding https://github.com/JetBrains/kotlin-web-site/blob/master/pages/community/slackccugl.md: - threads are a bit of a controversial topic. if we encourage them, we should state how to correctly use them. - we have both #beginner and #getting-started, aren't those kinda the same? - I would suggest adding to the list: #feed, #random, #spring

Disagreements on things are fine, argumentative behaviour or trolling are not.

Argumentative has double meaning, I believe that in the Code of Conduct the word is used in its more general meaning, but in science and law it is understood differently:

Argumentative

Argumentative is an evidentiary objection raised in response to a question which prompts a witness to draw inferences from facts of the case.

So you can imagine my shock when I'm reading in the code of conduct something that to me and many others who work/read science and law stuff means following: you can disagree but it is not OK to use evidence to argue your point.

I'm curious about something. I've noticed that different channels here seem to have different tolerances for arguably off-topic conversations. I've noticed in particular that most #rx discussions are not really Kotlin related. I am not complaining about this; in fact the opposite. Perhaps selfishly because I am still learning how to use RxJava, a lot of these discussions have been very valuable to me. I actually find myself tempted to ask questions there that I know aren't Kotlin related, but I don't want to violate the rules or the norms of this Slack. So, does anyone have any thoughts on this? Should the norms for various channels be established "de facto" (organically) or should they be more strict? (tl;dr version: Can I ask my general Rx questions in #rx ? 😄 )

... doesn't do anything.

📣 we are approaching uploaded files size limit. Not tomorrow, but soon. From quick look top user is #tornadofx sharing videos. Any ideas on how to deal with it?

Not sure where I should raise that, but it seems Youtrack does not manage patch release. Nothing new but I do think with the new versioning scheme it will be quite confusing. Defining fixed version to

1.1.4

when fixed on

1.1.4-3

is barely ok, but defining

1.1.50

when the bug is actually fixed in

1.1.51

is super confusing IMO. Cf. https://youtrack.jetbrains.com/issue/KT-20411

there's this one that just has un unrelated name : 🐥

the :wrong_channel: slack logo?

It's prohibitively expensive to pay for the commercial slack with the number of users we have here. As a solution to the problem you describe, I tend to just screenshot or copy-paste to my notes database if I notice something of interest.

Should we somehow enforce rules of this slack if they are being purposefully ignored? e.g. we have this

Job ads should have a specific description of what is expected, location, remote/on-site, and salary range

in #hiring, but there are some posts there authors of which decline to give salary range even in PM.

but I think a quick “hey, you probably wanna join #android” or “try the quick switcher, search for `getting started`” would go a long way

If I've found a question on StackOverflow that's Kotlin related, but hasn't had an answer yet, is it frowned upon to post that same question in this slack (in the efforts for it to be seen by someone who can answer)?

Hey guys, I've been thinking about a rational metaprogramming framework for Kotlin. Wrote a blurb to better express myself, but what are your thoughts?

Disregard then

our own instance hasn’t been recording since December, it looks like https://kotlinlang.slackarchive.io/general/page-100

Is there a policy around creating channels? I published a Kotlin-related library and was wondering if it’s okay to create a channel here. https://robfletcher.github.io/strikt/

Here are a couple suggestions: - Allow guilds to customize their structure more, similar to Discord - Add highlight.js support! It's not difficult, and would greatly improve UX - Dark theme would be nice to have

Probably the better option, UX-wise

As a reaction to the discussion around java_questions's question in #general: I find the way we quickly disregard non-kotlin questions a bit frustrating in more focused channels such as #gradle #intellij #spring etc. I do understand the reasoning behind it but I wish we could relax the requirements a bit because: 1. This is the only java-ecosystem slack-like community I know of. 2. It's attended by thousands of people with similar mindset and programming approaches as me. 3. The turn around for getting an answer is 100x faster than Stack Overflow. I realize these reasons are quite selfish but it's just how I feel.

BDW @orangy, I started posting sometimes on Twitter some awesome or crazy Kotlin examples like this one: https://twitter.com/marcinmoskala/status/1009016606947729410 https://twitter.com/marcinmoskala/status/1007640373970329600 https://twitter.com/marcinmoskala/status/1011953526904246272 https://twitter.com/marcinmoskala/status/1018786619636224000 https://twitter.com/marcinmoskala/status/1031142833816842240 Do you think it is fine to share them on #feed? I preasummed that they are too small and I would be spammy.

What do you peeps think? Is this a mad idea? https://twitter.com/pablisc0/status/1035469304697946112

Are http://slack.kotl.in/ invite requests no longer being processed automatically? I've been encouraging our #san-diego Kotlin User Group members to join and participate, but in just the last couple weeks I've had two inquire about not receiving an invite after they'd submitted a request days before.

@ianbrandt they are being processed manually on a daily basis.

Should #kotlin-dsl be deleted? There is no activity and #gradle already covers this topic (actually Kotlin DSL is the main topic there). I propose delete to avoid confusion like in this thread: https://kotlinlang.slack.com/archives/C0B8M7BUY/p1536788071000100

There are always people asking in #android for general android help. Thoughts on an additional

android-general

chat to direct these questions to?

I think #coroutine was created by mistake.

The

:suspend:

emoji is too small compared to the others: :kotlin: 😒uspend: :android:

I've recently recreated that icon in a larger size – feel free to use it. It's not exact, but should be enough for an emoji…