From ooo-dev-return-15905-apmail-incubator-ooo-dev-archive=incubator.apache.org@incubator.apache.org Mon Apr 2 14:01:33 2012 Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BC2549A97 for ; Mon, 2 Apr 2012 14:01:33 +0000 (UTC) Received: (qmail 5677 invoked by uid 500); 2 Apr 2012 14:01:33 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 5611 invoked by uid 500); 2 Apr 2012 14:01:33 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 5601 invoked by uid 99); 2 Apr 2012 14:01:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 14:01:33 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jogischmidt@googlemail.com designates 209.85.215.175 as permitted sender) Received: from [209.85.215.175] (HELO mail-ey0-f175.google.com) (209.85.215.175) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 02 Apr 2012 14:01:25 +0000 Received: by eaae1 with SMTP id e1so598484eaa.6 for ; Mon, 02 Apr 2012 07:01:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=thtwH0cTOlkOlE/XQolMH8F3m0sPsdhLslxdAph/WvQ=; b=tIkb/VMFPUCm+Esk8t+JQWQnIfG9eyJNOdW/9KztJu/ZJFni3VdsPBzUAkWgn3Mcpq YvX2KYPJXHIGgzBRp8xyigrqmeTWXqn5juyqBe1q9EMDF5W4DKWaIpkBNQC+N6AYD6Ol Cul4toORB4o1/5UA+a1SzCgFSeE5kAU49qu9s6y4MaM+O4uXi+W25Ood03c+7HjCLkmh LFYR3YApmwYT+GMHnsUAUc/bFvu50FayTHlkskRKAkMYtnSdBtHVPjOORJJeQUKC7bbK hPgL4s0bZb4uB0Su561taFhXPV85crzg28ADqOxYKqQiKSRsCKmbyoFFdi8TORlBKY18 pgLg== Received: by 10.152.114.35 with SMTP id jd3mr9547734lab.18.1333375265494; Mon, 02 Apr 2012 07:01:05 -0700 (PDT) Received: from [9.155.131.20] (deibp9eh1--blueice3n2.emea.ibm.com. [195.212.29.180]) by mx.google.com with ESMTPS id ox7sm24132070lbb.17.2012.04.02.07.01.04 (version=SSLv3 cipher=OTHER); Mon, 02 Apr 2012 07:01:04 -0700 (PDT) Message-ID: <4F79B11F.1060604@googlemail.com> Date: Mon, 02 Apr 2012 16:01:03 +0200 From: =?UTF-8?B?SsO8cmdlbiBTY2htaWR0?= User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0) Gecko/20120327 Thunderbird/11.0.1 MIME-Version: 1.0 To: ooo-dev@incubator.apache.org Subject: Re: [WIKI] Confusion about wikis and multilingual wiki References: In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit On 4/2/12 3:47 PM, Claudio Filho wrote: > Hi > > I read all emails (possible) about our wikis, but not found the logic > of when use one or other wiki - cwiki or mediawiki (what caused my > mistake when i tried to contribute to localization procedure page). > When i see propositions for project goes to cwiki, and procedures > (like localization) to mediawiki. IMHO, after try many softwares, i > was obliged in to agree that the userfriendly and useful interface of > mediawiki for final user or not technical volunteer. > the point is that we didn't want to loose any information in the old wiki. But here we have a unclear license situation of the content that was a mistake in the past. This is still an area where we need some work. We should identify as much as possible content with a clear license and should try to identify the problematic ones. I hope it is clear now that new contribution are under ALv2, if not we should discuss it again and should define it. > My doubt is what is the logic to write in one or other wiki? it's a unlucky situation :-( > > In other hand, what is the destination of content in mediawiki? Can we > reuse, organize and update there content? This question bring the > second point: multilingual wiki. > > Looking the localization process, we already have some translations > and i not understand why we haven't a localization toolbar in our > pages (a bar in top of page, where we can select the base language). if you think you can help here I would recommend that you join the dev@infrastructure mailing list and also join the IRC channel #asfinfra on freenode. Means become active and help the infrastructure project by contributing... That's the Apache way join a project and help where you can. In the long term you should get more and more permission (potentially become a committer there as well) and > > If we have interesting in continue working with mediawiki, i can help > in manage the content with focus to give us a good information > architecture and multilingual support. see above Juergen