I think it looks great. Thanks! Adina
On Thu, Dec 31, 2015 at 2:01 PM, Aaron D. Mihalik <[email protected]> wrote: > Here's a shot: > > * A list of the three most important issues to address in the move > towards graduation. > > 1. Populate the website for the project > 2. Expand the "how to" document to explain the ways new contributors can > become involved in the project, so we increase the size of the community. > 3. Become familiar with the release process and have a first release as > part of the Apache Foundation > > * Any issues that the Incubator PMC or ASF Board might wish/need to be > aware of > > No > > * How has the community developed since the last report > > - We have documented (on Confluence) and tested procedures for committers > to review and incorporate Pull Requests into the incubator-rya Apache git > repository. > > - The committers are becoming much more comfortable with the Apache > infrastructure and processes. Committers have been documenting processes on > Confluence, creating Jira tickets, tying these to Rya components and > versions, and submitting and pulling in PRs to resolve these Jira tickets. > > - The Rya user community (i.e. non-committers) have begun submitting issues > through Jira and the dev list. These have become Jira tickets, resolved by > committers, and tested by the community. Specifically, the community > submitted RYA-19, RYA-17, and RYA-6. Committers resolved and the community > tested RYA-19 and RYA-17. > > - Non-committers have also begun submitting PRs that have been incorporated > into the apache repo. Specifically, RYA-13 and most of RYA-7 was done by > non-committers. > > - We've started logging "beginner" Jira tickets. These are issues that > we've found in Rya that a new developer could take on as a good way to "get > their feet wet" in the code base. > > * How has the project developed since the last report. > > - We've completed adding the Apache license headers and added license > header verification to the project's build. > > - Resolved a handful of issues that users have encountered. > > - Committed features: Delete support for secondary indices, more efficient > Mongo Core and Geo indexing. > > - Still working on creating a website for the project. > > - Working on deploying artifacts onto Maven > > - Working on creating a quick-start VM for users to try out Rya. > > > Date of last release: > > Not applicable > > When were the last committers or PMC members elected? > > Not applicable > > Signed-off-by: > > [ ](rya) Josh Elser > [ ](rya) Edward J. Yoon > [ ](rya) Sean Busbey > [ ](rya) Venkatesh Seetharam > > Shepherd/Mentor notes: > > > On Thu, Dec 31, 2015 at 1:23 PM Aaron D. Mihalik <[email protected]> > wrote: > > > yep, I'll take a shot. I'll post something to this list soon. > > > > On Thu, Dec 31, 2015 at 12:21 PM Adina Crainiceanu <[email protected]> > wrote: > > > >> Hi, > >> > >> We need to submit the next report to ASF. Can someone else work on this > >> and > >> submit it? I'm currently moving, unpacking, etc (not so much fun). > >> Instructions for submission are below. > >> > >> Thanks, > >> Adina > >> > >> > >> ---------- Forwarded message ---------- > >> From: Marvin Humphrey <[email protected]> > >> Date: Wed, Dec 30, 2015 at 5:04 PM > >> Subject: January 2016 Report > >> To: [email protected] > >> > >> > >> Greetings, {podling} developers! > >> > >> This is a reminder that your report is due next Wednesday, January > >> 6th. Details below. > >> > >> Best, > >> > >> Marvin Humphrey, Report Manager for January, on behalf of the > >> Incubator PMC > >> > >> --------------- > >> > >> 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, 20 January 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, January 6th). > >> > >> 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/January2016 > >> > >> 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 > >> > >> > >> > >> > >> -- > >> Dr. Adina Crainiceanu > >> http://www.usna.edu/Users/cs/adina/ > >> > > > -- Dr. Adina Crainiceanu http://www.usna.edu/Users/cs/adina/
