Re: A little annoying development with emails and "integration" with other tooling ...

[Claude Edney]

I totally agree Christopher and I thank you for acknowledging me because you 
can easily get confused and lost with so many mailing list emails lol. I would 
like to add in the friendliest manner, can the origination of the projects 
followed by a small synopsis rehashing what some may have missed would be 
awesome. Not only are the subject lines for projects confusing, but also their 
responses. This makes the journey and destination of the project ambiguous in 
definition and difficult to jump in if you missed communications in the chain. 
Thanks again for inquiring and I am happy to help when I can, I apologize for 
not being as active as I was previously in communications due to work; however 
I deeply believe in the projects including their troubleshoots. If I cannot get 
on a project I do want to follow it through the email chain for educational 
purposes as well. Thanks again and hope all is well!

Claude 

Sent from my iPhone

> On May 8, 2019, at 6:04 AM, Lars Francke  wrote:
> 
> Hi Chris,
> 
> I partially agree with you.
> 
> I agree with Github pull requests. They are hard to follow and hard to read
> (and I don't only mean the mails but also on the site itself).
> 
> I disagree with the Jira mails though. I wouldn't really know how to
> improve those and I like that the discussion is part of the issue itself
> and I don't agree that this has changed recently. Jira discussions have
> been happening like this for years at least in the projects I'm working on,
> so nothing really has changed there. They can't really put much content in
> the subject?
> 
> I also dislike that it's getting harder to keep track of things with
> Github + Jira. There are open Jira issues with "Pending Review" (or
> similar) state and there are open Pull requests where there used to be only
> one place.
> 
> Do you have any suggestions on how to improve this?
> 
> Cheers,
> Lars
> 
> On Wed, May 8, 2019 at 10:13 AM Christofer Dutz 
> wrote:
> 
>> Hi all,
>> 
>> I have noticed in a lot of projects I am involved in, that my active
>> participation has dropped with more and more communities shifting to
>> discuss things in jira and using github code reviews.
>> 
>> Usually I used the title of emails to decide on which discussions I should
>> follow … this worked great till all topics sort of start with:
>> 
>> [jira][someoperation][somproject-someissueid] some description
>> 
>> Or even worse:
>> 
>> [GitHub] [someproject] someone commented on a change in pull request
>> #someid: some description
>> 
>> …
>> 
>> Is it just me, or do you also have problems mass-scanning mailinglists
>> with these titles in most of their emails?
>> I mean … I am currently following about 30-40 email lists and I really
>> have to be efficient in keeping up to date.
>> 
>> For me I think it’s really damaging as I am not willing to manually go
>> through all the Jira issues and github pull requests or github issues to
>> scan through masses of emails to find the usually minimal information they
>> contain.
>> Especially github reviews really piss me off as the net information
>> content for each of these emails is minimal their use is minimal as the
>> context isn’t contained and I have to click on 10 emails to get the point
>> of one single review.
>> 
>> I think it’s great to be open to changes, but we really have to ensure we
>> don’t lose what has been good.
>> 
>> What do you think?
>> 
>> Chris
>> 
>> 
>> 


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: A little annoying development with emails and "integration" with other tooling ...

[Christofer Dutz]

Hi Dave,

Thank you very much ... highly appreciated 
:-)

Chris

Am 08.05.19, 21:26 schrieb "Dave Fisher" :

Hi -

I’ve submitted INFRA-18350 Gitbox - Improve Generated Email Subjects

I’ve suggested a shorter, more consistent email subject. Threading is being 
worked on slowly.

Regards,
Dave

> On May 8, 2019, at 7:15 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> I find it nearly impossible to follow GitHub (GitBox) emails. I know 
Infra has done some work on threading these which has improved the situation. 
More needs to be done to improve the subjects. Perhaps we can also create 
digest emails.
> 
> For JIRA I guess since I’ve used JIRA off and on since JIRA version 1 AND 
it is easier to have a meaningful subject I’m less concerned.
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On May 8, 2019, at 4:24 AM, Christofer Dutz  
wrote:
>> 
>> Hi Lars,
>> 
>> I agree that Jira emails have been there for quite some time. 
>> It seems as more projects are starting to discuss things in jira.
>> What I'm more referring to is that with the jira issues, it would be 
great if the title of these emails could be stripped down drastically.
>> Could imagine the email of the user doing something being used as sender 
and for example strip down the whole "JIRA Christofer Dutz commented on 
PLC4X-0815: yadda yadda" to something like "PLC4X-0815: yadda yadda (New 
comment)"
>> It's all this nonsense prefix to the interesting part of the mail title 
I'm mostly criticizing. 
>> Besides the lack of content in the GitHub emails, which is a second 
issue for me.
>> 
>> Chris
>> 
>> 
>> 
>> Am 08.05.19, 12:05 schrieb "Lars Francke" :
>> 
>>   Hi Chris,
>> 
>>   I partially agree with you.
>> 
>>   I agree with Github pull requests. They are hard to follow and hard to 
read
>>   (and I don't only mean the mails but also on the site itself).
>> 
>>   I disagree with the Jira mails though. I wouldn't really know how to
>>   improve those and I like that the discussion is part of the issue 
itself
>>   and I don't agree that this has changed recently. Jira discussions have
>>   been happening like this for years at least in the projects I'm 
working on,
>>   so nothing really has changed there. They can't really put much 
content in
>>   the subject?
>> 
>>   I also dislike that it's getting harder to keep track of things with
>>   Github + Jira. There are open Jira issues with "Pending Review" (or
>>   similar) state and there are open Pull requests where there used to be 
only
>>   one place.
>> 
>>   Do you have any suggestions on how to improve this?
>> 
>>   Cheers,
>>   Lars
>> 
>>   On Wed, May 8, 2019 at 10:13 AM Christofer Dutz 

>>   wrote:
>> 
>>> Hi all,
>>> 
>>> I have noticed in a lot of projects I am involved in, that my active
>>> participation has dropped with more and more communities shifting to
>>> discuss things in jira and using github code reviews.
>>> 
>>> Usually I used the title of emails to decide on which discussions I 
should
>>> follow … this worked great till all topics sort of start with:
>>> 
>>> [jira][someoperation][somproject-someissueid] some description
>>> 
>>> Or even worse:
>>> 
>>> [GitHub] [someproject] someone commented on a change in pull request
>>> #someid: some description
>>> 
>>> …
>>> 
>>> Is it just me, or do you also have problems mass-scanning mailinglists
>>> with these titles in most of their emails?
>>> I mean … I am currently following about 30-40 email lists and I really
>>> have to be efficient in keeping up to date.
>>> 
>>> For me I think it’s really damaging as I am not willing to manually go
>>> through all the Jira issues and github pull requests or github issues to
>>> scan through masses of emails to find the usually minimal information 
they
>>> contain.
>>> Especially github reviews really piss me off as the net information
>>> content for each of these emails is minimal their use is minimal as the
>>> context isn’t contained and I have to click on 10 emails to get the 
point
>>> of one single review.
>>> 
>>> I think it’s great to be open to changes, but we really have to ensure 
we
>>> don’t lose what has been good.
>>> 
>>> What do you think?
>>> 
>>> Chris
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: 

Re: A little annoying development with emails and "integration" with other tooling ...

[Dave Fisher]

Hi -

I’ve submitted INFRA-18350 Gitbox - Improve Generated Email Subjects

I’ve suggested a shorter, more consistent email subject. Threading is being 
worked on slowly.

Regards,
Dave

> On May 8, 2019, at 7:15 AM, Dave Fisher  wrote:
> 
> Hi -
> 
> I find it nearly impossible to follow GitHub (GitBox) emails. I know Infra 
> has done some work on threading these which has improved the situation. More 
> needs to be done to improve the subjects. Perhaps we can also create digest 
> emails.
> 
> For JIRA I guess since I’ve used JIRA off and on since JIRA version 1 AND it 
> is easier to have a meaningful subject I’m less concerned.
> 
> Regards,
> Dave
> 
> Sent from my iPhone
> 
>> On May 8, 2019, at 4:24 AM, Christofer Dutz  
>> wrote:
>> 
>> Hi Lars,
>> 
>> I agree that Jira emails have been there for quite some time. 
>> It seems as more projects are starting to discuss things in jira.
>> What I'm more referring to is that with the jira issues, it would be great 
>> if the title of these emails could be stripped down drastically.
>> Could imagine the email of the user doing something being used as sender and 
>> for example strip down the whole "JIRA Christofer Dutz commented on 
>> PLC4X-0815: yadda yadda" to something like "PLC4X-0815: yadda yadda (New 
>> comment)"
>> It's all this nonsense prefix to the interesting part of the mail title I'm 
>> mostly criticizing. 
>> Besides the lack of content in the GitHub emails, which is a second issue 
>> for me.
>> 
>> Chris
>> 
>> 
>> 
>> Am 08.05.19, 12:05 schrieb "Lars Francke" :
>> 
>>   Hi Chris,
>> 
>>   I partially agree with you.
>> 
>>   I agree with Github pull requests. They are hard to follow and hard to read
>>   (and I don't only mean the mails but also on the site itself).
>> 
>>   I disagree with the Jira mails though. I wouldn't really know how to
>>   improve those and I like that the discussion is part of the issue itself
>>   and I don't agree that this has changed recently. Jira discussions have
>>   been happening like this for years at least in the projects I'm working on,
>>   so nothing really has changed there. They can't really put much content in
>>   the subject?
>> 
>>   I also dislike that it's getting harder to keep track of things with
>>   Github + Jira. There are open Jira issues with "Pending Review" (or
>>   similar) state and there are open Pull requests where there used to be only
>>   one place.
>> 
>>   Do you have any suggestions on how to improve this?
>> 
>>   Cheers,
>>   Lars
>> 
>>   On Wed, May 8, 2019 at 10:13 AM Christofer Dutz 
>>   wrote:
>> 
>>> Hi all,
>>> 
>>> I have noticed in a lot of projects I am involved in, that my active
>>> participation has dropped with more and more communities shifting to
>>> discuss things in jira and using github code reviews.
>>> 
>>> Usually I used the title of emails to decide on which discussions I should
>>> follow … this worked great till all topics sort of start with:
>>> 
>>> [jira][someoperation][somproject-someissueid] some description
>>> 
>>> Or even worse:
>>> 
>>> [GitHub] [someproject] someone commented on a change in pull request
>>> #someid: some description
>>> 
>>> …
>>> 
>>> Is it just me, or do you also have problems mass-scanning mailinglists
>>> with these titles in most of their emails?
>>> I mean … I am currently following about 30-40 email lists and I really
>>> have to be efficient in keeping up to date.
>>> 
>>> For me I think it’s really damaging as I am not willing to manually go
>>> through all the Jira issues and github pull requests or github issues to
>>> scan through masses of emails to find the usually minimal information they
>>> contain.
>>> Especially github reviews really piss me off as the net information
>>> content for each of these emails is minimal their use is minimal as the
>>> context isn’t contained and I have to click on 10 emails to get the point
>>> of one single review.
>>> 
>>> I think it’s great to be open to changes, but we really have to ensure we
>>> don’t lose what has been good.
>>> 
>>> What do you think?
>>> 
>>> Chris
>>> 
>>> 
>>> 
>> 
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [DISCUSSION] Documentation Hackathons at ApacheCon

[Kenneth Knowles]

+1 from me as well, and I'll be at ApacheCon NA to help out. Are there
steps to take now, like asking in the projects to see which of your ideas
fits best? I would guess the BoF+hackathon between all the projects from
GSoD would be cool. Worst case, you have too many people writing docs in a
room...

On Fri, May 3, 2019 at 1:40 PM Aizhamal Nurmamat kyzy
 wrote:

> I think this is a fantastic idea! I fully support any effort to foster
> documentation contributions/documentation improvements. Let me know if I
> can help in any way.
>
> Thanks,
> Aizhamal
>
> *From: *Sharan Foga 
> *Date: *Fri, May 3, 2019 at 1:30 PM
> *To: * 
>
> Hi All
> >
> > Recently with the Google Season of Docs, quite a few of our projects were
> > interested in applying to get some help with their documentation, so I’m
> > thinking, what if we try and add some sort of documentation section to
> our
> > ApacheCon hackathons.
> >
> > If we have enough people from a project community we could start at a
> very
> > basic level e.g writing up some install or very basic getting started
> docs.
> >
> > Another idea is that the projects who weren’t successful in getting a
> > technical writer with Season of Docs, bring their idea and have a
> hackathon
> > or Birds of a Feather session during ApacheCon to plan, prepare or write
> > something that could help.
> >
> > At one of the previous open source summits  I attended I saw a
> > presentation on what they called ‘Book Sprints’ where a group of people
> got
> > together for a fixed time period and then wrote the documentation and
> > pubished it.  While we may not have the same time frame, perhaps doing at
> > least a documentation proof of concept could be interesting for both Las
> > Vegas and Berlin.
> >
> > What do people think?
> >
> > Thanks
> > Sharan
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> >
> >
>

Re: [VOTE] ComDev supports formation of D committee

[Kevin A. McGrail]

I'm +1 [non-binding] for splitting D from ComDev off into it's own
committee/PMC/initiative/etc.  It hasn't been done well under comdev and
it's time to give it a shot on it's own.

-KAM

On 5/8/2019 10:48 AM, Myrle Krantz wrote:
> FYI all:
>
> I'm going to call the vote on Friday morning (CET).  If it passes, I'll
> also add it to the board agenda at that time.  I ask that everyone who
> wants to participate do so by then.
>
> Best Regards,
> Myrle
>
> On Wed, May 8, 2019 at 1:53 PM Tim Williams  wrote:
>
>> -1...  it's completely unnecessary (as the work could easily be done under
>> the CommDev banner) and gives the sense of "action" towards a cause without
>> actually solving any real problem.  Ironically, I predict it will fracture
>> the community and have the effect of removing diversity of views on this
>> very subject - creating an echo-chamber.  It'll pass though, so best
>> wishes...
>>
>> Thanks,
>> --tim
>>
>> On 2019/05/04 22:06:47, Myrle Krantz  wrote:
>>> I propose that ComDev submmit the following statement to the board:
>>>
>>> "The ComDev PMC hereby requests that the board create a President's
>>> committee tasked with supporting our communities in their efforts to be
>>> diverse and welcoming places, and tasked with helping the ASF formulate a
>>> strategy to improve our diversity and inclusiveness.  The ComDev PMC
>>> likewise formally requests that the new committee look for ways in which
>>> ComDev can support our progress in these areas."
>>>
>>> Here's my +1.
>>>
>>> Best Regards,
>>> Myrle
>>> PMC Member, Apache Community Development
>>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [VOTE] ComDev supports formation of D committee

[Myrle Krantz]

FYI all:

I'm going to call the vote on Friday morning (CET).  If it passes, I'll
also add it to the board agenda at that time.  I ask that everyone who
wants to participate do so by then.

Best Regards,
Myrle

On Wed, May 8, 2019 at 1:53 PM Tim Williams  wrote:

> -1...  it's completely unnecessary (as the work could easily be done under
> the CommDev banner) and gives the sense of "action" towards a cause without
> actually solving any real problem.  Ironically, I predict it will fracture
> the community and have the effect of removing diversity of views on this
> very subject - creating an echo-chamber.  It'll pass though, so best
> wishes...
>
> Thanks,
> --tim
>
> On 2019/05/04 22:06:47, Myrle Krantz  wrote:
> > I propose that ComDev submmit the following statement to the board:
> >
> > "The ComDev PMC hereby requests that the board create a President's
> > committee tasked with supporting our communities in their efforts to be
> > diverse and welcoming places, and tasked with helping the ASF formulate a
> > strategy to improve our diversity and inclusiveness.  The ComDev PMC
> > likewise formally requests that the new committee look for ways in which
> > ComDev can support our progress in these areas."
> >
> > Here's my +1.
> >
> > Best Regards,
> > Myrle
> > PMC Member, Apache Community Development
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: A little annoying development with emails and "integration" with other tooling ...

[Dave Fisher]

Hi -

I find it nearly impossible to follow GitHub (GitBox) emails. I know Infra has 
done some work on threading these which has improved the situation. More needs 
to be done to improve the subjects. Perhaps we can also create digest emails.

For JIRA I guess since I’ve used JIRA off and on since JIRA version 1 AND it is 
easier to have a meaningful subject I’m less concerned.

Regards,
Dave

Sent from my iPhone

> On May 8, 2019, at 4:24 AM, Christofer Dutz  wrote:
> 
> Hi Lars,
> 
> I agree that Jira emails have been there for quite some time. 
> It seems as more projects are starting to discuss things in jira.
> What I'm more referring to is that with the jira issues, it would be great if 
> the title of these emails could be stripped down drastically.
> Could imagine the email of the user doing something being used as sender and 
> for example strip down the whole "JIRA Christofer Dutz commented on 
> PLC4X-0815: yadda yadda" to something like "PLC4X-0815: yadda yadda (New 
> comment)"
> It's all this nonsense prefix to the interesting part of the mail title I'm 
> mostly criticizing. 
> Besides the lack of content in the GitHub emails, which is a second issue for 
> me.
> 
> Chris
> 
> 
> 
> Am 08.05.19, 12:05 schrieb "Lars Francke" :
> 
>Hi Chris,
> 
>I partially agree with you.
> 
>I agree with Github pull requests. They are hard to follow and hard to read
>(and I don't only mean the mails but also on the site itself).
> 
>I disagree with the Jira mails though. I wouldn't really know how to
>improve those and I like that the discussion is part of the issue itself
>and I don't agree that this has changed recently. Jira discussions have
>been happening like this for years at least in the projects I'm working on,
>so nothing really has changed there. They can't really put much content in
>the subject?
> 
>I also dislike that it's getting harder to keep track of things with
>Github + Jira. There are open Jira issues with "Pending Review" (or
>similar) state and there are open Pull requests where there used to be only
>one place.
> 
>Do you have any suggestions on how to improve this?
> 
>Cheers,
>Lars
> 
>On Wed, May 8, 2019 at 10:13 AM Christofer Dutz 
>wrote:
> 
>> Hi all,
>> 
>> I have noticed in a lot of projects I am involved in, that my active
>> participation has dropped with more and more communities shifting to
>> discuss things in jira and using github code reviews.
>> 
>> Usually I used the title of emails to decide on which discussions I should
>> follow … this worked great till all topics sort of start with:
>> 
>> [jira][someoperation][somproject-someissueid] some description
>> 
>> Or even worse:
>> 
>> [GitHub] [someproject] someone commented on a change in pull request
>> #someid: some description
>> 
>> …
>> 
>> Is it just me, or do you also have problems mass-scanning mailinglists
>> with these titles in most of their emails?
>> I mean … I am currently following about 30-40 email lists and I really
>> have to be efficient in keeping up to date.
>> 
>> For me I think it’s really damaging as I am not willing to manually go
>> through all the Jira issues and github pull requests or github issues to
>> scan through masses of emails to find the usually minimal information they
>> contain.
>> Especially github reviews really piss me off as the net information
>> content for each of these emails is minimal their use is minimal as the
>> context isn’t contained and I have to click on 10 emails to get the point
>> of one single review.
>> 
>> I think it’s great to be open to changes, but we really have to ensure we
>> don’t lose what has been good.
>> 
>> What do you think?
>> 
>> Chris
>> 
>> 
>> 
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [VOTE] ComDev supports formation of D committee

[Tim Williams]

-1...  it's completely unnecessary (as the work could easily be done under the 
CommDev banner) and gives the sense of "action" towards a cause without 
actually solving any real problem.  Ironically, I predict it will fracture the 
community and have the effect of removing diversity of views on this very 
subject - creating an echo-chamber.  It'll pass though, so best wishes...

Thanks,
--tim

On 2019/05/04 22:06:47, Myrle Krantz  wrote: 
> I propose that ComDev submmit the following statement to the board:
> 
> "The ComDev PMC hereby requests that the board create a President's
> committee tasked with supporting our communities in their efforts to be
> diverse and welcoming places, and tasked with helping the ASF formulate a
> strategy to improve our diversity and inclusiveness.  The ComDev PMC
> likewise formally requests that the new committee look for ways in which
> ComDev can support our progress in these areas."
> 
> Here's my +1.
> 
> Best Regards,
> Myrle
> PMC Member, Apache Community Development
> 

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [VOTE] ComDev supports formation of D committee

[Rich Bowen]

 I too believe this to be part of ComDev's charter, but it is clear that we
have done little to address it since the formation of this PMC. So indeed
perhaps it is the time to try something new.

+1 to that something new although I remain ambivalent to what specific form
this committee/pmc/thingy should take.

On Mon, May 6, 2019, 06:55 Ulrich Stärk  wrote:

> +0
>
> not sure if a president's committee is the best way of getting this done
> or whether it would be
> better to have it as part of comdev. But better do something than nothing
> at all. Plus, we can fix
> stuff later so I'll leave it to those wanting to drive it to figure it out.
>
> Uli
>
> On 05.05.19 00:06, Myrle Krantz wrote:
> > I propose that ComDev submmit the following statement to the board:
> >
> > "The ComDev PMC hereby requests that the board create a President's
> > committee tasked with supporting our communities in their efforts to be
> > diverse and welcoming places, and tasked with helping the ASF formulate a
> > strategy to improve our diversity and inclusiveness.  The ComDev PMC
> > likewise formally requests that the new committee look for ways in which
> > ComDev can support our progress in these areas."
> >
> > Here's my +1.
> >
> > Best Regards,
> > Myrle
> > PMC Member, Apache Community Development
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: A little annoying development with emails and "integration" with other tooling ...

[Christofer Dutz]

Hi Lars,

I agree that Jira emails have been there for quite some time. 
It seems as more projects are starting to discuss things in jira.
What I'm more referring to is that with the jira issues, it would be great if 
the title of these emails could be stripped down drastically.
Could imagine the email of the user doing something being used as sender and 
for example strip down the whole "JIRA Christofer Dutz commented on PLC4X-0815: 
yadda yadda" to something like "PLC4X-0815: yadda yadda (New comment)"
It's all this nonsense prefix to the interesting part of the mail title I'm 
mostly criticizing. 
Besides the lack of content in the GitHub emails, which is a second issue for 
me.

Chris



Am 08.05.19, 12:05 schrieb "Lars Francke" :

Hi Chris,

I partially agree with you.

I agree with Github pull requests. They are hard to follow and hard to read
(and I don't only mean the mails but also on the site itself).

I disagree with the Jira mails though. I wouldn't really know how to
improve those and I like that the discussion is part of the issue itself
and I don't agree that this has changed recently. Jira discussions have
been happening like this for years at least in the projects I'm working on,
so nothing really has changed there. They can't really put much content in
the subject?

I also dislike that it's getting harder to keep track of things with
Github + Jira. There are open Jira issues with "Pending Review" (or
similar) state and there are open Pull requests where there used to be only
one place.

Do you have any suggestions on how to improve this?

Cheers,
Lars

On Wed, May 8, 2019 at 10:13 AM Christofer Dutz 
wrote:

> Hi all,
>
> I have noticed in a lot of projects I am involved in, that my active
> participation has dropped with more and more communities shifting to
> discuss things in jira and using github code reviews.
>
> Usually I used the title of emails to decide on which discussions I should
> follow … this worked great till all topics sort of start with:
>
> [jira][someoperation][somproject-someissueid] some description
>
> Or even worse:
>
> [GitHub] [someproject] someone commented on a change in pull request
> #someid: some description
>
> …
>
> Is it just me, or do you also have problems mass-scanning mailinglists
> with these titles in most of their emails?
> I mean … I am currently following about 30-40 email lists and I really
> have to be efficient in keeping up to date.
>
> For me I think it’s really damaging as I am not willing to manually go
> through all the Jira issues and github pull requests or github issues to
> scan through masses of emails to find the usually minimal information they
> contain.
> Especially github reviews really piss me off as the net information
> content for each of these emails is minimal their use is minimal as the
> context isn’t contained and I have to click on 10 emails to get the point
> of one single review.
>
> I think it’s great to be open to changes, but we really have to ensure we
> don’t lose what has been good.
>
> What do you think?
>
> Chris
>
>
>



-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: A little annoying development with emails and "integration" with other tooling ...

[Claude Warren]

Christofer,

I have to agree, the projects I have been involved with are getting harder
to follow.  Too much noise in the signal.  However, I do not have any
constructive suggestions at this time.

I keep thinking there could be an app/tool that 

but then I remember Claude's Law:"There is no first world problem that can
not be made worse by an app."

Claude

On Wed, May 8, 2019 at 9:13 AM Christofer Dutz 
wrote:

> Hi all,
>
> I have noticed in a lot of projects I am involved in, that my active
> participation has dropped with more and more communities shifting to
> discuss things in jira and using github code reviews.
>
> Usually I used the title of emails to decide on which discussions I should
> follow … this worked great till all topics sort of start with:
>
> [jira][someoperation][somproject-someissueid] some description
>
> Or even worse:
>
> [GitHub] [someproject] someone commented on a change in pull request
> #someid: some description
>
> …
>
> Is it just me, or do you also have problems mass-scanning mailinglists
> with these titles in most of their emails?
> I mean … I am currently following about 30-40 email lists and I really
> have to be efficient in keeping up to date.
>
> For me I think it’s really damaging as I am not willing to manually go
> through all the Jira issues and github pull requests or github issues to
> scan through masses of emails to find the usually minimal information they
> contain.
> Especially github reviews really piss me off as the net information
> content for each of these emails is minimal their use is minimal as the
> context isn’t contained and I have to click on 10 emails to get the point
> of one single review.
>
> I think it’s great to be open to changes, but we really have to ensure we
> don’t lose what has been good.
>
> What do you think?
>
> Chris
>
>
>

-- 
I like: Like Like - The likeliest place on the web

LinkedIn: http://www.linkedin.com/in/claudewarren

Re: A little annoying development with emails and "integration" with other tooling ...

[Lars Francke]

Hi Chris,

I partially agree with you.

I agree with Github pull requests. They are hard to follow and hard to read
(and I don't only mean the mails but also on the site itself).

I disagree with the Jira mails though. I wouldn't really know how to
improve those and I like that the discussion is part of the issue itself
and I don't agree that this has changed recently. Jira discussions have
been happening like this for years at least in the projects I'm working on,
so nothing really has changed there. They can't really put much content in
the subject?

I also dislike that it's getting harder to keep track of things with
Github + Jira. There are open Jira issues with "Pending Review" (or
similar) state and there are open Pull requests where there used to be only
one place.

Do you have any suggestions on how to improve this?

Cheers,
Lars

On Wed, May 8, 2019 at 10:13 AM Christofer Dutz 
wrote:

> Hi all,
>
> I have noticed in a lot of projects I am involved in, that my active
> participation has dropped with more and more communities shifting to
> discuss things in jira and using github code reviews.
>
> Usually I used the title of emails to decide on which discussions I should
> follow … this worked great till all topics sort of start with:
>
> [jira][someoperation][somproject-someissueid] some description
>
> Or even worse:
>
> [GitHub] [someproject] someone commented on a change in pull request
> #someid: some description
>
> …
>
> Is it just me, or do you also have problems mass-scanning mailinglists
> with these titles in most of their emails?
> I mean … I am currently following about 30-40 email lists and I really
> have to be efficient in keeping up to date.
>
> For me I think it’s really damaging as I am not willing to manually go
> through all the Jira issues and github pull requests or github issues to
> scan through masses of emails to find the usually minimal information they
> contain.
> Especially github reviews really piss me off as the net information
> content for each of these emails is minimal their use is minimal as the
> context isn’t contained and I have to click on 10 emails to get the point
> of one single review.
>
> I think it’s great to be open to changes, but we really have to ensure we
> don’t lose what has been good.
>
> What do you think?
>
> Chris
>
>
>

A little annoying development with emails and "integration" with other tooling ...

[Christofer Dutz]

Hi all,

I have noticed in a lot of projects I am involved in, that my active 
participation has dropped with more and more communities shifting to discuss 
things in jira and using github code reviews.

Usually I used the title of emails to decide on which discussions I should 
follow … this worked great till all topics sort of start with:

[jira][someoperation][somproject-someissueid] some description

Or even worse:

[GitHub] [someproject] someone commented on a change in pull request #someid: 
some description

…

Is it just me, or do you also have problems mass-scanning mailinglists with 
these titles in most of their emails?
I mean … I am currently following about 30-40 email lists and I really have to 
be efficient in keeping up to date.

For me I think it’s really damaging as I am not willing to manually go through 
all the Jira issues and github pull requests or github issues to scan through 
masses of emails to find the usually minimal information they contain.
Especially github reviews really piss me off as the net information content for 
each of these emails is minimal their use is minimal as the context isn’t 
contained and I have to click on 10 emails to get the point of one single 
review.

I think it’s great to be open to changes, but we really have to ensure we don’t 
lose what has been good.

What do you think?

Chris