Re: Status of ftp server?

[Bron Gondwana]

On Tue, Feb 25, 2020, at 10:16, Quanah Gibson-Mount wrote:
> Hi,
> 
> The documentation in numerous places states that release tarballs can be 
> obtained from "ftp.cyrusimap.org". However, this server appears to be 
> offline.
> 
> Example reference: 
> 
> 
> Do all the various documentation locations referencing FTP need to be 
> updated, or is it intended to bring the FTP server back online?

Thanks for reminding us about the FTP server situation, we'll figure something 
out shortly one way or the other.

I suspect we'll actually move to entirely HTTP, since FTP is a pretty awful 
protocol to firewall and manage compared to HTTP which can be easily hosted 
directly out of Github, which is where our code and issue tracker is stored.

Cheers,

Bron.

--
 Bron Gondwana, CEO, Fastmail Pty Ltd
 br...@fastmailteam.com

Re: Status of ftp server?

[Dave McMurtrie]

On Wed, 26 Feb 2020, ellie timoney wrote:

The FTP is known to be down, and we don't expect it to come back.  This 
is all still hosted by CMU at the moment, even though they've pulled out 
of the project.


The infrastructure for cyrusimap.org is still running at CMU.  I was 
unaware the ftp server was down.


Our real plan has been to move the cyrusimap.org domain away from the 
CMU infrastructure and onto github.io (which doesn't provide FTP 
anyway), and then update all the documentation accordingly at once. 
(The temporary URL for the github.io site is 
https://cyrusimap.github.io, but once we have the real domain, we'll use 
that for it instead.)


Getting action out of CMU is like pulling teeth though, so maybe we 
should just remove the dead FTP links from documentation in the 
meantime.


Really?  What was asked of us that we didn't respond to?

Dave

Re: Status of ftp server?

[ellie timoney]

The FTP is known to be down, and we don't expect it to come back.  This is all 
still hosted by CMU at the moment, even though they've pulled out of the 
project.

Our real plan has been to move the cyrusimap.org domain away from the CMU 
infrastructure and onto github.io (which doesn't provide FTP anyway), and then 
update all the documentation accordingly at once.  (The temporary URL for the 
github.io site is https://cyrusimap.github.io, but once we have the real 
domain, we'll use that for it instead.)

Getting action out of CMU is like pulling teeth though, so maybe we should just 
remove the dead FTP links from documentation in the meantime.

I've been referring people to the github-hosted url's (i.e. under 
https://github.com/cyrusimap/cyrus-imapd/releases) in the release announcement 
emails, because I don't expect the "https://cyrusimap.org/releases; links to 
remain valid either, once the domain moves to githhub.io.

Cheers,

ellie

On Tue, Feb 25, 2020, at 10:16 AM, Quanah Gibson-Mount wrote:
> Hi,
> 
> The documentation in numerous places states that release tarballs can be 
> obtained from "ftp.cyrusimap.org".  However, this server appears to be 
> offline.
> 
> Example reference: 
> 
> 
> Do all the various documentation locations referencing FTP need to be 
> updated, or is it intended to bring the FTP server back online?
> 
> The webserver frontend to the data appears to still work:
> 
> 
> 
> Thanks,
> Quanah
> 
> --
> 
> Quanah Gibson-Mount
> Product Architect
> Symas Corporation
> Packaged, certified, and supported LDAP solutions powered by OpenLDAP:
> 
>

Status of ftp server?

[Quanah Gibson-Mount]

Hi,

The documentation in numerous places states that release tarballs can be 
obtained from "ftp.cyrusimap.org".  However, this server appears to be 
offline.


Example reference: 



Do all the various documentation locations referencing FTP need to be 
updated, or is it intended to bring the FTP server back online?


The webserver frontend to the data appears to still work:



Thanks,
Quanah

--

Quanah Gibson-Mount
Product Architect
Symas Corporation
Packaged, certified, and supported LDAP solutions powered by OpenLDAP: