I guess community is gonna be hard. In three years most of the contributors
(if not all) come from the same company that donated the original source
base.

Would be an option to graduate as a subproject of an existing TLP? I don't
know, TinkerPop?

On Mon, Sep 10, 2018 at 5:15 AM Hwansung Yu <deejayf...@gmail.com> wrote:

> As Doyung said in previous report emails, three things are important for
> graduation.
>
> 1. Make a third release.
> 2. Attract more users and contributors.
> 3. Build the developer community in both size and diversity.
>
> The third release is what we have to discuss and do in the community.
>
> Increasing user and contirubutor and activating community seem like the
> same issue on board.
>
> Previously (in November 2016, when I looked up the mail) there was a
> discussion to add a new committer, but the committer was not added. how you
> think about finishing this discussion and adding a committer.
>
> I think most graph database projects has small community compared to other
> major apache projects.
> So I think it is not easy to make new users or developers feel attractive.
> But small communities are not always meaningless projects.
>
> What are some ways to activate our community? Can you help me?
>
> 2018년 9월 10일 (월) 14:52, Sergio Fernández <wik...@apache.org>님이 작성:
>
> > signed-off
> >
> > I think we should discuss the future of the podling sooner than later. I
> > can see the graduation farther than ever.
> >
> > On Sun, Sep 2, 2018, 20:33 DO YUNG YOON <sho...@gmail.com> wrote:
> >
> > > Hi folks.
> > >
> > > I was bit busy during the last 2 month and missed our podling report
> for
> > > August.
> > >
> > > Here I try to write the report for September.
> > >
> > > Please feel free to comment.
> > >
> > >
> > >
> > > 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 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?
> > >
> > > * not much activities on the mailing list.
> > > * few active committers spend their time working on opened issues.
> > >
> > > How has the project developed since the last report?
> > >
> > > * mostly still working on opened issues.
> > >   - 22 issues are created and 16 of them are resolved since the last
> > > report(June 2018).
> > >   - keep working on GraphQL integration/OLAP supports.
> > >
> > > 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:
> > >
> > > IPMC/Shepherd notes:
> > >
> > >
> > >
> > > On Mon, Sep 3, 2018 at 9:55 AM <jmcl...@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, 19 September 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, September 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.
> > > >
> > > > Candidate names should not be made public before people are actually
> > > > elected, so please do not include the names of potential committers
> or
> > > > PPMC members in your report.
> > > >
> > > > 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/September2018
> > > >
> > > > 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