Many congratulations Brian, welcome aboard! :)
Best Regards,
Swapnil M Mane
On Tue, Jul 6, 2021 at 11:01 PM Sharan Foga wrote:
> Hi Everyone
>
> I'd like to announce that the ComDev PMC has invited Brian Proffitt to
> become a PMC Member and am very glad to let you all know that he has
> accept
Hi Apache Airflow community,
Airflow Summit 2021 starts in 2 days and you can still register.
In the words of Jarek Potiuk, one or the organizers, here is what to expect:
We start with the community day - including discussing Airflow Security,
then we follow with the first-time-users day where
Does it really make sense to use the same list for development
discussions amongst the ComDev community, and discussions with the
general public?
At present this single list is acting as both developer and user list.
[Many projects would also have commits, issues and notifications lists]
It may n
On Tue, Jul 06, 2021 at 01:16:19PM -0400, Joe Brockmeier wrote:
>First, I feel like I have to respond given the Truman State University sig.
>It's rare I run into other Truman grads in the wild, though we wouldn't
>have crossed paths on campus... (1998 grad here...)
Wow, this is a first for me, to
ctubbsii commented on pull request #64:
URL: https://github.com/apache/comdev-site/pull/64#issuecomment-875026587
> issues have not been enabled so that setting is irrelevant.
As far as I can tell, the "issues" type is used for all
"[issue_comment](https://docs.github.com/en/develope
On Tue, Jul 6, 2021 at 1:10 PM Dave Fisher wrote:
[SNIP]
> Tell me why a split discussion is good for the community?
I feel like I didn't do a good enough job of responding to this point,
so to clarify further:
My answer is that it's *not*. However, that problem already exists
with any issue tra
Great discussion, everybody! Here's some thoughts in response to some
of the questions/concerns raised:
People should *not* have to subscribe to the other list in order to
participate in discussions. It should just be for automated notices.
The best practice is, like commits@, have it moderated an
rbowen merged pull request #29:
URL: https://github.com/apache/comdev-site/pull/29
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
rbowen commented on pull request #29:
URL: https://github.com/apache/comdev-site/pull/29#issuecomment-874967401
Thanks!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To
Hi Everyone
This is a quick reminder that the schedules for both ApacheCon Asia and
ApacheCon@Home have been published! And you know what that means? It means it's
time to take a look and plan which presentations you want to attend..and this
year there year there is a lot to choose from.
For A
On 7/6/21 1:31 PM, Sharan Foga wrote:
Hi Everyone
I'd like to announce that the ComDev PMC has invited Brian Proffitt to become a
PMC Member and am very glad to let you all know that he has accepted. :-)
For those that don't know Brian, he has been a key part of the organisation and
running
Hi Everyone
I'd like to announce that the ComDev PMC has invited Brian Proffitt to become a
PMC Member and am very glad to let you all know that he has accepted. :-)
For those that don't know Brian, he has been a key part of the organisation and
running of ApacheCon over the last couple of yea
First, I feel like I have to respond given the Truman State University sig.
It's rare I run into other Truman grads in the wild, though we wouldn't
have crossed paths on campus... (1998 grad here...)
If the PRs appear here on this list, it makes it slightly easier to have a
discussion on list abou
I have rather hard as a mentor in the Incubator now that all new projects use
GitHub. Much development discussion is driven away from dev@project mailing
lists and occurs in issues(if enabled) and PRs.
comdev-site: https://github.com/apache/comdev-site/blob/master/.asf.yaml
notifications:
com
dave2wave commented on pull request #64:
URL: https://github.com/apache/comdev-site/pull/64#issuecomment-874922146
issues have not been enabled so that setting is irrelevant.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub an
I don't think asking for a new mailing list for GitHub notifications is
unreasonable. In fact, I would go as far to say that having a GitHub
notifications mailing list makes more sense than having those
notifications being sent to the "dev" mailing list. Shouldn't the dev
mailing list be used for
bessbd commented on pull request #64:
URL: https://github.com/apache/comdev-site/pull/64#issuecomment-874882211
+1 (non-binding)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comm
rbowen merged pull request #65:
URL: https://github.com/apache/comdev-site/pull/65
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
rbowen opened a new pull request #65:
URL: https://github.com/apache/comdev-site/pull/65
Revert email list -> mailing list, as per discussion on several other PRs.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
rbowen merged pull request #54:
URL: https://github.com/apache/comdev-site/pull/54
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
rbowen commented on pull request #54:
URL: https://github.com/apache/comdev-site/pull/54#issuecomment-874840568
Thank you.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
Sorry, I have a slight correction on my response. I meant to write:
'"OPT-IN" makes so much more sense here.' Sorry for any confusion.
On Tue, Jul 6, 2021 at 10:45 AM Christopher wrote:
>
> To respond to your questions:
>
> On Tue, Jul 6, 2021 at 10:06 AM Rich Bowen wrote:
> >
> > May I be the c
Fair. Count me as -0. Thanks for your detailed answers.
On 7/6/21 10:45 AM, Christopher wrote:
To respond to your questions:
On Tue, Jul 6, 2021 at 10:06 AM Rich Bowen wrote:
May I be the contrary voice and ask why?
I put two points of justification in the PR, but to repeat here:
1. These
To respond to your questions:
On Tue, Jul 6, 2021 at 10:06 AM Rich Bowen wrote:
>
> May I be the contrary voice and ask why?
I put two points of justification in the PR, but to repeat here:
1. These automated notices are redundant if somebody is already watching
the relevant notices for the rep
swapnilmmane commented on pull request #41:
URL: https://github.com/apache/comdev-site/pull/41#issuecomment-874820387
Hi @rbowen, I will suggest waiting for #62 to be merged. I think, after that
this PR will be marked as merged automatically.
At least this similar thing has happened for
If I had a dollar for every time I've been on a list with this discussion
or a variant thereof... I wouldn't be rich, but I could probably buy myself
a really spiffy NVME drive or something.
FWIW I think the better approach is to filter rather than shunt the commits
to a different list. I don't fe
May I be the contrary voice and ask why? Why do we not want to know
what's being committed in our name? It's not like this list gets a lot
of traffic, and those very emails that you want to banish to another
list were what reminded me that we have PRs that have been languishing
for several mont
Hi ComDev,
I'm probably not the only one who has noticed the flurry of emails on
the main dev@community.apache.org due to GitHub activity on the
comdev-site repo.
To help deal with that, I created a pull request:
https://github.com/apache/comdev-site/pull/64
For more information, see
https://cwik
ctubbsii opened a new pull request #64:
URL: https://github.com/apache/comdev-site/pull/64
This change redirects GitBox issue/pull request activity to a separate
mailing list to avoid spamming the dev@ list. The new notifications@
list must be created by the ComDev PMC before accepting
On 06/07/2021 15.11, Rich Bowen wrote:
I have been looking through some PRs and came across
https://github.com/apache/comdev-site/pull/42 and I'm not sure how to
proceed here.
We do not have a mentoring program. But the text in some of the pages in
the "Mentoring" nav menu *seem* to be referr
I have been looking through some PRs and came across
https://github.com/apache/comdev-site/pull/42 and I'm not sure how to
proceed here.
We do not have a mentoring program. But the text in some of the pages in
the "Mentoring" nav menu *seem* to be referring to GSOC, while others
are not, and
rbowen commented on a change in pull request #46:
URL: https://github.com/apache/comdev-site/pull/46#discussion_r664533976
##
File path: source/calendars/__index.md
##
@@ -7,39 +7,37 @@ This calendar lists major events relating to The Apache
Software Foundation
and our many A
rbowen commented on pull request #44:
URL: https://github.com/apache/comdev-site/pull/44#issuecomment-874737843
We do not have a mentoring program. It would be nice to have one, but I
don't think we're doing anybody any favors by documenting a non-existent
program. We really should either
rbowen commented on pull request #41:
URL: https://github.com/apache/comdev-site/pull/41#issuecomment-874733892
@swapnilmmane Does that mean we need to close this PR?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use th
rbowen commented on pull request #49:
URL: https://github.com/apache/comdev-site/pull/49#issuecomment-874733103
I appear to have merged something in the wrong order, and this PR is now in
conflict.
--
This is an automated message from the Apache Git Service.
To respond to the message, pl
rbowen commented on pull request #49:
URL: https://github.com/apache/comdev-site/pull/49#issuecomment-874732783
Yeah, I'm pretty sure lanyrd.com went away years ago.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
rbowen commented on pull request #52:
URL: https://github.com/apache/comdev-site/pull/52#issuecomment-874730207
Thanks. I'm happy to merge this PR, either with reverting "email list" back
to "mailing list", or I can just make that change after merging, as you prefer.
Let me know, and I'll
rbowen commented on a change in pull request #52:
URL: https://github.com/apache/comdev-site/pull/52#discussion_r664522957
##
File path: source/contributors/etiquette.md
##
@@ -54,45 +51,45 @@ Review and try to reformulate to be as clear as possible.
opinion, we must..." or th
rbowen commented on a change in pull request #55:
URL: https://github.com/apache/comdev-site/pull/55#discussion_r664520979
##
File path: source/gettingStarted/101.md
##
@@ -13,19 +13,19 @@ The key to working on projects at Apache (and on any open
source project, for th
is to
rbowen merged pull request #27:
URL: https://github.com/apache/comdev-site/pull/27
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
rbowen commented on pull request #27:
URL: https://github.com/apache/comdev-site/pull/27#issuecomment-874714784
Thanks. These changed do indeed add clarity.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
rbowen commented on pull request #63:
URL: https://github.com/apache/comdev-site/pull/63#issuecomment-874713330
While I'm glad to merge this, I'm not sure this resource even works any
more. My guess is that it's using a deprecated version of a Google Maps API,
and none of the maps are load
rbowen merged pull request #63:
URL: https://github.com/apache/comdev-site/pull/63
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: dev-unsubscr...
cottage14 commented on pull request #49:
URL: https://github.com/apache/comdev-site/pull/49#issuecomment-874239301
incorporating suggestions
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the s
clr-apache commented on pull request #62:
URL: https://github.com/apache/comdev-site/pull/62#issuecomment-874287280
Looks good. Thanks.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specif
swapnilmmane commented on pull request #25:
URL: https://github.com/apache/comdev-site/pull/25#issuecomment-874112299
Thank you @bdelacretaz!
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the
swapnilmmane commented on pull request #41:
URL: https://github.com/apache/comdev-site/pull/41#issuecomment-874116439
Thank you @cottage14 for your work.
As the merge branch, `cottage14:patch-26` for this PR is from a different
repository and edits from maintainers were not allowed, I wa
swapnilmmane commented on a change in pull request #41:
URL: https://github.com/apache/comdev-site/pull/41#discussion_r663943082
##
File path: source/newcommitter.md
##
@@ -295,11 +295,11 @@ This is the followup email after the new committer has
accepted the invitation
48 matches
Mail list logo
