Yeah, this looks great Pei, thanks!

Steve

On Dec 3, 2012, at 5:47 PM, "Masanz, James J." <[email protected]> wrote:

> Thanks Pei!
> 
> 
>> -----Original Message-----
>> From: [email protected]
>> [mailto:ctakes-dev-return-935-
>> [email protected]] On Behalf Of Chen, Pei
>> Sent: Monday, December 03, 2012 10:46 AM
>> To: [email protected]
>> Subject: RE: Incubator PMC/Board report for Dec 2012 ([ppmc])
>> 
>> See Draft Below:
>> 
>> --------------------
>> cTAKES
>> 
>> cTAKES (clinical Text Analysis and Knowledge Extraction System) is a
>> natural language processing (NLP) tool for information extraction from
>> electronic medical record clinical free-text.
>> 
>> cTAKES was voted into the Incubator by the IPMC on Monday, June 11,
>> 2012.
>> 
>> Three most important steps moving towards graduation
>> 
>>  - Attract new contributors
>>  - Make at least one cTAKES release
>>  - Get everyone's ICLA on file and start developing code at Apache and
>> using
>>    the infrastructure
>> 
>> Community:
>> 
>>  We have had additional committers and PPMC members join.
>>  We have the Software Grants on file from the necessary
>> institutions(CTAKES-2).
>>  We have been using JIRA tickets to replace the Bugs tickets.
>>  We have been actively using the ASF mailing lists for communication,
>> with over 328 mails in ctakes-dev@ in Nov.
>> 
>> Development:
>> 
>> - We successfully migrated the cTAKES codebase from SourceForge to ASF
>> SVN.
>> - We have been successfully using Maven builds and ASF Nexus for staging
>> our development.
>> - We have integrated cTAKES with continuous integration using ASF
>> Jenkins.
>> - We have updated the code base to include ASF copyright headers to
>> source files.
>> - We have integrated the Apache RAT plug-in for Audit.
>> - We have updated the README/LICENSE files appropriately.
>> - We have a release candidate (3.0.0-incubating) pending Review/Vote.
>> - The ctakes-dev@ discussions have been active.
>> 
>> --Pei
>> 
>>> -----Original Message-----
>>> From: Marvin [mailto:[email protected]]
>>> Sent: Saturday, December 01, 2012 11:50 AM
>>> To: [email protected]
>>> Subject: Incubator PMC/Board report for Dec 2012 ([ppmc])
>>> 
>>> 
>>> 
>>> Dear podling,
>>> 
>>> This email was sent by an automated system on behalf of the Apache
>>> Incubator PMC.
>>> It is an initial reminder to give you plenty of time to prepare your
>>> quarterly board report.
>>> 
>>> The board meeting is scheduled for Wed, 19 December 2012, 10:00:00
>> PST.
>>> The report for your podling will form a part of the Incubator PMC
>>> report. The Incubator PMC requires your report to be submitted 2 weeks
>>> before the board meeting, to allow sufficient time for review and
>>> submission (Wed, Dec 5th).
>>> 
>>> Please submit your report with sufficient time to allow the incubator
>>> PMC, and subsequently board members to review and digest. Again, the
>>> very latest you should submit your report is 2 weeks prior to the
>> board meeting.
>>> 
>>> Thanks,
>>> 
>>> The Apache Incubator PMC
>>> 
>>> Submitting your Report
>>> ----------------------
>>> 
>>> Your report should contain the following:
>>> 
>>> * Your project name
>>> * A brief description of your project, which assumes no knowledge of
>>> the project
>>>   or necessarily of its field
>>> * A list of the three most important issues to address in the move
>> towards
>>>   graduation.
>>> * Any issues that the Incubator PMC or ASF Board might wish/need to
>>> be aware of
>>> * How has the community developed since the last report
>>> * How has the project developed since the last report.
>>> 
>>> This should be appended to the Incubator Wiki page at:
>>> 
>>>  http://wiki.apache.org/incubator/December2012
>>> 
>>> Note: This manually populated. You may need to wait a little before
>>> this page is
>>>      created from a template.
>>> 
>>> Mentors
>>> -------
>>> Mentors should review reports for their project(s) and sign them off
>>> on the Incubator wiki page. Signing off reports shows that you are
>>> following the project - projects that are not signed may raise alarms
>> for the Incubator PMC.
>>> 
>>> Incubator PMC
> 

Reply via email to