Return-Path: Delivered-To: apmail-commons-dev-archive@www.apache.org Received: (qmail 43961 invoked from network); 4 Aug 2007 19:20:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 4 Aug 2007 19:20:50 -0000 Received: (qmail 81614 invoked by uid 500); 4 Aug 2007 19:20:49 -0000 Delivered-To: apmail-commons-dev-archive@commons.apache.org Received: (qmail 81111 invoked by uid 500); 4 Aug 2007 19:20:48 -0000 Mailing-List: contact dev-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list dev@commons.apache.org Received: (qmail 81102 invoked by uid 99); 4 Aug 2007 19:20:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Aug 2007 12:20:48 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of flamefew@gmail.com designates 209.85.146.181 as permitted sender) Received: from [209.85.146.181] (HELO wa-out-1112.google.com) (209.85.146.181) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 Aug 2007 19:20:42 +0000 Received: by wa-out-1112.google.com with SMTP id k34so1221201wah for ; Sat, 04 Aug 2007 12:20:22 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=gnhg4wrTy8bQ2THgMXMyz8dZ3ITfzfHCiepU7xrcUKOu2eVGbw/J7Ev40LeJV6tNcE0V2ShEufz02CMAiU438mWjz5PhnEl1epGfHkSzszyiUYLU3aEGRdsd4RDIBQpe+Je5irEaM7AdryVAVERXL0p30MRtGtRbwfAlPEBW180= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=F7+lP8ugj46n+nnF8vsK999jI1sU9dWlWfko+eKHZ1oyoF6vy4k5vZk8w2ERBl2h8ZvpIlC/umYY9QUv1I6owreFZdDRk9PWaISG+cAmmJS88kZBSnstw2EPg4RsNn4exilPfjoH8bYN0SRGnrbArGjVhxpEYNGHBhZ7wlgXHpg= Received: by 10.115.17.1 with SMTP id u1mr4132575wai.1186255222561; Sat, 04 Aug 2007 12:20:22 -0700 (PDT) Received: by 10.115.92.8 with HTTP; Sat, 4 Aug 2007 12:20:22 -0700 (PDT) Message-ID: <31cc37360708041220r60dcfd12n5031267ff2d79094@mail.gmail.com> Date: Sat, 4 Aug 2007 12:20:22 -0700 From: "Henri Yandell" To: "Jakarta Commons Developers List" Subject: Re: [all] Wiki enabling fields in JIRA? In-Reply-To: <20070804132422.GB21719@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <46B33884.5080109@apache.org> <31cc37360708040203ue3cfe02pe28e27f8d350c25@mail.gmail.com> <20070804132422.GB21719@localhost> X-Virus-Checked: Checked by ClamAV on apache.org On 8/4/07, Jeff Turner wrote: > On Sat, Aug 04, 2007 at 02:03:54AM -0700, Henri Yandell wrote: > > When it came up before, I thought there was a problem with enabling it > > on an existing project? How do all the old issues look? Did they get > > wiki'd? > > Old issues get wikified too. > > Suggestion from the peanut gallery: make the change and see if anyone > complains. IMO the benefits are worth it. Besides {code}, it's handy to > be able to link to [urls|http://foo.com] and [attached files|^foo.txt] > inline. What happens to http://foo.com on its own? Currently that gets turned into a link, will all the links we have get unlinked? If these are the primary gains, it seems to me that wikified issues are worse than normal ones. Links are harder to do, making code easier to do is actually a bad idea as we'd much rather see patches than code dumps, and being able to link to an attached file is a nice to have - rarely needed. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org For additional commands, e-mail: dev-help@commons.apache.org