Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Derby Development" <derby-dev@db.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of jta@bristowhill.com designates
 66.75.162.135 as permitted sender)
Message-ID: <431867C4.1050901@bristowhill.com>
Date: Fri, 02 Sep 2005 07:55:00 -0700
From: "Jean T. Anderson" <jta@bristowhill.com>
User-Agent: Mozilla Thunderbird 1.0.2-1.3.2 (X11/20050324)
MIME-Version: 1.0
To: Derby Development <derby-dev@db.apache.org>
Subject: Re: Bugs and 10.1.2 release
References: <4310AA29.8000403@sbcglobal.net> <4315EEAA.6040201@debrunners.com>
 <4317695E.1090207@sun.com> <43176D5A.4070805@debrunners.com>
 <4317712F.1020600@Sourcery.Org> <43177A53.6030809@sun.com>
 <43178B15.3010402@Sourcery.Org>
In-Reply-To: <43178B15.3010402@Sourcery.Org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Satheesh Bandaram wrote:
> I am not sure if we should put our general process info on a Wiki.. Are
> you proposing effectively moving most of the website info to the Wiki? I
> would rather have Jean or some PMC member control the process info and
> changes to it. She has been very effective in managing the site so far.
> For all other stuff, including coding and architectural ideas/tips, Wiki
> is great. Can Wiki have pointers back to website for process info? :-)
> 

Wikis are really great when the info is still fluid. Once it stabilizes, 
it's nice to catch that snapshot on the web site.

Remember: content on the web site (including current content) does not 
have to be in forrest xml source files and you do not have to become 
knowledgeable about forrest unless you choose to. For more info, see:

http://db.apache.org/derby/papers/index.html#How+to+Contribute+Papers

  -jean