How about we put this lines into the proposal to address the concern?
BTW, Baidu has a commercial product which is based on the HugeGraph.
I think it fine as long as the commercial product flow The Apache trademark 
policy[1] and keep the HugeGraph code clean. 

[1]https://www.apache.org/foundation/marks/services

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem


> On Jan 8, 2022, at 5:26 PM, Jermy Li <javalov...@gmail.com> wrote:
> 
> Hi
> 
> Yes I'm sure all the relevant repos at GitHub/hugegraph [1] will be donated
> to ASF.
> 
> At present, there are more than 10 sub-projects. For the convenience of
> management, we plan to merge them into 4 sub-projects [2].
> Some demo projects may be ignored(like hugegraph-plugin-stanford-analyzer),
> but all key projects will be donated.
> 
> [1] https://github.com/orgs/hugegraph/repositories
> [2] https://cwiki.apache.org/confluence/display/INCUBATOR/HugeGraphProposal
> (section
> #Initial Source)
> 
> --
> 
> Regards,
> 
> 
> Jermy Li | Senior Software Engineer @Baidu
> 
> javalov...@gmail.com <javalov...@gmail.com>
> 
> 
> Juan Pan <panj...@apache.org> 于2022年1月7日周五 22:47写道:
> 
>> Hello Dave,
>> 
>> 
>> There are a few repos of HugeGraph at GitHub, it’s too loose and not easy
>> to manage. So the team decides to merge some of repos into [1],
>> 
>> 
>> ```
>> 1. https://github.com/hugegraph/hugegraph
>> 2. https://github.com/hugegraph/hugegraph-computer
>> 3. https://github.com/hugegraph/hugegraph-commons
>> 4. [PLAN] The ecosystem repository hugegraph-toolchain, including
>> hugegraph-client, hugegraph-loader, hugegraph-tools, hugegraph-hubble,
>> hugegraph-test, hugegraph-doc:
>> https://github.com/hugegraph/hugegraph-toolchain
>> ```
>> Double-check here, All the relevant repos at Github will be donated to
>> ASF, right? @Jermy
>> 
>> 
>> [1]
>> https://cwiki.apache.org/confluence/display/INCUBATOR/HugeGraphProposal
>> 
>> ------------------------------------------------------------------------------
>> Juan Pan(Trista), Twitter: @tristaZero
>> 
>> 
>> On 01/7/2022 01:12,Dave Fisher<w...@apache.org> wrote:
>> Hi -
>> 
>> Not every repository at GitHub.com/hugegraph is included in the proposal.
>> What does the HugeGraph community intend to do with those repositories? Are
>> any of those key to the project?
>> 
>> Thanks,
>> Dave
>> 
>> On Jan 4, 2022, at 9:47 AM, Jermy Li <javalov...@gmail.com> wrote:
>> 
>> Hi, I'm Jermy from HugeGraph team. Thanks to mentors for introducing the
>> project.
>> 
>> @JB
>> We have sorted out a comparison(some main features of graph database)
>> between
>> HugeGraph and Neo4j + Titan/Janus, I'm glad to share with you:
>> 
>> 
>> (I post a picture here due to the table format can't be displayed well in
>> the email,
>> please refer to this link[1] for a text version.)
>> 
>> [1]
>> https://medium.com/@jermylee/comparison-of-graph-database-neo4j-janusgrraph-and-hugegraph-b144c527a6e2
>> <
>> https://medium.com/@jermylee/comparison-of-graph-database-neo4j-janusgrraph-and-hugegraph-b144c527a6e2
>>> 
>> 
>> --
>> Regards,
>> 
>> Jermy Li | Senior Software Engineer @Baidu
>> javalov...@gmail.com <mailto:javalov...@gmail.com>
>> Lidong Dai <lidong...@apache.org <mailto:lidong...@apache.org>>
>> 于2022年1月4日周二 22:56写道:
>> I'm so glad to see that HugeGraph will enter into the Apache Incubator!
>> 
>> I'm happy to be the mentor of the project.  As far as I know, HugeGraph
>> initial team has done a lot of work for this project.
>> 
>> BTW,  our new project also need a graph database, I think HugeGraph is a
>> good choice
>> 
>> 
>> Best Regards
>> 
>> 
>> 
>> ---------------
>> Apache DolphinScheduler PMC Chair
>> LidongDai
>> lidong...@apache.org <mailto:lidong...@apache.org>
>> Linkedin: https://www.linkedin.com/in/dailidong <
>> https://www.linkedin.com/in/dailidong>
>> Twitter: @WorkflowEasy <https://twitter.com/WorkflowEasy <
>> https://twitter.com/WorkflowEasy>>
>> ---------------
>> 
>> 
>> On Tue, Jan 4, 2022 at 7:02 PM Yu Li <car...@gmail.com <mailto:
>> car...@gmail.com>> wrote:
>> 
>> Thanks for driving this, Williem!
>> 
>> I'm happy to be the mentor of the project. I've had several conversations
>> with the team (both online and offline), and were attracted by their
>> technical taste and willingness of open source contribution and
>> collaboration. Hope the project could be accepted by the incubator, and
>> move on rapidly and healthy towards building up a great community!
>> 
>> @JB I happen to discuss with the team about comparison of existing graph
>> database systems, and would like to share some information here:
>> 
>> Comparison with AGE (I didn't find open document and below is my
>> understanding based on previous discussion):
>> 
>> - Common features of HugeGraph and AGE:
>> - Both support complete graph query language. AGE supports
>> openCypher, and HugeGraph supports Apache Gremlin.
>> - Both support basic graph CRUD operations.
>> - Both support PostgreSQL as backend storage, and the organisation of
>> the stored graph data is similar.
>> - Difference between HugeGraph and AGE:
>> - Different ways of integrating PostgreSQL: AGE runs as a plug-in of
>> PostgreSQL, while HugeGraph runs PostgreSQL as an independent storage
>> system.
>> - Besides supporting PostgreSQL as the storage backend, HugeGraph
>> supports a variety of other backends, such as RocksDB (the
>> default),
>> Cassandra, HBase, MySQL, etc. in a pluggable way.
>> - Besides supporting basic graph CRUD operations, HugeGraph also
>> supports real-time OLTP graph algorithm, distributed OLAP graph
>> calculation, rich attribute/graph indices and schema constraints,
>> etc.
>> 
>> 
>> Comparison with Neo4j and JanusGraph/Titan:
>> 
>> - Please refer to this document [1], and there are more benchmark data
>> here [2] (in Chinese now, and I believe English translation is on the
>> way)
>> 
>> 
>> Hope the information helps, and please feel free to correct me or give
>> supplements here, team (smile).
>> 
>> Best Regards,
>> Yu
>> 
>> [1]
>> https://blog.actorsfit.com/a?ID=01650-caeae70a-01c9-4ab8-a440-07b24e732ee7
>> <
>> https://blog.actorsfit.com/a?ID=01650-caeae70a-01c9-4ab8-a440-07b24e732ee7
>>> 
>> [2]
>> 
>> 
>> https://hugegraph.github.io/hugegraph-doc/performance/hugegraph-benchmark-0.5.6.html
>> <
>> https://hugegraph.github.io/hugegraph-doc/performance/hugegraph-benchmark-0.5.6.html
>>> 
>> 
>> On Tue, 4 Jan 2022 at 16:47, Jean-Baptiste Onofré <j...@nanthrax.net
>> <mailto:j...@nanthrax.net>> wrote:
>> 
>> Hi Willem,
>> 
>> it looks like an interesting project.
>> 
>> Just for my curiosity, how can we compare HugeGraph with Neo4j, Titan,
>> or PostgreSQL AGE ?
>> Especially in term of graph distribution, parallel processing, etc ?
>> 
>> Thanks !
>> Regards
>> JB
>> 
>> On 04/01/2022 03:27, Willem Jiang wrote:
>> Hi
>> 
>> First happy new year to everyone!
>> 
>> We want to propose HugeGraph[1]  as a new Apache Incubator project.
>> 
>> HugeGraph is a large-scale and easy-to-use graph database. In the case
>> of 100+ billion data (vertices and edges), HugeGraph has complete
>> HTAP[2] capabilities built in its internal system. The design goal of
>> HugeGraph is to achieve a balance between availability, performance
>> and cost.
>> 
>> I'd be happy to be the Champion of this project and may Thanks to
>> Trista Pan (panjuan at apache dot org),Lidong Dai (lidongdai at apache
>> dot org),Xiangdong Huang (hxd at apache dot org),Yu Li (liyu at apache
>> dot org) for being the mentor of HugeGraph project and helping us to
>> polish the incubating proposal[2].
>> 
>> Looking forward to your feedback and thank you very much.
>> 
>> [1]https://github.com/hugegraph/hugegraph/ <
>> https://github.com/hugegraph/hugegraph/>
>> [2]
>> https://en.wikipedia.org/wiki/Hybrid_transactional/analytical_processing <
>> https://en.wikipedia.org/wiki/Hybrid_transactional/analytical_processing>
>> [3]
>> https://cwiki.apache.org/confluence/display/INCUBATOR/HugeGraphProposal <
>> https://cwiki.apache.org/confluence/display/INCUBATOR/HugeGraphProposal>
>> 
>> Best Regards,
>> 
>> Willem Jiang
>> 
>> Twitter: willemjiang
>> Weibo: 姜宁willem
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org <mailto:
>> general-unsubscr...@incubator.apache.org>
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> <mailto:general-h...@incubator.apache.org>
>> 
>> 
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org <mailto:
>> general-unsubscr...@incubator.apache.org>
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> <mailto:general-h...@incubator.apache.org>
>> 
>> 
>> 
>> 
>> 


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Reply via email to