I tried to write *February* report and here it is. please review.

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 third 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?

  * Suggestion from community on interactive graph visualization feature is
under development(S2GRAPH-174)
  * Initial committer who has been dormant for a while become active
on(S2GRAPH-172)
How has the project developed since the last report?

  * Support GraphQL as standard web interface. (S2GRAPH-172)
  * Support Elastic Search as global index provider. (S2GRAPH-175)
  * Add Embedded RocksDB as storage backend. (S2GRAPH-166)
  * Provide java client.
    - Define public interface and change code base to only use interface.
(S2GRAPH-170)
    - Implementing java client is not yet started.

How would you assess the podling's maturity?
Please feel free to add your own commentary.

  [ ] Initial setup
  [ ] Working towards first release
  [x] Community building
  [ ] Nearing graduation
  [ ] Other:

Date of last release:

  2017-08-26

When were the last committers or PPMC members elected?

  None

Signed-off-by:

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


On Thu, Feb 1, 2018 at 5:50 PM DO YUNG YOON <sho...@gmail.com> wrote:

> I am going to volunteer this time, and will write it by this weekend.
>
> Thanks for notifying.
>
> On Tue, Jan 30, 2018 at 1:35 PM Sergio Fernández <wik...@apache.org>
> wrote:
>
>> Any volunteer for this reporting cycle?
>>
>> On Mon, Jan 29, 2018 at 8:20 PM, <johndam...@apache.org> 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, 21 February 2018, 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, February 07).
>> >
>> > 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/February2018
>> >
>> > 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