home contents changes options help subscribe edit

Stand-alone pages

System

Documentation

DownloadArea

WebPages?

Internal

Mailing lists

Translations

Unlike one of our proprietary competitors, we do not have a translation web interface. Installing Pootle (http://translate.sourceforge.net/) and integrating it with Savane would be great. Other improvements would be to connect it directly to the repository to edit the .po using a more intuitive web interface.

Note: Pootle is currently (1/2009) merging different branches and switching to the Django web framework. The latest release isn't very stable, but the next ought to be :)

http://transifex.org/ is not a web interface but rather attempts to simplify and unify the translation workflow, easing maitainers/translators interactions.

The Translation Project (http://www.translationproject.org/) doesn't have tools to edit the .po and .pot per se, but they have a publication system to manage them by team. It manages a good part of the GNU projects, including coreutils and GCC. The source code can be found at: http://svn.vrijschrift.org/tp-repo/TP/

Tools to work with .po:

Other projects:

Assigned to:

Wiki

Provide a wiki for projects: problems include spam and replication for 2500+ projects. Or 1 big wiki for everybody, but we need to have a solid spam protection first. The goal is to avoid setting up a wiki that will be filled with spam, with not enough visitors to fix it (we're not as big as Wikipedia just yet ;)). Note that WikiSpam? is usually different than (unfortunately) more common mail spam.

The format used by the wiki is also important. It would be good to be able to switch to another wiki system in the future, if needed.

This very wiki is hosted by ZWiki, but it relies on Zope. We don't have much experience with Zope, but from what we could see it doesn't seem suitable for hosting a lot of wikis. For example, the size of the ZODB grows large very quickly (600M for 1 wiki, which we thus had to purge).

Suggestion for anti-spam: I think that one of the most useful anti-spam features would actually be statistics. We have numerous anti-spam systems in different areas, but little data on how much spam was caught, nor ways to quickly review caught spam to check for possible false positives. It would be good to have a set of anti-spam features that we could enable or disable, and then see how effective it was.

Another discussion: http://lists.gnu.org/archive/html/savannah-hackers-public/2009-01/msg00003.html

  • Work-around: manual sync from temp wiki site to .gnu.org for the Hurd Wiki
  • Disallow non-member contribution (not recommended)

Find a nice wiki for that, consuming little resource

zodb size --simon, Sat, 13 Oct 2007 08:35:23 +0000 reply

Hi Beuc.. zodb files get large, but that's just historical records chewing up disk space, and does not correspond to memory usage. Many zope sites have zodb files of 1G or more. Pack it periodically to keep the size down. FYI I host 30 zwikis on one server and 60 on another without problem.

zodb size --Beuc, Sat, 13 Oct 2007 09:30:46 +0000 reply

Hi, that's what I meant with "purge", that is, "pack". I had to throw away the wiki history because of that. I think I read that new ZWikis? version are using their own history format to avoid this problem, though. Anyway maybe I'm wrong, but until now I don't find Zope very practical, packing being one of the burdens.

zodb size --simon, Sat, 13 Oct 2007 15:42:38 +0000 reply

That's correct, current Zwiki preserves edit history through packs. Well it's easy to pack nightly with a cron job, but I hear you, chat me if I can help.




subject:
  ( 12 subscribers )