Sourceforge could solve some of these problems: Web hosting (of static files). Sourceforge provide this, and it should perform well. If there is no dynamic code there should be no administrative overhead.
Mantis: We could run this ourselves using php+mysql on sourceforge servers, but we would have to admin it ourselves. Their hosted apps service does not currently support importing data, so we would not be able to use that to host our existing bug tracker. Having to upgrade it manually would be a *major* pain, from what nextgens has said... Wiki: Sourceforge can provide hosted MediaWiki, which will immediately solve the problem of our french wiki. However, our english wiki is using Wikka, which is nonstandard. We probably want to migrate it to MediaWiki at some point... Other stuff: Mailing lists: Past experience suggests we don't want to use sourceforge's mailing list services, so we will need to find somewhere else. https://checksums.freenetproject.org : We need SSL with redirects, so that the update scripts continue to work; and architecturally it's the Right Thing... Mailing list archives: We could rely entirely on third parties, quite a few providers archive our lists. Anywhere we get mailman from will probably provide basic non-searchable pipermail archiving. Some paid providers do free installation and upgrades of mantis, mediawiki etc. For example, godaddy hosting connection, which is included with their $6.99/mo 150GB space / 1500GB transfer deal; whether we would be able to import our existing data is not immediately clear. IMHO this would solve most of the above problems: - Web hosting. - https://checksums - Mantis. *Possibly* hosted (if we can import data), if not we could admin ourselves. - MediaWiki. - File hosting. (If it's over 1500GB for a release, then we use CoralCache that month). However, it doesn't solve the mailing lists issue. Neither does Sourceforge or Google in a satisfactory way. On Saturday 30 May 2009 11:55:17 Matthew Toseland wrote: > We need to get rid of emu. It costs us a significant amount of money and we > don't seem able to cost-effecitvely administer it. > > Basically what we need: > - PHP scripts. The website is built with PHP. > - Database-backed PHP for MANTIS. I don't think we should get rid of MANTIS. > - SSL. We need to serve checksums and signatures through SSL, although big > files will generally be served through HTTP. It would be nice to serve the > installer through SSL if we have a huge traffic limit, since code signing > certs are expensive, on the other hand if we get cheaper hosting we can > probably afford to buy a code signing cert with a fraction of the money > saved... > - IMAP accounts ideally, but at least aliases. > > What we do NOT need: > - Auto-build. This is difficult to secure, and not really compatible with a > secure git-based workflow. > > Anything I've missed? > > One option: > > http://www.uk2.net/web-hosting/ > > Includes SSL, IMAP, 1TB traffic per month (bandwidth is very expensive with > bytemark, even if we qualified for the 50% discount for the main distributor > of free software), domain hosting, and a (very basic) uptime SLA, for ?13.95 > to ?19.95/mo depending on how long we buy it for (2 years down to 1 month). > > Thoughts? -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 835 bytes Desc: This is a digitally signed message part. URL: <https://emu.freenetproject.org/pipermail/devl/attachments/20090603/436b9e74/attachment.pgp>
