incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Dudney <>
Subject Re: [PROPOSAL] Open JPA
Date Wed, 08 Mar 2006 22:30:06 GMT
Hi Guys,

Isn't the whole point of incubation community? We want the community  
and we want to grow it while in incubation.

Good doc and QA people will go just as far as good coders in building  
a user community (perhaps even further) while making it possible for  
the coders to build more code.

IMO we should be dancing in the streets that there is a QA and doc  
team ready to go.

Now on to the specifics of this proposal, if the people from BEA are  
involved because they are employees of BEA but don't really want to  
continue working on OpenJPA if/when their employment changes then I  
guess I'd not be so happy. But if they are committed to the project  
then I say welcome aboard, can we get some of your time over on  

BTW: I don't think its so easy to get good people of any skill set...


Bill Dudney
MyFaces -

On Mar 8, 2006, at 3:11 PM, robert burrell donkin wrote:

> On 3/8/06, Yoav Shapira <> wrote:
>> Hola,
>>> it's easy to get good open source coders: it's much harder to find
>>> good documentors who are willing to contribute to open source
>>> projects. demand for good documentation is always high but supply is
>>> typically low. i'm willing to cut good documentors much more slack
>>> than coders.
>> Hypothetically, does slack == commit privileges, or do we want to set
>> the bar for committership higher?
>> If Joe Q. Random emailed us saying he thinks [some currently in
>> incubation project] is great and he's a technical writer and would
>> like commit access so that he can write up the docs for it, would he
>> get that access?  Probably not,
> i'd say: submit a patch :)
> given enough good patches, i'd nominate them
>> but the difference here is that the
>> proposed documentors and QA people are already part of the team, so
>> they're not random...
>> I also suppose we can always review the status of documentation and
>> test cases at the end of incubation, see who did what, and  
>> accordingly
>> adjust the commiter list during incubator graduation?
> isn't this really an issue about the bootstrapping committer lists?
> should there be any difference between a coder who hasn't hacked a
> line and a documentor who hasn't written a word?
> - robert
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message