It's easy to make a offline discussion if you are setting together,
but it's impossible for the outside contributor to know the design
details without having a face 2 face talk with the core development
team. Open Source means openness and cooperation, we should avoid
internal discussions to
Yes, I agree to set up workflow for ShardingSphere. After discussion, I
think make a general and clear open source rule and workflow is important.
I talk with Craig during ApacheCon, he also suggested that.
ShardingSphere has entered apache incubator about 10 moths, I am glad to
see our
+1
We should build a work flow that people outside JD can also complete a core
feature.
As initial committer, we should share our knowledge on how to resolve problems,
Break requirements down into small pieces that can do pull request and review
by others.
--
Zhao Jun
Apache
Hi Sheng,
Thanks for your suggestions for ShardingSphere community.
After scanning your suggestions, some of pains brought up really exist now, i
think. Moreover, sorry, i did.
After ShardingSphere entering into incubator, it is growing up quickly, but its
growth of community can not keep
