Hi all,


Since this is our first go at this, I thought I’d start us out with this basic 
report and we can iterate it here in this loverly time-series database system 
known as email. ;)



Here’s my first crack at it, Randall (CC’d has also mentioned assisting with 
this editing work). If you’re interested in helping with this sort of thing, 
please volunteer. :)



Here’s the in-progress Incubator status report we’ll be adding our info to:

http://wiki.apache.org/incubator/October2016



And here is our content so far:



--------------------

Annotator



Annotator provides annotation enabling code for browsers, servers, and humans.



Annotator has been incubating since 2016-08-30.



Three most important issues to address in the move towards graduation:



  1. continue to migrate existing community to the ASF

  2. setup infrastructure (web site, repos, issue tracker) here at the ASF

  3. engage with committers listed in our Proposal and discuss code plans



Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be

aware of?



  None at this time.





How has the community developed since the last report?



  Many participants from the previous mailing list have signed-up on the 
[email protected]<mailto:[email protected]> 
mailing list. We are still learning the ASF systems, but are working to collect 
more accurate numbers on the migration of the community here.





How has the project developed since the last report?



  We are still getting on our feet with regards to community, so no code has 
been developed at present. Our core targets are collecting the community here, 
launching the web site, and setting up the various repos and issues. Code 
collaboration will follow those.





Date of last release:



  XXXX-XX-XX – none at this time.



When were the last committers or PMC members elected?







Signed-off-by:



  [ ](annotator) Nick Kew

  [ ](annotator) Brian McCallister

  [ ](annotator) Daniel Gruno

  [ ](annotator) Jim Jagielski



Shepherd/Mentor notes:







--------------------



Thanks!

Benjamin



--
http://bigbluehat.com/
http://linkedin.com/in/benjaminyoung



From: [email protected]<mailto:[email protected]>
Sent: Sunday, October 2, 2016 9:13 AM
To: 
[email protected]<mailto:[email protected]>
Subject: Podling Report Reminder - October 2016



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 October 2016, 10:30 am PDT.
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, October 05).

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/October2016

Note: This is 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