account to send mails
- A domain like discuss.opendal.apache.org
On Tue, Dec 19, 2023, at 18:55, Xuanwo wrote:
Does it need any configuration from the mailing list part,
i.e.,
involve INFRA setup?
Discourse will provide us an incoming email address. All email
sent to
this address will become
On Wed, 2023-12-20 at 14:26 +0800, Xuanwo wrote:
> **Other solutions?**
>
> We could also consider hosting a modern frontend for our mailing
> list, similar to Hyperkitty. For instance, take a look at:
> https://ml.ruby-lang.org/mailman3/hyperkitty/list/ruby-t...@ml.ruby-lang.or
On 12/20/23 07:26, Xuanwo wrote:
I did some research on discourse and found that it doesn't work as it described.
Alought it can receive and create new topics from mailing list, but it can't
send mails to mailing list when posts or replies created at discourse. This
will make it
I did some research on discourse and found that it doesn't work as it described.
Alought it can receive and create new topics from mailing list, but it can't
send mails to mailing list when posts or replies created at discourse. This
will make it a possible read-only archives of o
need to add this
>>>>> address into the dev@o.a.o's subcriber list.
>>>> This is talking about Discourse SaaS which cost about $100 ($50 if
>>>> we have non-profit discount).
>>>> If we can request a vm from ASF Infra, we will need:
>>
VM with 4C8G
> > > - Postgresql
> > > - A SMTP account to send mails
> > > - A domain like discuss.opendal.apache.org
> > >
> > > On Tue, Dec 19, 2023, at 18:55, Xuanwo wrote:
> > > > > Does it need any configuration from the mailing list part,
; - A domain like discuss.opendal.apache.org
> >
> > On Tue, Dec 19, 2023, at 18:55, Xuanwo wrote:
> > > > Does it need any configuration from the mailing list part,
> > > > i.e.,
> > > > involve INFRA setup?
> > >
> > > Discours
After a closer look, I don't think Discourse brings too much value but
a new platform to track.
Although as long as it's a third-party integration that doesn't affect
the view from a pure mailing list user, I don't object it. But it
doesn't seem valuable to
t; - A domain like discuss.opendal.apache.org
>
> On Tue, Dec 19, 2023, at 18:55, Xuanwo wrote:
> >> Does it need any configuration from the mailing list part, i.e.,
> >> involve INFRA setup?
> >
> > Discourse will provide us an incoming email address. All email se
rbowen merged PR #140:
URL: https://github.com/apache/comdev-site/pull/140
--
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...@community.apa
rbowen opened a new pull request, #140:
URL: https://github.com/apache/comdev-site/pull/140
(no comment)
--
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-m
All:
In an effort to better coordinate communications, the pr...@apache.org
mailing list will soon be shifting to incoming press/media inquiries
and subsequent conversations only. Conversations around marketing &
publicity, website updates, GitHub notifications, and anything else
under M
TL;DR: We’re updating how auto-generated email from Github will be
threaded on your mailing lists. If you want to keep the old defaults,
details are below.
We’re pleased to let you know that we’re tweaking the way that auto-
generated email from Github will appear on your mailing lists. This
will
[
https://issues.apache.org/jira/browse/COMDEV-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ryan Skraba closed COMDEV-482.
--
> [Reporter] mailing list statistics are incorr
now.
> [Reporter] mailing list statistics are incorrect
>
>
> Key: COMDEV-482
> URL: https://issues.apache.org/jira/browse/COMDEV-482
> Project: Community Development
>
Ryan Skraba created COMDEV-482:
--
Summary: [Reporter] mailing list statistics are incorrect
Key: COMDEV-482
URL: https://issues.apache.org/jira/browse/COMDEV-482
Project: Community Development
[
https://issues.apache.org/jira/browse/COMDEV-477?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giovanni Bechis resolved COMDEV-477.
Resolution: Fixed
> Apache SpamAssassin mailing l
kege) gave me all the info I needed.
Thanks
> Apache SpamAssassin mailing list
> -
>
> Key: COMDEV-477
> URL: https://issues.apache.org/jira/browse/COMDEV-477
> Project: Community Development
>
may also.
> Apache SpamAssassin mailing list
> -
>
> Key: COMDEV-477
> URL: https://issues.apache.org/jira/browse/COMDEV-477
> Project: Community Development
> Issue Type: Question
>
Giovanni Bechis created COMDEV-477:
--
Summary: Apache SpamAssassin mailing list
Key: COMDEV-477
URL: https://issues.apache.org/jira/browse/COMDEV-477
Project: Community Development
Issue
Hi root4dm; you can get a subscribe link and see the archives here
https://lists.apache.org/list.html?security-disc...@community.apache.org
Note we've only mentioned the list in the ApacheCon presentation and we're
waiting for that presentation to be archived public before mentioning this
list to
Vào 17:31, Th 2, 27 thg 9, 2021 r00t4dm Hi,
>
> I want to know, How to subscribe to this mail list.
>
> r00t4dm
>
> Cloud-Penetrating Arrow Lab of Meituan Corp Information Security Department
>
>
> Bertrand Delacretaz 于2021年9月27日周一 下午4:27写道：
>
> > Hi,
> >
> > On Mon, Sep 20, 2021 at 8:27 AM Mark
Hi,
On Mon, Sep 20, 2021 at 8:27 AM Mark J. Cox wrote:
> ...I still like this living in the community project though, because the
> likely outcome
> of the discussion are collation of resources and practices and the right
> place for them is in comdev...
Same here, and a Special Interest Group
Thanks, would someone in community PMC be able to submit the request to
create the list? https://selfserve.apache.org/mail.html
(subscribers to post, otherwise moderated),
Regards, Mark
On Mon, Sep 20, 2021 at 6:24 PM Craig Russell wrote:
> +1 for security-disc...@community.apache.org
>
> Crai
+1 for security-disc...@community.apache.org
Craig
> On Sep 19, 2021, at 11:27 PM, Mark J. Cox wrote:
>
> On 2021/09/19 21:44:34, Dave Fisher wrote:
>> This is a good idea. Assuming that this is a public list then either pick
>> another name, or do not use self serve to request it, instead u
I like the idea of security-discuss. Helps highlight that it's not the
list to report vulnerabilities to unlike seclists or security@
addresses.
On Mon, Sep 20, 2021 at 1:27 AM Mark J. Cox wrote:
>
> On 2021/09/19 21:44:34, Dave Fisher wrote:
> > This is a good idea. Assuming that this is a publ
On 2021/09/19 21:44:34, Dave Fisher wrote:
> This is a good idea. Assuming that this is a public list then either pick
> another name, or do not use self serve to request it, instead use an INFRA
> JIRA ticket.
>
> Security@ lists requested through self serve become private mailing lists
> w
ilitate an open
> and collaborative process, the group would like to request the
> configuration of a new mailing list, secur...@community.apache.org.
>
> The new list will enable interested participants and members of the ASF
> share best practices and build a collaborative community ar
pen
> and collaborative process, the group would like to request the
> configuration of a new mailing list, secur...@community.apache.org.
>
> The new list will enable interested participants and members of the ASF
> share best practices and build a collaborative community around infosec
of a new mailing list, secur...@community.apache.org.
The new list will enable interested participants and members of the ASF
share best practices and build a collaborative community around infosec
that ultimately should create a more security development environment for
Apache projects.
If at
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
Hi Maxim, I’ve just sent the formal request. Thanks.
From: Maxim Solodovnik
Date: Thursday, 1 April 2021, 15:22
To: mentors
Cc: dev , dev ,
Subject: Re: Mentors@ mailing list issue
I see the mail from Boris Stoyanov
This user subscription was not confirmed (due to I saw no mentor
request
obably visible to comdev PMC only
>
> On Thu, 1 Apr 2021 at 19:11, Rohit Yadav wrote:
> >
> > Dear dev-community, mentors, cc Maxim (GSoC admin), CloudStack dev/pmc list,
> >
> > Can anyone with access/privileges, check if mails are being sent to
> > the ment
heck if mails are being sent to
> the mentors@ mailing list [1] for GSoC. Per this, the list does not
> exist: https://lists.apache.org/list.html?ment...@community.apache.org
>
> [1] https://community.apache.org/gsoc.html
>
>
Dear dev-community, mentors, cc Maxim (GSoC admin), CloudStack dev/pmc list,
Can anyone with access/privileges, check if mails are being sent to
the mentors@ mailing list [1] for GSoC. Per this, the list does not
exist: https://lists.apache.org/list.html?ment...@community.apache.org
[1] https
Hello Eli,
I cannot speak for Apache or the Apache SpamAssassin project. The concept
of partnering with us is not a common or simple endeavor. That is a dead
end in my opinion.
However, I am a project management committee {pmc} member and have spent
nearly 25 years battling spammers. I think I
Dear Apache Development Team,
My name is Eli Ecanow and I am carrying out the project under the
supervision of the FBI LA citizens academy. I am an undergraduate student
studying computer science at the University of Michigan and am working
alongside 4 undergraduate students studying Computer Scie
Chris yes pliewse include indo on mew mailing liat
On Fri, Jul 5, 2019, 9:22 AM Christofer Dutz
wrote:
> Hi all,
>
> in order to improve the communication and exchange between Apache IoT
> projects, we have decided to create a mailing list for IoT related topics
> and projec
Hi all,
in order to improve the communication and exchange between Apache IoT projects,
we have decided to create a mailing list for IoT related topics and projects.
We have noticed that several projects have been addressing the same tasks
multiple times, just because they didn’t know about
On 3/2/19 7:33 AM, sebb wrote:
> I wonder if there should be a separate mailing list for discussion of
> the code for which ComDev is responsible.
>
> For example, Projects, Reporter, HelpWanted
>
> This would normally be the dev@ list, but that has long since been
>
On Sat, Mar 2, 2019 at 1:34 PM sebb wrote:
> ...Maybe code@ or tools@ or something else?...
Considering that few of the comdev folks are currently active in that
area, isn't there a risk to increase that fragmentation?
Another option would be to move those bits of code to GitHub if they
aren't t
Apps Account,awww.asus.application
Sent from my ASUS
Original Message
From:sebb
Sent:Sat, 02 Mar 2019 22:12:54 +0800
To:dev@community.apache.org
Subject:Recent spam (was: New mailing list for discussion of ComDev code
(projects, reporter etc))
>On Sat, 2 Mar 2019 at 13
On Sat, 2 Mar 2019 at 13:23, Shane Curcuru wrote:
>
> Side question: why has moderation let so much spam through to this list
> recently?
I think all the spam is from subscribers.
We could force all posts to be moderated, but that might be too much work.
sebb wrote on 3/2/19 7:33 AM:
> I wonder if there should be a separate mailing list for discussion of
> the code for which ComDev is responsible.
>
> For example, Projects, Reporter, HelpWanted
>
> This would normally be the dev@ list, but that has long since been
>
I wonder if there should be a separate mailing list for discussion of
the code for which ComDev is responsible.
For example, Projects, Reporter, HelpWanted
This would normally be the dev@ list, but that has long since been
used for general ASF community discussion, so it's too late to c
list with some mark in emails. Then
> some filtered view can be prepared for emails related to upstream.
>
> I hope it helps.
>
> Sincerely,
> Dmitriy Pavlov
>
>
> ср, 26 сент. 2018 г. в 1:05, Alexandre Rafalovitch :
>
> > In my mind, there are three differentiati
e it helps.
Sincerely,
Dmitriy Pavlov
ср, 26 сент. 2018 г. в 1:05, Alexandre Rafalovitch :
> In my mind, there are three differentiation:
> 1) The Solr Users mailing list traffic is quite large and diverse. So,
> it can be both overwhelming (for everybody) and hard to notice
> mess
In my mind, there are three differentiation:
1) The Solr Users mailing list traffic is quite large and diverse. So,
it can be both overwhelming (for everybody) and hard to notice
messages that are possibly of much higher impact than others. An
upstream framework that is suddenly broken or wants to
mailing lists, Jiras, etc, but they are all
> rather high volume and are among peers.
>
> Would it make sense to have a mailing list where committers of
> upstream projects could ask questions related to their implementation
> of API, interface, feature dependency, etc? The list would n
would be Apache Camel, NiFi, ManifoldCF, Nutch, etc.
And Solr would be upstream to Calcite, OpenNLP, Tika, ZooKeeper, etc.
We have Dev and User mailing lists, Jiras, etc, but they are all
rather high volume and are among peers.
Would it make sense to have a mailing list where committers of
upstream
Hi Debanjan, the typical way to get involved is to start working with
specific projects; you could look at open bugs and subscribe to the
user and dev mailing lists for Kafka, HDFS, etc., and offer your help
there.
Thanks and good luck!
On Sun, Jul 15, 2018 at 11:23 PM, Debanjan Dhar
wrote:
Hello,
I am interested in joining the apache community ( Apache Software Foundation )
as a developer.
Myself, Debanjan Dhar, is a 2 year working professional in IT industry and have
worked on multiple Apache Hadoop Softwares like kafka, HDFS, YARN etc.
Please let me know if if any information
[
https://issues.apache.org/jira/browse/COMDEV-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb resolved COMDEV-202.
-
Resolution: Won't Fix
> Ability to tag tasks with mailing list threads discussing / working on the
>
[
https://issues.apache.org/jira/browse/COMDEV-202?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sebb reopened COMDEV-202:
-
> Ability to tag tasks with mailing list threads discussing / working on the
> help wante
Ability to tag tasks with mailing list threads discussing / working on the
> help wanted task
> ---
>
> Key: COMDEV-202
> URL: https://issues.apache.org
How can i join mailing list of APACHE for GOOGLE SUMMER OF CODE
;
> Thanks!
>
> --Rich
>
>
> Forwarded Message ----
> Subject: New Feathercast mailing list
> Date: Wed, 25 Jan 2017 15:46:18 -0500
> From: Rich Bowen
> To: featherc...@apache.org
>
> Hi,
>
> I'm BCC'ing you because at some point you have expressed s
To anyone who has at any time expressed interest in helping out with
Feathercast, please see below. (Some of you have already received this,
but sending it to comdev just in case I missed someone!)
Thanks!
--Rich
Forwarded Message
Subject: New Feathercast mailing list
Date
have some asks, hopefully in
> order from easy to hard:
>
> 1) I would like to display the subscriber count in the mailing list
> panels. It looks like there is a file reporter.a.o uses called
> mailinglists.json that I can’t get at. Can I get the subscriber counts
> without auth
ike
people.a.o and dist.a.o and avoid authentication at reporter.a.o, so I did
that, but I’m blocked on a few things so I have some asks, hopefully in
order from easy to hard:
1) I would like to display the subscriber count in the mailing list
panels. It looks like there is a file reporter.a.o uses
n in mind.
> >
> > Which I think means that every PMC needs to replicate the same
> information
> > about how to subscribe to a mailing list...
>
> Mailing list pages like
> http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/
> include those instructions, do you t
out how to subscribe to a mailing list...
Mailing list pages like
http://mail-archives.apache.org/mod_mbox/jackrabbit-dev/
include those instructions, do you think we need more than that?
-Bertrand
Hi,
The page https://www.apache.org/foundation/mailinglists.html is written
with "foundation level" subscription in mind.
Which I think means that every PMC needs to replicate the same information
about how to subscribe to a mailing list.
Would it make sense to expand the "Projec
Would anyone be willing to share a screenshot or inventory of these
TLP project statistics?
With the open-source in-memory data tools available, I suspect a
real-time system for reporting project statistics is viable.
I'll volunteer to go through existing and desired mailing list stat
On 10 May 2015 at 16:50, Karl Heinz Marbaise wrote:
> Hi,
>
> I can see on that page the statistics for the mailing lists of the Maven
> project.
>
> https://reporter.apache.org/
>
> The question is. Can this be made visible for the community? Or do we have
> already such a thing which is availab
Hi,
I can see on that page the statistics for the mailing lists of the Maven
project.
https://reporter.apache.org/
The question is. Can this be made visible for the community? Or do we
have already such a thing which is available?
Kind regards
Karl Heinz Marbaise
Apache Maven PMC
In general, you can look at the general mailing list information at
http://www.apache.org/foundation/mailinglists.html
But each project also usually have details about what lists are available
for the project, and how to subscribe/unsubscribe.
See some examples below :
http://wink.apache.org
hello,
I want to subscribe apache's mailing list for educational purposes and
ultimately, taking participation in open source.
thanks
o create autoresponder for PRC mailing list
Joe, from my perspective I think a week is perfectly ok and appreciated.
I was concerned when I saw Tony's response because it
sounded more "if" than "when" it would get done. That might not have been
the intention, but it is how it re
Joe Schaefer wrote:
Yeah Tony's remarks were a botched interpretation of an irc conversation.
I wasn't too thrilled with what he wrote either. If a JIRA ticket will
help ease your mind while we figure out what to do, go for it. Otherwise
it's not necessary.
I would say I'm very good at naggin
- Original Message
> From: Serge Knystautas
> Cc: ASF Infrastructure ; fundrais...@apache.org;
> ASF Trademarks & Brand Management ; ASF DevCom
> ; ASF Marketing & Publicity
> Sent: Mon, March 22, 2010 6:54:19 PM
> Subject: Re: Request to create autoresp
Joe Schaefer wrote:
This is news to me, as discussion of an autoresponder has
been going on for at least 3 months. Oh well.
So another week or so isn't going to make much difference.
I'm not sure if I'm
understanding this correctly: there's nothing we can do?
Is that the situation?
The si
t to create autoresponder for PRC mailing list
>
> Thanks, Tony.
This is news to me, as discussion of an autoresponder has
> been going on for at least 3 months. Oh well.
So another week or so isn't going to make much difference.
> I'm not sure if I'm
> understandi
:
> From: Tony Stevenson
> Subject: Re: Request to create autoresponder for PRC mailing list
> To: s...@apache.org
> Cc: "ASF Infrastructure" , fundrais...@apache.org,
> "ASF Trademarks & Brand Management" , "ASF DevCom"
> , "ASF Marketing
On 15/03/2010 04:19, Sally Khudairi wrote:
Hello Infra team --
As you know, the PRC has been disbanded and we're working to formalize our new
operations.
One thing we'd like to implement this week is to create an autoresponder for
emails sent to the PRC list. The message we'd like folks to re
Hello Infra team --
As you know, the PRC has been disbanded and we're working to formalize our new
operations.
One thing we'd like to implement this week is to create an autoresponder for
emails sent to the PRC list. The message we'd like folks to receive when
sending messages to p...@apache.o
77 matches
Mail list logo
