imbajin commented on code in PR #2227:
URL: 
https://github.com/apache/incubator-hugegraph/pull/2227#discussion_r1219778695


##########
README.md:
##########
@@ -55,27 +59,38 @@ And here are links of other **HugeGraph** 
component/repositories:
 3. [hugegraph-commons](https://github.com/apache/incubator-hugegraph-commons) 
(**common & rpc** module)
 4. [hugegraph-website](https://github.com/apache/incubator-hugegraph-doc) 
(**doc & website** code)
 
-## Contributing
+## 🤝 Contributing
 
 Welcome to contribute to HugeGraph, please see [`How to 
Contribute`](CONTRIBUTING.md) for more information.
 
-## License
+Thank you to all the people who already contributed to HugeGraph!
 
-HugeGraph is licensed under Apache 2.0 License.
+[![contributors 
graph](https://contrib.rocks/image?repo=apache/hugegraph)](https://github.com/apache/incubator-hugegraph/graphs/contributors)
 
-## Thanks
+## ⏰ Contributor Over Time
+
+[![Stargazers Over 
Time](https://contributor-overtime-api.git-contributor.com/contributors-svg?chart=contributorOverTime&repo=apache/incubator-hugegraph)](https://git-contributor.com?chart=contributorOverTime&repo=apache/incubator-hugegraph)
+
+## 👍 Stargazers Over Time
+
+![Stargazers over 
time](https://api.star-history.com/svg?repos=apache/incubator-hugegraph&type=Date)

Review Comment:
   > I think it is reconcilable, put the 2 charts in the readme will be faster, 
the official website update is slower
   
   yep, but maybe we need listen the community voice (like a **vote** in 
**discussion** to choose what kind of chart we need show in the `README`), 
because it occupies a larger space



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to