Re: drop from Daffodil PMC

[Steve Lawrence]

Will do. You're always welcome back if you decide you find the time again.

Thanks,
- Steve

On 2/3/21 1:27 PM, Fahl, Beth wrote:
> I'd like to be removed from the PMC for Daffodil but remain as a contributor. 
> My apache ID is efinnegan.
> 
> Thanks,
> Beth
> 

drop from Daffodil PMC

[Fahl, Beth]

I'd like to be removed from the PMC for Daffodil but remain as a contributor. 
My apache ID is efinnegan.

Thanks,
Beth

avoiding redundant comment and commit messages

[Interrante, John A (GE Research, US)]

I'm receiving both GitHub and GitBox notifications and I have a caveat about 
relying only on GitBox notifications besides missing comments in the "Review 
Changes" box.  The GitBox notifications seem to be sent out in batches 
considerably later (sometimes hours later) than the GitHub notifications.  I've 
added a comment to Steve's infra ticket asking Infra to speed up the batch 
frequency too.

-Original Message-
From: Steve Lawrence  
Sent: Wednesday, February 3, 2021 10:30 AM
To: dev@daffodil.apache.org
Subject: EXT: Re: avoiding redundant comment and commit messages

I had the same issue and got tired of this redundancy a while ago so I disabled 
notifications from GitHub and only rely on those notifications from Apache's 
GitBox.

I think there are two things that I no longer see, which is a bit annoying, but 
in practice hasn't been too much of an issue, so I just deal with it. Those two 
things are:

1) Pull request comments made in the "Review Changes" thing aren't sent out by 
gitbox. This sometimes means I'll miss a +1 (since this is where we often add 
hose), especially if +1 was the only comment. Inline comments do get sent out 
by gitbox though. I opened a ticket for this issue with infra but I don't think 
they've made any progress on fixing this:

https://issues.apache.org/jira/browse/INFRA-21041

2) I *think* Gitbox doesn't send out notifications when a pull request is 
updated with new commits--fixup commits are a pretty important and frequent 
part of our workflow. Fortunately, people usually add a comment when new 
commits are added, which GitBox does send out, so I don't usually don't miss 
these.


My solution for these two issues so far has just been to periodically manually 
check reviews I've made for review comments or check PR's others have made for 
updated commits. It's a bit of a manual process, but not awful, and I prefer it 
over all the double emails.

The other option would be to not subscribe to commits@daffodil.a.o, but I think 
you'd then you miss out on Jira updates, and all the other stuff that goes to 
commits@. It's definitely alot more than gitbox notifications, so probably not 
recommended. And I think the incubator prefers that all committers/PPMC members 
subscribe to commits, since it really is the only place that gives the (almost) 
complete picture of changes.

We could have suggestions that people not add "Review Changes" comments, and 
when updates are made to pull requests we always add a comment saying there's 
an update. But that's hard to remember and enforce. We really just need Infra 
to fix these issues with gitbox, but I'm not sure this is high priority. 
Though, from a traceability perspective, one could argue that there are 
comments and PR information that gitbox is missing and so isn't "happening on a 
mailing list" so maybe the priority should be pretty high for infra, since 
"happening on a mailing list" is a pretty important mantra to ASF.

- Steve



On 2/3/21 10:12 AM, Beckerle, Mike wrote:
> I seem to get two of everything.
> 
> I get one message from "GitBox" sent to commits@daffodil I get one 
> from "notificati...@github.com" to 
> incubator-daffo...@noreply.github.com
> 
> I cannot guarantee that every message always shows up to both of these.
> 
> If I unsubscribe from the latter, will I miss some things, or is all 
> the same traffic always sent to both.
> 
> Mike Beckerle | Principal Engineer
> 
> mbecke...@owlcyberdefense.com 
> 
> P +1-781-330-0412
> 
> Connect with us!
> 
>  m/owlcyberdefense>
> 
> 
> 
> **
> 
> The information contained in this transmission is for the personal and 
> confidential use of the individual or entity to which it is addressed. 
> If the reader is not the intended recipient, you are hereby notified 
> that any review, dissemination, or copying of this communication is 
> strictly prohibited. If you have received this transmission in error, 
> please notify the sender immediately
> 

Re: avoiding redundant comment and commit messages

[Steve Lawrence]

I had the same issue and got tired of this redundancy a while ago so I
disabled notifications from GitHub and only rely on those notifications
from Apache's GitBox.

I think there are two things that I no longer see, which is a bit
annoying, but in practice hasn't been too much of an issue, so I just
deal with it. Those two things are:

1) Pull request comments made in the "Review Changes" thing aren't sent
out by gitbox. This sometimes means I'll miss a +1 (since this is where
we often add hose), especially if +1 was the only comment. Inline
comments do get sent out by gitbox though. I opened a ticket for this
issue with infra but I don't think they've made any progress on fixing this:

https://issues.apache.org/jira/browse/INFRA-21041

2) I *think* Gitbox doesn't send out notifications when a pull request
is updated with new commits--fixup commits are a pretty important and
frequent part of our workflow. Fortunately, people usually add a comment
when new commits are added, which GitBox does send out, so I don't
usually don't miss these.


My solution for these two issues so far has just been to periodically
manually check reviews I've made for review comments or check PR's
others have made for updated commits. It's a bit of a manual process,
but not awful, and I prefer it over all the double emails.

The other option would be to not subscribe to commits@daffodil.a.o, but
I think you'd then you miss out on Jira updates, and all the other stuff
that goes to commits@. It's definitely alot more than gitbox
notifications, so probably not recommended. And I think the incubator
prefers that all committers/PPMC members subscribe to commits, since it
really is the only place that gives the (almost) complete picture of
changes.

We could have suggestions that people not add "Review Changes" comments,
and when updates are made to pull requests we always add a comment
saying there's an update. But that's hard to remember and enforce. We
really just need Infra to fix these issues with gitbox, but I'm not sure
this is high priority. Though, from a traceability perspective, one
could argue that there are comments and PR information that gitbox is
missing and so isn't "happening on a mailing list" so maybe the priority
should be pretty high for infra, since "happening on a mailing list" is
a pretty important mantra to ASF.

- Steve



On 2/3/21 10:12 AM, Beckerle, Mike wrote:
> I seem to get two of everything.
> 
> I get one message from "GitBox" sent to commits@daffodil
> I get one from "notificati...@github.com" to 
> incubator-daffo...@noreply.github.com
> 
> I cannot guarantee that every message always shows up to both of these.
> 
> If I unsubscribe from the latter, will I miss some things, or is all the same 
> traffic always sent to both.
> 
> Mike Beckerle | Principal Engineer
> 
> mbecke...@owlcyberdefense.com 
> 
> P +1-781-330-0412
> 
> Connect with us!
> 
> 
> 
> 
> 
> **
> 
> The information contained in this transmission is for the personal and 
> confidential use of the individual or entity to which it is addressed. If the 
> reader is not the intended recipient, you are hereby notified that any 
> review, 
> dissemination, or copying of this communication is strictly prohibited. If 
> you 
> have received this transmission in error, please notify the sender immediately
> 

[RESULT] [VOTE] Contributors - Graduate Apache Daffodil (Incubating) to a top-level project

[Mike Beckerle]

(Message text slightly revised to remove incorrect phrase about not waiting
the full time period.)

--

We have received +1 from all mentors, active PPMC, and Contributors
And the 72 hours has elapsed.

So the vote passes unanimously.

Thank you.

Next step will be to prepare (and discuss here) our proposal to the board
for graduation. This will then be voted on by the incubator PMC for
approval to take it to the ASF board. Stay tuned.

Permalink to vote thread:

https://lists.apache.org/thread.html/r91af73ae28284945ffe881cea7877766213eaa405da21e233d85eb83%40%3Cdev.daffodil.apache.org%3E

-mike beckerle

On Thu, Jan 28, 2021 at 6:08 PM Mike Beckerle  wrote:

> One of the first steps in graduating from the Apache incubator to top
> level is making sure we have consensus among our contributors that this
> makes sense now. This is an initial first step.
>
> Please reply with your vote (+1, 0, or -1 with reasons)
>
> This vote will be open for at least 72 hours (non-weekend), so until at
> least 5pm US.ET (UTC-5) on Tuesday, Feb 2.
>
> You can review our wiki page about how we meet the ASF project maturity
> model which is something projects do to self-assess before moving forward.
> Your comments on this wiki page are also welcome.
>
>
> https://cwiki.apache.org/confluence/display/DAFFODIL/Apache+Daffodil+Maturity+Model+Assesment
>
> About voting: see The Apache Voting Process:
> https://www.apache.org/foundation/voting.html if you'd like to review the
> process/guidance.
>
> My vote +1.
>


-- 
Learn CPR. Save a Life - I Did !

[RESULT] [VOTE] Contributors - Graduate Apache Daffodil (Incubating) to a top-level project

[Mike Beckerle]

We have received +1 from all mentors, active PPMC, and Contributors
And the 72 hours has elapsed.

So the vote passes unanimously, with no need to wait the full time period.

Thank you.

Next step will be to prepare (and discuss here) our proposal to the board
for graduation. This will then be voted on by the incubator PMC for
approval to take it to the ASF board. Stay tuned.

Permalink to vote thread:

https://lists.apache.org/thread.html/r91af73ae28284945ffe881cea7877766213eaa405da21e233d85eb83%40%3Cdev.daffodil.apache.org%3E

-mike beckerle

On Thu, Jan 28, 2021 at 6:08 PM Mike Beckerle  wrote:

> One of the first steps in graduating from the Apache incubator to top
> level is making sure we have consensus among our contributors that this
> makes sense now. This is an initial first step.
>
> Please reply with your vote (+1, 0, or -1 with reasons)
>
> This vote will be open for at least 72 hours (non-weekend), so until at
> least 5pm US.ET (UTC-5) on Tuesday, Feb 2.
>
> You can review our wiki page about how we meet the ASF project maturity
> model which is something projects do to self-assess before moving forward.
> Your comments on this wiki page are also welcome.
>
>
> https://cwiki.apache.org/confluence/display/DAFFODIL/Apache+Daffodil+Maturity+Model+Assesment
>
> About voting: see The Apache Voting Process:
> https://www.apache.org/foundation/voting.html if you'd like to review the
> process/guidance.
>
> My vote +1.
>

avoiding redundant comment and commit messages

[Beckerle, Mike]

I seem to get two of everything.

I get one message from "GitBox" sent to commits@daffodil
I get one from "notificati...@github.com" to 
incubator-daffo...@noreply.github.com

I cannot guarantee that every message always shows up to both of these.

If I unsubscribe from the latter, will I miss some things, or is all the same 
traffic always sent to both.

Mike Beckerle | Principal Engineer

[cid:04277154-4ad9-443f-9337-264ca394c4fd]

mbecke...@owlcyberdefense.com

P +1-781-330-0412

Connect with us!

[cid:228ec6e0-9ffc-4298-a483-6e2540bd4d8a][cid:0d099090-c20d-420b-bd2f-f2b1f7e0674b]

[cid:5ed4975c-9c6e-4f98-b4e6-7a957ff7757a]



The information contained in this transmission is for the personal and 
confidential use of the individual or entity to which it is addressed. If the 
reader is not the intended recipient, you are hereby notified that any review, 
dissemination, or copying of this communication is strictly prohibited. If you 
have received this transmission in error, please notify the sender immediately