alamb opened a new pull request, #20629:
URL: https://github.com/apache/datafusion/pull/20629

   ## Which issue does this PR close?
   
   
   
   ## Rationale for this change
   
   It was mentioned it is hard to find out about new events 
[link](https://www.linkedin.com/feed/update/urn:li:ugcPost:7433220719607545856?commentUrn=urn%3Ali%3Acomment%3A%28ugcPost%3A7433220719607545856%2C7433309539426504705%29&dashCommentUrn=urn%3Ali%3Afsd_comment%3A%287433309539426504705%2Curn%3Ali%3AugcPost%3A7433220719607545856%29)
   
   <img width="584" height="458" alt="Screenshot 2026-03-01 at 7 26 16 AM" 
src="https://github.com/user-attachments/assets/4807d2c1-8c4a-488b-a6a6-4fb9eafc67b1";
 />
   
   
   ## What changes are included in this PR?
   
   Add links to the various meetups that are scheduled in the next fe months to 
the webpage
   
   I made them with codex using this prompt and then checked all the links
   
   <details><summary>Details</summary>
   <p>
   
   
   
   ```text
   › I would like to update the contents of the page 
./docs/source/user-guide/concepts-readings-events.md
   
     This is published here 
https://datafusion.apache.org/user-guide/concepts-readings-events.html
   
     Specifically, let's first update the list of events with more recent ones. 
To do so, please look at the discussions here 
https://github.com/apache/datafusion/discussions
   
     Please use the `gh` command to fetch the contents of github discussions 
and issues when necessary
   
     For example, here is a recent event: 
https://github.com/apache/datafusion/discussions/19859 in San Francisco that 
should be on the events page
   
     There are also events scheduled in Stockholm, Denver, Seattle, in the next 
few months that should be on there
   
     There are also seveal in the past
   ```
   
   
   </p>
   </details> 
   
   ## Are these changes tested?
   
   <!--
   We typically require tests for all PRs in order to:
   1. Prevent the code from being accidentally broken by subsequent changes
   2. Serve as another way to document the expected behavior of the code
   
   If tests are not included in your PR, please explain why (for example, are 
they covered by existing tests)?
   -->
   
   ## Are there any user-facing changes?
   
   <!--
   If there are user-facing changes then we may require documentation to be 
updated before approving the PR.
   -->
   
   <!--
   If there are any breaking changes to public APIs, please add the `api 
change` label.
   -->
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


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

Reply via email to