Ok, time to execute on this, please engage in
https://issues.apache.org/jira/browse/LUCENE-8951 if you want to contribute!
--
Jan Høydahl, search solution architect
Cominvent AS - www.cominvent.com
> 9. aug. 2019 kl. 01:08 skrev Namgyu Kim :
>
> +1 for issues@ and builds@
> Thanks Jan :)
>
>
+1 for issues@ and builds@
Thanks Jan :)
2019년 8월 9일 (금) 오전 3:02, Jan Høydahl 님이 작성:
> We already have commits@, so let’s go with issues@ and builds@
>
> Jan Høydahl
>
> 8. aug. 2019 kl. 18:32 skrev Namgyu Kim :
>
> +1 to Jan's idea :D
> I think it's better to split the mailing list.
>
> But I
> Maybe just JIRA is fine here since it's the master place holding the issue
> status.
+1
> we could get the dev list subscribed for a daily summary email. WDYT?
This is quick to test out and would probably work well.
Or perhaps, as Alexandre does with his filtering, only subscribe to
On Thu, Aug 8, 2019 at 2:42 PM Jan Høydahl wrote:
> ...
> Whether [Created|Resolved] mails for JIRA/PR should also go to Dev list is
> still an open question. To help decide, here's the expected volume for
> those (from reporter.apache.org:
> 357 issues opened in JIRA, past quarter, 270 issues
We already have commits@, so let’s go with issues@ and builds@
Jan Høydahl
> 8. aug. 2019 kl. 18:32 skrev Namgyu Kim :
>
> +1 to Jan's idea :D
> I think it's better to split the mailing list.
>
> But I have a little opinion about the name.
> Which one is better, the singular(build-issue) or
+1 to Jan's idea :D
I think it's better to split the mailing list.
But I have a little opinion about the name.
Which one is better, the singular(build-issue) or the plural(builds-issues)?
Personally, "build-issue" looks better because names of the our mailing
list are used as a singular. (not
I'll let this email topic run over the weekend to attract more eyeballs. Even
if it's not a VOTE thread, feel free to add your +1 or -1's, and if others also
seem in favour of this idea then I'll start working on it next week. To sum up
what I believe to be the current consensus:
A new issues@
+1 to Jan’s idea of the bot-originated lists be announce only…..
Personally I’ve been able to make some sense out of the messages by
1> switching to the mac mail client (not an option for others, I know). It
threads pretty well and for those topics where there are 10 replies I only have
to
I apply the following (gmail) rules, just in case it helps somebody.
With this combination, I am able to track human conversations
reasonably well.
Human conversation:
Matches: from:(-g...@apache.org) subject:(-[jira]) list:
Do this: Skip Inbox, Apply label "ML/Lucene-dev"
All JIRA issues,
I don't have strong feelings for whether we have one list of two, i.e. issues@
and builds@ - I'll subscribe to them anyways. A benefit of the latter is that
the list names are intuituve and self describing.
I guess the strongest argument against would be that many will not subscribe
and miss
On 8/6/2019 5:17 PM, Jan Høydahl wrote:
Personally I think the ratio of notifications vs human emails is a bit too
high. I fear external devs who just want to follow the project may get
overwhelmed and unsubscribe.
One suggestion is therefore to add a new list where detailed JIRA comments and
+1 - Just two days ago I created a filter to send [JENKINS] emails
elsewhere... I don't want to completely unsubscribe from Lucene development
emails, but the traffic here is a bit overwhelming and it's hard to see the
signal in the noise sometimes (high recall, low precision you might say!)
On
+1
The mail list is sending so many mails that it has become difficult to catch up
On Thu, Aug 8, 2019 at 12:26 AM Michael Sokolov wrote:
>
> big +1 -- I'm also curious why the subject lines of many automated
> emails (from Jira?) start with [CREATED] even though they are
> generated by
big +1 -- I'm also curious why the subject lines of many automated
emails (from Jira?) start with [CREATED] even though they are
generated by comments or other kinds of updates (not creating a new
issue). Overall, I think we have way too much comment spam. In
particular Github comments are so
It's a problem. I am mentoring a colleague who is stressed with the
prospect of keeping up with our community because of the volume of email,
and so it's a serious barrier to community involvement. I too have email
filters to help me, and it took some time to work out a system. We could
share
Hi
+1 for separated list(s) for JIRA/Github updates and Jenkins jobs.
While I myself am not in trouble with assorting the mails thanks to
gmail filters, I know an user (external dev) who unsubscribed this
list. The one reason is the volume of the mail flow :)
Tomoko
2019年8月7日(水) 8:17 Jan
Hi
The mail volume on dev@ is fairly high, betwen 2500-3500/month.
To break down the numbers last month, see
https://lists.apache.org/trends.html?dev@lucene.apache.org:lte=1M:
Top 10 participants:
-GitBox: 420 emails
-ASF subversion and git services (JIRA): 351 emails
-Apache Jenkins Server:
17 matches
Mail list logo
