On Tue, Oct 25, 2016 at 8:03 PM, John D. Ament <johndam...@apache.org> wrote: > > > On Tue, Oct 25, 2016 at 10:27 PM Anthony Baker <aba...@pivotal.io> wrote: >> >> What I’m taking from this thread is that: >> >> 1) We (the Geode project) need to rework the README now that we have maven >> artifacts available. > > I'm not sure the relationship. There's two issues I see with the current > docs. > > 1. They're pointing to Pivotal, meaning you need to go to a vendor to > understand how to use Geode. While I understand this was a late donation > from Pivotal, it should be treated as a priority to use ASF docs.
Thanks for spotting a couple of links in the README -- we need to change it. > 2. They're pointing to client libraries from that same vendor. The project > should provide OOTB self maintained libraries for developers to leverage the > tool, without the use of a third party. Which libraries are you talking about? The ones I see all are available either from Spring.io or from Maven central. > I'll point out that one of your mentors has suggested that this project is > really close to graduation... based on what I'm seeing (and to explain - > this isn't a random drive by, I'm looking at alternate persistence stores > for ActiveMQ Artemis), this project still has very close ties to a vendor > and unless it can separate that I'm not sure it can graduate. John, while I appreciate your very constructive feedback and diligent mentorship I feel your assessment is unfair. In fact, $ git grep -i pivotal in the workspace provides a very instructive count of how far the project has gone to distance itself from the vendor it came from (and the fact that you can fit it on a single screen is even more instructive). On top of that -- there ALWAYS will be value added components that certain vendors are going to distributed around the project. That includes Pivotal. As it stands, Geode is fully self-contained which is not to say it provides all the client functionality one could think of. While excessive advertisement of such additional functionality is clearly not accepabtle, tactuflly pointing users at the directions of open source extensions (Spring.io) or even closed source ones (Pivotal, Ampool, SnappyData) is quite an accepted practice. Thanks, Roman.
