| 75 | | >>>>[wiki:seanegan]: Where does the user actually click to download the package? Is it possible to download the package directly from the homepage, or do you have to go to this page first? From this page, where is the link to download? For UNIX distros, it would be nice if the home page contained two links, one for the binaries and one for the source... but in a way not to confuse the 15 year old Ubuntu livecd users. ;) |
| 76 | | >>>[wiki:joekepley]: For the example page I drew up in the wireframe, the idea was that we had a repository that Ubuntu people should use instead of downloading the tarball; My plan was to explain the recommended install method for each distro in the (2) area, then alternates in the (4) area. So if, say, it's the Windows page, then there would be a big download link there to the installer exe. But if it's a Linux install that already has the latest Pidgin in the distro (or there's a repository provided), then the user should install through those methods unless they have a good reason not to. The sourceforge files page is pretty confusing to those 15 yo livecd users because it's not obvious what the smartest install option is. |
| 77 | | >>[wiki:lschiere]: Okay, I initially liked the idea of having our own repositories, but I have been thinking more about it. If you take a look at the SourceForge stats, we average around 100Gb/day for the downloads. That is more than this server will be able to handle. FAR more. We must *not* host the primary pull location here. If we start setting up repositories, and making that the suggested option, we are going to swamp this server. That means that as painful as SourceForge's release process is, this server does not replace that aspect of SourceForge for us. We still need their mirror network. |
| 78 | | >[wiki:joekepley]: Wow, good point on the bandwidth with that kind of traffic; that wasn't something I had considered. We can probably still go with separate install pages where it makes sense, but if a distro's own repository doesn't have the latest version, we can direct users to the appropriate download page on sourceforge. |
| | 75 | >>>>>[wiki:seanegan]: Where does the user actually click to download the package? Is it possible to download the package directly from the homepage, or do you have to go to this page first? From this page, where is the link to download? For UNIX distros, it would be nice if the home page contained two links, one for the binaries and one for the source... but in a way not to confuse the 15 year old Ubuntu livecd users. ;) |
| | 76 | >>>>[wiki:joekepley]: For the example page I drew up in the wireframe, the idea was that we had a repository that Ubuntu people should use instead of downloading the tarball; My plan was to explain the recommended install method for each distro in the (2) area, then alternates in the (4) area. So if, say, it's the Windows page, then there would be a big download link there to the installer exe. But if it's a Linux install that already has the latest Pidgin in the distro (or there's a repository provided), then the user should install through those methods unless they have a good reason not to. The sourceforge files page is pretty confusing to those 15 yo livecd users because it's not obvious what the smartest install option is. |
| | 77 | >>>[wiki:lschiere]: Okay, I initially liked the idea of having our own repositories, but I have been thinking more about it. If you take a look at the SourceForge stats, we average around 100Gb/day for the downloads. That is more than this server will be able to handle. FAR more. We must *not* host the primary pull location here. If we start setting up repositories, and making that the suggested option, we are going to swamp this server. That means that as painful as SourceForge's release process is, this server does not replace that aspect of SourceForge for us. We still need their mirror network. |
| | 78 | >>[wiki:joekepley]: Wow, good point on the bandwidth with that kind of traffic; that wasn't something I had considered. We can probably still go with separate install pages where it makes sense, but if a distro's own repository doesn't have the latest version, we can direct users to the appropriate download page on sourceforge. |
| | 79 | >[wiki:seanegan]: By the way, my question still isn't quite answered. The wireframe doesn't have any "click here to download" link. I think you're saying that Ubuntu wouldn't have one because we don't recommend that they download Gaim from our webpage. What would the Windows page look like? Would it be obvious how to download pidgin-2.0.0.exe, because right now it isn't. |
| | 80 | |
