Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: bloodhound-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of olemis@gmail.com designates
 209.85.210.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <50BDD462.7040803@wandisco.com>
References: <20121201152616.D2A73D8C0@minotaur.apache.org>
	<CAKoya927iLnOFWGDP3D0guZLYCBVurhae2=-mva7JN3jEx0ihA@mail.gmail.com>
	<50BC821F.6030809@wandisco.com>
	<CAJSKAsi59dWUrs3UxF=Hn8U2oNxWax=XJPZ_2RFeCmdwCRhqYA@mail.gmail.com>
	<50BC9D79.6050205@wandisco.com>
	<50BCE700.2030702@wandisco.com>
	<CAKoya92NfV71r+QGwOGGGifF9zGHdUJb0MvjLmGRrKsZz2=r5g@mail.gmail.com>
	<CAJSKAsh_0RsAUASM9s7V47s0+n_AA+tU=QY=owNTHWMcETqrwQ@mail.gmail.com>
	<CAGMZAuM+zjn0Ni1H3a1sczimLF3z-_jLFbsKAqOL1VcjT9gyig@mail.gmail.com>
	<50BDD462.7040803@wandisco.com>
Date: Tue, 4 Dec 2012 09:29:16 -0500
Message-ID: 
 <CAGMZAuMpWaffb4SHNne0EE+7Qk9=GvRoQUiNBYVOrV16b31SrQ@mail.gmail.com>
Subject: Re: Incubator PMC/Board report for Dec 2012 ([ppmc])
From: Olemis Lang <olemis@gmail.com>
To: bloodhound-dev@incubator.apache.org
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

On 12/4/12, Gary Martin <gary.martin@wandisco.com> wrote:
> On 03/12/12 22:54, Olemis Lang wrote:
>> On 12/3/12, Peter Ko=C5=BEelj <peter@digiverse.si> wrote:
>>> For point 3 ...
>> [...]
>>
>> btw , will we release a new version in December ?
>
> I am certainly hoping that we will.
>

good !
:)

>>
>>> For point 2, from personal experience, it is not that bad. Setup was
>>> fairly
>>> straightforward but I did miss some documentation on software
>>> design/architecture and such. Actually Trac's are good enough and maybe
>>> we
>>> should simply point to read-worthy pieces and add some of our own for B=
H
>>> code.
>>>
>> two suggestions :
>>
>> 1. add the wiki page in #139 to i.a.o
>
> It would naturally go in on release of 0.4.

ok

> I suppose we could have a
> section in the wiki for upcoming documentation or the documentation of
> upcoming features.
>

Interesting . Maybe that's what BEP are for , but if there is a need
for something different than that , I think it's ok .

>> 2. mention the work we started on BEPs as a means to gather
>>      community consensus and eventually also being a reference,
>>      and documentation of major changes .
>
> So to meet this suggestion I could append something like the following
> to the final paragraph:
>
> Along these lines, the project has added a number of enhancement proposal
> pages to the wiki that are intended to reflect the decisions made on the
> project's dev mailing list, reducing the need to be aware of all previous
> discussion for newcomers.
>

"One such proposal documents how the community will work on tickets
submitted to the issue tracker. As a consequence in a few minutes new
contributors will understand our workflow and the reasons we
considered to install it ."

... more or less ... please improve .
;)

--=20
Regards,

Olemis.

Blog ES: http://simelo-es.blogspot.com/
Blog EN: http://simelo-en.blogspot.com/

Featured article: