Agreed.

We also need to think about improving the situation on training data. One
thing to think about is whether we can take advantage of DUALIST to
bootstrap the creation of training data:

http://code.google.com/p/dualist/

Jason

On Tue, Jun 7, 2011 at 3:41 PM, Jörn Kottmann <[email protected]> wrote:

> Exactly, I fully agree with Grant. We invested a lot of time to into this
> already, and I
> believe we are on the right way, we need to continue this effort and be
> patient.
>
> A contributor/committer is usually a user first, and therefore we need to
> make it as easy as possible
> for potential users to get started and to get involved. When people start
> using OpenNLP
> some might need to fix/change something and contribute it back.
>
> Jörn
>
>
>
> On 6/7/11 10:12 PM, Grant Ingersoll wrote:
>
>> One thing to think about and discuss is how to encourage/find new
>> committers.  Nominations of individuals should be done on the PPMC (private
>> list), but out here we should at least think about ways to help contributors
>> become committers.  In some cases, this may mean avoiding the tendency to
>> jump in and fix a problem before someone else, who is less experienced, can
>> put up a patch.   Other ways, are better documentation, encouragement, etc.
>> for those kicking the tires.    Generally speaking, my rule of thumb for
>> nominating someone is a few good quality patches that show they get the code
>> at a decent level as well as they show they get how the ASF and the project
>> work and can work positively with others in the community.
>>
>> Just food for thought as we move towards graduation, as I think OpenNLP is
>> moving along quite nicely as an Incubator project.
>>
>> -Grant
>>
>> On Jun 6, 2011, at 3:58 AM, Jörn Kottmann wrote:
>>
>>  Hi all,
>>>
>>> please report status items for our board report.
>>>
>>> Thanks,
>>> Jörn
>>>
>>
>


-- 
Jason Baldridge
Assistant Professor, Department of Linguistics
The University of Texas at Austin
http://www.jasonbaldridge.com
http://twitter.com/jasonbaldridge

Reply via email to