Thanks everybody for your feedback!
I also agree, that dev@ is mostly like a forum for every topics potentially
related to Beam improvement (in different ways, not only the code) and I’d ask
more developers to take a look on user@ from time to time as well (even if it’s
not very active but we
> I would say that it is on us to redirect traffic to the correct place if
we want to effect a change.
+1 to this.
I think the clean way to accomplish this is to say: "Let's continue this
conversation on user@", add user@ and move dev@ to bcc (to avoid the
fork), then (hopefully), answer the
I am in the same boat: I'm subscribed to both but the dev@ ones are more
visible to me. That being said, I do think it's valuable to have segregated
discussion (otherwise why have two lists), and "lurkers" on users@ can
learn from questions answered there.
I would say that it is on us to redirect
My impression is that Boyuan is right: People may email dev@ because they
may feel they're more likely to get a response. I'll confess that I am
subscribed to both, but pay more attention to dev : /
On Wed, Mar 10, 2021 at 2:16 PM Kenneth Knowles wrote:
> Note on the data: dev@ is much higher
Note on the data: dev@ is much higher volume than user@ right now (maybe
2x?). [1] [2]
I think https://beam.apache.org/community/contact-us/ has an OK
description. I guess we could make it more clear about "Developer and
contributor discussions" / "Developer mailing list" to mean that it is
about
> On 10 Mar 2021, at 22:13, Onur Ozer wrote:
>
> One of the sample mails belongs to me, sorry for that. I thought the dev list
> was a better place. Will ask similar to the other list as well.
Onur,
Well, I just picked up a random example of one of the latest emails, that, I
believe, should
I subscribed to both user@ and dev@. It seems to me that we have more
active folks who have knowledge to offer help on the dev@ than the user@.
It's always good to have dev@ and user@ for different usages as long as dev@
and user@ are almost equivalent helpful for dev/users to look for help.
On
One of the sample mails belongs to me, sorry for that. I thought the dev
list was a better place. Will ask similar to the other list as well.
On Wed, Mar 10, 2021 at 12:13 PM Steve Niemitz wrote:
> As a frequent emailer of dev@, I'll admit that it's often very difficult
> to figure out if I
As a frequent emailer of dev@, I'll admit that it's often very difficult to
figure out if I should be emailing user@ or dev@, and typically just chose
dev@ because it seems more likely to get an answer there. Having clearer
guidelines around what is a "dev" topic would be very useful to better
On Wed, Mar 10, 2021 at 11:16 AM Alexey Romanenko
wrote:
>
>
> What do you think should be the right behaviour for managing such emails?
>> Forward this email to user@ (and remove dev@ address from copy) and ask
>> politely to continue a discussion there? I tried it several times but
>>
> What do you think should be the right behaviour for managing such emails?
> Forward this email to user@ (and remove dev@ address from copy) and ask
> politely to continue a discussion there? I tried it several times but
> sometimes it happened that discussion was "forked” and continued in
On Wed, Mar 10, 2021 at 10:36 AM Alexey Romanenko
wrote:
> Hello all,
>
> A quick question about our mailing lists policy.
>
> Quite often I see that people tend to send the user-related questions to
> dev@. For example: [1], [2] and many similar ones.
>
> I believe it’s a bad practice since
Hello all,
A quick question about our mailing lists policy.
Quite often I see that people tend to send the user-related questions to dev@.
For example: [1], [2] and many similar ones.
I believe it’s a bad practice since it's mixing up with other dev-related
threads and makes it difficult to
13 matches
Mail list logo
