Essentially the problems are: 1. Hosting the static web site and files. This includes web hosting, hosting big files, fixed redirects over SSL, etc. It may involve moving from https://checksums to somewhere else, but it will still have to include SSL.
This can be solved fairly easily with Google Apps and Google Web Apps and Google Release System, or can be solved with a very cheap paid hosting service. 2. Hosting mailing lists. Most likely this will be solved by using berlios. Hopefully they provide searchable archives, but arguably that isn't our problem as many third parties do this already. 3. The bug tracker. This is a big one. MANTIS has some serious disadvantages - it is a pain to maintain, it is written in php and therefore has security issues. And other bug trackers might very well be better at helping developers to get their job done. Mantis can be hosted (by sourceforge or by godaddy), but it is not clear whether it will be possible to import existing data. Or it can be manually maintained on any paid-for php+database web hosting service, which we don't want to do if we can avoid it. IMHO it is important that we keep the existing data. On the other hand I might support keeping it in some static form and using a new bug tracker, if a new bug tracker was demonstrably better. What bug tracker should we use? Trac? Jira? Lighthouse? Something else? 4. The wikis. We have a French wiki using MediaWiki and an English wiki using Wikka. It is highly unlikely we will find anywhere, free or otherwise, that hosts managed Wikka, so we will probably have to convert it to MediaWiki - or start again. Again, IMHO it is important to keep existing content as not doing so results in significant new work having to be done. We need to decide on #3 and #4, IMHO these are the real blockers. #1 can be solved, but I don't think it makes sense to try to solve it until we have decided what we are going to do about #3 and #4 because it will influence the architecture of the solution to #1. I would also like to point out that we've spent a lot of time on this already! -------------- 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/20090604/8e772c54/attachment.pgp>
