You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm interested in Nebula and have looked at it in the last few days. I think Nebula-Community is not doing a very good job, here are my two small suggestions:
Github Issue, I think the label classification of the current Issue is not particularly friendly to newcomers, for example, when I want to find whether there is a relatively simple bug in Nebula's Issue, I did not find the easy issue ( because there is no easy/ For example, when I tried to find out if there were any easier bugs in Nebula's Issue, I didn't find an easy issue (because there was no easy/medium/hard label) and the good first issue never seemed to appear :)
doc and blog, I have read this blog, but be honest, I only have an impression of a general source code flow after reading it, but not a good understanding of the module I want to know. So I would suggest to split the project into modules and do a source code analysis of each module, and in each issue, give a label according to the module involved, so that it is more friendly for Contributor.
Tons of thanks for your valuable thoughts and ideas shared here, we really treasure and appreciate them.
For 1. we are working on them, and hopefully soon, there will be properly organized issues/tasks labeled on both core and utils repos.
For 2. It's also what we were preparing for, and your idea here had made us rethink its priorities, hopefully, we'll have more contents dive into different function blocks of the nebula graph in the future.
Please stay tuned! And I would like to notify you when we have some progress here.
I'm interested in Nebula and have looked at it in the last few days. I think Nebula-Community is not doing a very good job, here are my two small suggestions:
我对 Nebula 比较感兴趣,并且这几天也看了一下。我觉得 Nebula-Community 并没有做的非常好,以下我的两点小小的建议:
The text was updated successfully, but these errors were encountered: