[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Savannah-cvs] [SavaneTasks] (edit) split Savane and non-Savane tasks

From: Beuc
Subject: [Savannah-cvs] [SavaneTasks] (edit) split Savane and non-Savane tasks
Date: Sat, 10 Jan 2009 10:04:17 +0000

-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:
-* Official webpages need to be validated by maintainers and their 
team - open wiki can be a problem
- * Work-around: manual sync from temp wiki site to for the Hurd Wiki
- * Disallow non-member contribution (not recommended)
Mailing list subscription

* auto-invite people to these lists on either account or project creation

 * look for a way to easily invite people (mailing list command?)

-Unlike one of our proprietary competitors, we do not have a translation web 
interface. Installing Pootle ( 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.
- is not a web interface but rather attempts to simplify 
and unify the translation workflow, easing maitainers/translators interactions.
-Tools to work with .po:
- * - the Translate 
Toolkit, used by Pootle.
- * - .po parser
- * - - only an initial 
code import
-Assigned to:

-Assigned to:
-From simon Sat Oct 13 08:35:23 +0000 2007
-From: simon
-Date: Sat, 13 Oct 2007 08:35:23 +0000
-Subject: zodb size
-Message-ID: <address@hidden://>
-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.
-From Beuc Sat Oct 13 09:30:46 +0000 2007
-From: Beuc
-Date: Sat, 13 Oct 2007 09:30:46 +0000
-Subject: zodb size
-Message-ID: <address@hidden://>
-In-Reply-To: <address@hidden://>
-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 
-[10 more lines...]

forwarded from

reply via email to

[Prev in Thread] Current Thread [Next in Thread]