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
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
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
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
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
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
13 matches
Mail list logo
