t je 15.5.2017 ob 16:12 napisal:
>> >>>
>> >>> No, and that's sort of the issue at hand here. I've requested these
>> >>>
>> >>>> mailing list changes because the dev@ traffic is typically github o
No, and that's sort of the issue at hand here. I've requested these
> >>>
> >>>> mailing list changes because the dev@ traffic is typically github or
> >>>> JIRA
> >>>> chatter. We have no on list discussions. I'm basically trying
e another via email, since our other
>>>> attempts have not worked out well.
>>>>
>>>> I would expect that Slack discussions are summarized here by those
>>>> participating in them. Not automatically.
>>>>
>>>> John
>
e, May 9, 2017, 21:43 John D. Ament wrote:
All,
Based on a brief chat on Slack, I'm going to go ahead and create two new
mailing lists:
- commits@
- issues@
The reason being, the dev list is designed for developer discussions,
but
most of the banter is on JIRA issues or GitHub PRs/commits.
zin
>> wrote:
>>
>> I missed the Slack chat, but sounds good +1. Is there an easy way to get a
>>> digest of the slack chat over dev mailing list?
>>>
>>> On Tue, May 9, 2017, 21:43 John D. Ament wrote:
>>>
>>> All,
>>>>
&
May 9, 2017 at 10:00 PM Arthur Berezin
wrote:
I missed the Slack chat, but sounds good +1. Is there an easy way to get a
digest of the slack chat over dev mailing list?
On Tue, May 9, 2017, 21:43 John D. Ament wrote:
All,
Based on a brief chat on Slack, I'm going to go ahead and cr
est of the slack chat over dev mailing list?
>
> On Tue, May 9, 2017, 21:43 John D. Ament wrote:
>
> > All,
> >
> > Based on a brief chat on Slack, I'm going to go ahead and create two new
> > mailing lists:
> >
> > - commits@
> > - issues@
>
I missed the Slack chat, but sounds good +1. Is there an easy way to get a
digest of the slack chat over dev mailing list?
On Tue, May 9, 2017, 21:43 John D. Ament wrote:
> All,
>
> Based on a brief chat on Slack, I'm going to go ahead and create two new
> mailing lis
All,
Based on a brief chat on Slack, I'm going to go ahead and create two new
mailing lists:
- commits@
- issues@
The reason being, the dev list is designed for developer discussions, but
most of the banter is on JIRA issues or GitHub PRs/commits. To effectively
measure the community ope