Buildbot success in on pelican_websites

[bu...@apache.org]

The Buildbot has detected a passing build on builder pelican_websites while building httpd.
Full details are available at:
    https://ci2.apache.org/#builders/3/builds/3524

Buildbot URL: https://ci2.apache.org/

Worker for this Build: bb_slave9_ubuntu

Build Reason: Triggered pelican auto-build via .asf.yaml by wave
Blamelist: asfinfra, dev@httpd.apache.org

Build succeeded!

Sincerely,
 -The Buildbot

Re: where do we want to send website bot notices?

[Greg Stein <gs...@gmail.com>]

I think any commit, including to the website, should go to commits@httpd
(which should be the proper name for cvs@ which is stoopid archaic).

Cheers,
-g


On Fri, Jun 25, 2021, 17:50 Roy T. Fielding <fi...@gbiv.com> wrote:

> I was about to update the site config so that it wouldn't send notices
> to dev, but I don't know whether they should instead go to cvs, docs, or
> a new list (like notices at httpd).  Any opinions?
>
> ....Roy
>

Re: where do we want to send website bot notices?

[Dave Fisher <wa...@apache.org>]

FYI - for the website the locations are controlled from

https://github.com/apache/httpd-site/blob/main/.asf.yaml

github:
  features:
    # Enable issue management
    issues: true

notifications:
  commits: cvs@httpd.apache.org
  issues: dev@httpd.apache.org
  pullrequests: dev@httpd.apache.org

pelican:
  notify: dev@httpd.apache.org
  autobuild: preview/*
  target: asf-site
  theme: theme/apache
  whoami: main

Github issues is optional and can be turned off.

notifications.commits are the GitHub commits.
notifications.pullrequests happen if anyone suggestions an update to the site.
pelican.notify are buildbot runs of the website.

HTH,
Dave

> On Jun 28, 2021, at 1:35 AM, Ruediger Pluem <rp...@apache.org> wrote:
> 
> 
> 
> On 6/28/21 10:12 AM, Joe Orton wrote:
>> On Fri, Jun 25, 2021 at 03:50:33PM -0700, Roy T. Fielding wrote:
>>> I was about to update the site config so that it wouldn't send notices
>>> to dev, but I don't know whether they should instead go to cvs, docs, or
>>> a new list (like notices at httpd).  Any opinions?
>> 
>> We already have notifications@ which is used for GitHub PR 
>> notifications, that makes sense to me.
>> 
> 
> I don't care if it is notifications@ or cvs@ / commits@. Both locations make some sense.
> 
> Regards
> 
> Rüdiger

Re: where do we want to send website bot notices?

[Ruediger Pluem <rp...@apache.org>]

On 6/28/21 10:12 AM, Joe Orton wrote:
> On Fri, Jun 25, 2021 at 03:50:33PM -0700, Roy T. Fielding wrote:
>> I was about to update the site config so that it wouldn't send notices
>> to dev, but I don't know whether they should instead go to cvs, docs, or
>> a new list (like notices at httpd).  Any opinions?
> 
> We already have notifications@ which is used for GitHub PR 
> notifications, that makes sense to me.
> 

I don't care if it is notifications@ or cvs@ / commits@. Both locations make some sense.

Regards

Rüdiger

Re: where do we want to send website bot notices?

[Joe Orton <jo...@redhat.com>]

On Fri, Jun 25, 2021 at 03:50:33PM -0700, Roy T. Fielding wrote:
> I was about to update the site config so that it wouldn't send notices
> to dev, but I don't know whether they should instead go to cvs, docs, or
> a new list (like notices at httpd).  Any opinions?

We already have notifications@ which is used for GitHub PR 
notifications, that makes sense to me.

Regards, Joe

where do we want to send website bot notices?

["Roy T. Fielding" <fi...@gbiv.com>]

I was about to update the site config so that it wouldn't send notices
to dev, but I don't know whether they should instead go to cvs, docs, or
a new list (like notices at httpd).  Any opinions?

....Roy