[ 
https://issues.apache.org/jira/browse/HDDS-5001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18101384#comment-18101384
 ] 

Prabhat Singh Yadav commented on HDDS-5001:
-------------------------------------------

Picking this up, but the original scope no longer applies to the current site, 
so flagging before doing any work:

ApacheCon 2021 is long past, so adding that specific event banner/image would 
be incorrect today.
The website was rebuilt on Docusaurus (the "Website v2" work under HDDS-9539). 
In the new site, the footer copyright year is already rendered dynamically via 
new Date().getFullYear() in docusaurus.config.js, so the "update the year to 
2021" part is obsolete — the year now updates automatically.

Two options:

(a) Close as obsolete — both original asks (2021 ApacheCon banner + hardcoded 
year) no longer apply.
(b) Re-scope to: "Enable a reusable event announcementBar on the site for the 
current/upcoming community event." The new site already has a commented-out 
announcementBar stub in docusaurus.config.js; enabling it is a small, 
self-contained change and gives us a reusable mechanism for future events.

I'm happy to do (b) if there's a current event worth promoting — otherwise I'd 
suggest (a). Any preference?

> Add ApacheCon Event Banner to website
> -------------------------------------
>
>                 Key: HDDS-5001
>                 URL: https://issues.apache.org/jira/browse/HDDS-5001
>             Project: Apache Ozone
>          Issue Type: Sub-task
>          Components: website
>            Reporter: Tsz-wo Sze
>            Assignee: Prabhat Singh Yadav
>            Priority: Major
>
> We should add an ApacheCon Event Banner to our website.
> - https://www.apachecon.com/event-images/
> Also, we should update the year to 2021.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to