I saw that message on INFRA - at the top it says:

"TL;DR: if your project web site is kept in subversion, disregard this email 
please. If your project web site is using git, and you have not deployed it via 
.asf.yaml, you MUST switch before July 1st or risk your web site goes stale."

Curator's website is in svn so I think we're safe, right?

-Jordan

> On Jun 10, 2021, at 2:23 PM, Enrico Olivelli <[email protected]> wrote:
> 
> What can we do now ?
> 
> Are we risking seeing curator.apache.org to be offline ?
> 
> Enrico
> 
> Il giorno lun 31 mag 2021 alle ore 18:30 tison <[email protected]>
> ha scritto:
>> 
>> Attach the NOTICE mail here[1]. It seems just like something as a marker.
>> 
>> However, from the instructions we use svn to publish the website and won't
>> be affected.
>> 
>> Best,
>> tison.
>> 
>> [1]
>> https://lists.apache.org/thread.html/r8d023c0f5afefca7f6ce4e26d02404762bd6234fbe328011e1564249%40%3Cusers.infra.apache.org%3E
>> 
>> 
>> tison <[email protected]> 于2021年6月1日周二 上午12:21写道:
>> 
>>> IIRC our website publish guide stays here[1] and I did ever follow it.
>>> 
>>> .asf.yaml file helps on configure GitHub & JIRA & Mailing List
>>> Notification settings, but I don't see how to setup a publish workflow from
>>> the doc.
>>> 
>>> Here is an example from Flink[2] but still I don't understand how it works.
>>> 
>>> Best,
>>> tison.
>>> 
>>> [1]
>>> https://cwiki.apache.org/confluence/display/CURATOR/For+Curator+Committers#ForCuratorCommitters-HowtoPublishtheCuratorWebsite
>>> [2] https://github.com/apache/flink-web/blob/asf-site/.asf.yaml
>>> 
>>> 
>>> 
>>> Enrico Olivelli <[email protected]> 于2021年6月1日周二 上午12:11写道:
>>> 
>>>> Hello everyone,
>>>> I received a NOTICE from infra that tells that every website must use
>>>> .asf.yaml configuration file for publishing the website
>>>> 
>>>> 
>>>> https://cwiki.apache.org/confluence/display/INFRA/Git+-+.asf.yaml+features#Git.asf.yamlfeatures-WebSiteDeploymentServiceforGitRepositories
>>>> 
>>>> I do not find anything about this stuff on Curator git repo
>>>> 
>>>> thoughts ?
>>>> 
>>>> Enrico
>>>> 
>>> 

Reply via email to