Hi all,
I've a pull request[1] to try to improve how the Beam site guides people to
these channels. Would someone take a look?
The PR encourages users to use SO and user@. Depending on others' opinion,
we can also mention slack.
The PR also attempts to improve the bottom links on the website for u
Sorry for late answer. The issue here is that once we have a
communication channel, users expect
answers on it. Python SDK is getting momentum and we need to serve users where
they are (as mentioned by others above).
One strong advantage of 'real-time' communication (Slack/IRC) is that it is
bette
For the Go SDK, emailing the dev list or asking on Slack are probably the
best ways to get an answer from me. I'm not in the habit to search for open
Go SDK questions on stack overflow right now, but will chip in if they're
pointed out to me
As Alexey mentions, Slack largely works for quick back a
Pablo, thank you for raising this question.
I can’t say for Python, but as a someone, who tries to keep an eye on Java SDK
related questions on ML/Slack/SO for a while, I’d say that Slack is not very
effective for this.
There are several reasons for that:
- People tend to expect a quick feedbac
I pinned a message to #beam reminding people of the user@, but pinned
messages aren't immediately visible. We might be better off editing the
topic, which always appears at the top of the channel, to include
https://beam.apache.org/community/contact-us/ or links to user@ and SO. We
should also add
+Ismaël Mejía can you share your impressions from
Slack? Do you think Java/Python/other users get appropriate support there?
On Fri, Sep 6, 2019 at 7:16 PM Ahmet Altay wrote:
> I agree Slack can be used by Beam users and it would be good to meet users
> where they are. If I understand correctly
I agree Slack can be used by Beam users and it would be good to meet users
where they are. If I understand correctly, the issue Pablo is raising is
that there are not enough people online in Slack that can answer python
questions. We also need to help people who ask questions and who can answer
the
I see no reason slack can't be suitable for Beam users -- other open source
projects do utilize Slack for user chatter, too. Though what it could be
is different from how currently used. There are 173 accounts in
#beam-python, and a decent portion of recent conversations (at quick
glance) look li
Both StackOverflow and mailing lists have better answer rates for python
questions. Suggesting either one of them makes sense. I also find
StackOverflow easier to use but that is a personal preference. The
original problem is that lack of support within Slack. Both mailing list
and stackoverflow a
+1 to StackOverflow first, though I'm not important for Beam Python users.
Udi has a good point about discussions. If an SO question has a lot of back
and forth, or no response, then it is good to point to other channels the
user might try next.
Kenn
On Fri, Sep 6, 2019 at 2:20 PM Robert Bradshaw
I would also suggest SO as the best alternative, especially due to its
indexability and searchability. If discussion is needed, the users
list (my preference) or slack can be good options, and ideally the
resolution is brought back to SO.
On Fri, Sep 6, 2019 at 1:10 PM Udi Meiri wrote:
>
> I don'
I don't go on Slack, but I will be notified of mentions. It has the
advantage of being an informal space.
SO can feel just as intimidating as the mailing list IMO. Unlike the
others, it doesn't lend itself very well to discussions (you can only post
comments or answers).
On Fri, Sep 6, 2019 at 1
Hello all,
THE SITUATION:
It was brought to my attention recently that Python users in Slack are not
getting much support, because most of the Beam Python-knowledgeable people
are not on Slack. Unfortunately, in the Beam site, we do refer people to
Slack for assistance[1].
Java users do receive r
13 matches
Mail list logo
