Here is my draft for the report this time.

S2Graph

S2Graph is a distributed and scalable OLTP graph database built on Apache
HBase to support fast traversal of extremely large graphs.

S2Graph has been incubating since 2015-11-29.

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

  1. Make a second release.
  2. Attract more users and contributors.
  3. Build the developer community in both size and diversity.

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

  None

How has the community developed since the last report?

  * Mailing lists have been quiet.
    - one inquery on full text search feature support.

How has the project developed since the last report(Feb 2017)?

  * Development has been quiet.
    - Working on Integration with Apache TinkerPop3
      - StructureStandardSuite has been passed.
      - ProcessStandardSuite has been begun. 325/582 passed, 257 failed.

  * Issues resolved/created: 0/1

Date of last release:

  Apache S2Graph 0.1.0-incubating on 2016-11-01.

When were the last committers or PMC members elected?

  None

Signed-off-by:

  [ ](s2graph) Andrew Purtell
  [ ](s2graph) Seetharam Venkatesh
  [ ](s2graph) Sergio Fernández


Following is my random thought.

Personally, I was not-active for a while and got back on April then started
to work on ISSUE-136. As it turns out validating S2Graph's tinkerpop
integration is way more than just one issue. I think making issue very
specific and clear can help interested folks to start.

For example, in ISSUE-136

1. I had to setup test environment for gremlin-tests which I spend lots of
time to figure out what is expected schema for each tests.
2. Actually implement interfaces.
3. Validate if implementation is correct.
4. Check if test case assumption is also applicable to s2graph. there are
lots of test cases, which are either dependents or independents.

I think in this case, it would be much easier for interested folks to
involve if each test cases separated as each independent issues.

Also I feel that we have not set clear milestone for the release. what to
be included must be discussed first, then we should focus on issues that
related to upcoming release. tinkerpop3 support has been in my mind for
milesone for 0.2.0 release, but never been decided and discussed through
mailing list.

I am happy to volunteer above if other folks agrees.

On Thu, Apr 27, 2017 at 4:10 PM Sergio Fernández <[email protected]> wrote:

> Who volunteers for reporting this time?
>
> I'd like to use this report to discuss where the podling is going. The
> community looks very quite. And I don't see development since December:
> https://github.com/apache/incubator-s2graph/commits/master Options on the
> table are many, but I;'d like to gather more feedback.
>
> On Thu, Apr 27, 2017 at 2:41 AM, <[email protected]> wrote:
>
> > 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, 17 May 2017, 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, May 03).
> >
> > 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.
> > *   How does the podling rate their own maturity.
> >
> > This should be appended to the Incubator Wiki page at:
> >
> > https://wiki.apache.org/incubator/May2017
> >
> > 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