...
- I think that #1 has been less than optimal recently. We've had a couple of recent projects where most of the discussion has been "should it be an independent project or a repo of another project." I suggested subprojects as a potential compromise for future cases like this, but there are many other possible ways to handle this kind of issue (maybe a project taxonomy, for instance).
- On #2, the proliferation of projects has confused outsiders. I can't count the number of times I've been asked how to build "an Ursa blockchain." While I am definitely in favor of project proliferation, we need a way to control the message to the outside. What we have right now is really confusing for newbies.
- As for #3, I think I (and a lot of others) were frustrated a bit by some of the recent project discussions. We need to make things clear-cut. While there will always be corner cases that require judgment calls, these should ideally be as few as possible. This goes along with my points on #1.
What do you all think?
Bobbi:
To speak to point # 2, In order to reduce confusion for newcomers, consistent learning materials that convey the Hyperledger could be designed to control the message.