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

[Greg Stein]

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  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
>

Buildbot success in on pelican_websites

[buildbot]

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/3552

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: migration of the HTTPD project website

[Dave Fisher]

FYI -

The regeneration of vulnerability reports is now a manual exercise. On review 
with Infra it was decided that running arbitrary shell scripts during a pelican 
build is a security risk.

All the best,
Dave

> On Jun 25, 2021, at 10:12 AM, Dave Fisher  wrote:
> 
> The Migration from CMS to ASF-Pelican is staged!
> 
> https://httpd.staged.apache.org/ is ready.
> 
> https://github.com/apache/httpd-site/
> 
> See the README on GitHub for details.
> 
> All The Best,
> Dave
> 
>> On Jun 22, 2021, at 11:00 AM, Dave Fisher  wrote:
>> 
>> 
>> 
>>> On Jun 21, 2021, at 6:26 AM, Eric Covener  wrote:
>>> 
>>> On Sun, Jun 20, 2021 at 3:25 PM Andrew Wetmore  wrote:
 
 Hi, Eric:
 
 Yes, committers can use either GitHub or Gitbox.
 
 I am not sure what the "can you give a hint about the migration aspect" 
 means. Maybe I was not clear. We have to move all projects off the Apache 
 CMS and to some other technology, such as Pelican. Infra can help with 
 that move to a Git repository. Sometime this summer the Apache CMS will 
 stop functioning, which would mean you would have a hard time updating 
 your website.
>>> 
>>> I was referring to  "...migration process available that could speed
>>> things along." not the overall migration off the CMS.
>>> Daniel referred to
>>> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features
>>> but I didn't find any reference to "migration".
>>> 
>>> https://github.com/apache/httpd-site was created but it's empty.  I
>>> was assuming we'd have some starting point based on the CMS-based site
>>> content and whatever additional template/scaffolding is needed that
>>> we'd be able to see w/o replacing our currently published site.
>>> I don't want anyone to start from scratch if there's a better way to
>>> get started.
>> 
>> I have the go ahead to do the migration for you. The goal is to create a 
>> staged site that will be nearly identical to your current site.
>> 
>> Expect more information this week.
>> 
>> All The Best,
>> Dave
>> 
>> 
>