The SSL certificate on https://conference.scipy.org/ appears to be expired.

Our hosting has been closed by Rackspace. There was no notification. I'll redeploy the site asap.

The sidebar on the site needs to be updated to include a link to "2015". That has to happen in the script (wherever the website is served) called proc_versions(). It is probably somewhere in a file like ./publisher/_static/proc_links.js ... which doesn't seem to be in this repo. Is it elsewhere in the server? (The state of the proper file in the proceedings repo seems to be irrelevant: https://github.com/scipy-conference/scipy_proceedings/blob/master/publisher/_static/proc_links.js)

Thoughts on this @aterrel @dpinte ?

PRs #56 and #57 should be reverted once we have a proper solution for the broken proceedings links (#55) introduced by moving the site for Enthought's S3 bucket to Github pages.

The configuration changes and HTML redirects introduced in these two PRs are temporary until we have a permanent solution.

The bug is that make rsync fails without properly resolving the hostname. The cause appears to be that the person who wrote the makefile was relying on a mapping between conference and the server name in their ssh configfile.

The conference dates are shown, but there's no link to the website.

When you request to receive an email with your credentials, the message is incomplete because it is missing the email address to write to if you don't get an email within a few minutes...

It belongs in the list here https://conference.scipy.org/past.html

Current advice for deploying:

Email [email protected] to get the content deployed.

Any reason not to deploy via gh-actions, Netlify, or similar?

The server we use to host conference.scipy.org keeps a copy of proc_link.js in the root of the proceedings directory. We currently have an issue where this file has not been updated to include the 2017 proceedings (2012 is also missing, for unknown reasons).

Until this part of the publishing process can be automated, we should include an explicit step in the publishing documentation to copy over the most recent js file from the proceedings.

The certificate expired October 28, and this is breaking DOI to conference proceedings. The proceedings appear to be served from elsewhere, but hopefully someone who can fix follows this repo. https://conference.scipy.org/proceedings/scipy2020/

If this repo is no longer active, perhaps the wiki can be updated.
https://github.com/scipy/scipy/wiki/Web-service-infrastructure#conferencescipyorg

I don't know if this the right place to report this, but some of the past years are not working on the website.

e.g. https://conference.scipy.org/scipy2013/ gives a 404 not found page.

I noticed because this Matplotlib page links to one of the talks. Actually clicking on the link there (https://conference.scipy.org/scipy2013/tutorial_detail.php?id=103) downloads a PHP file.

One of the projects I work on uses sphinx's linkcheck to validate all the URLs in our docs. We noticed that the URLs that link to the conference proceedings have started to fail the linkcheck

...
2024-03-10T06:07:22.7942075Z (        outreach: line   60) broken    http://conference.scipy.org/proceedings/scipy2019/slides.html - 404 Client Error: Not Found for url: https://conference.scipy.org/proceedings/scipy2019/slides.html
2024-03-10T06:07:22.9437406Z (       citations: line   25) ok        https://arxiv.org/abs/2103.12504
2024-03-10T06:07:22.9849483Z (        outreach: line   39) broken    http://conference.scipy.org/proceedings/scipy2020/slides.html - 404 Client Error: Not Found for url: https://conference.scipy.org/proceedings/scipy2020/slides.html
...

and currently all the links on https://conference.scipy.org/proceedings/ (e.g. https://conference.scipy.org/proceedings/scipy2023 fail with a 404).