apache
Process to add 3rd party solution providers to the Apache AGE documentation?
Hi there,
Quick intro - I'm Arthur Bigeard, the creator of G.V(), a graph database IDE compatible with many many graph databases. Apache AGE support has been a frequent request for us and I finally got round to implementing support for it, I'm hoping to release this in the next couple of weeks.
Is there a place in the documentation for Apache AGE that 3rd party integrations like ours can be mentioned?
The long story short of the integration is it allows connecting to Apache AGE instances, querying and visualizing the graph data, as well as editing and exploring it interactively (and a bunch more things) Including a little screenshot below to give you an idea of what this looks like:
Cheers, Arthur
@arthur-bigeard-gdotv I'm not sure it is appropriate to add this to the documentation. I did, however, create a discussion thread for this -
https://github.com/apache/age/discussions/2261
That makes perfect sense - we're neither free nor open source, unfortunately, but I'm sure there will be other solutions out there that could fit the bill. Apache TinkerPop has a "Powered By" section on their website (https://tinkerpop.apache.org/community.htm for reference) that does a good job of highlighting adoption and support of the framework from various providers out there. I know that there's support for Apache AGE in Azure Postgres, not sure if there are other places as well? Would be useful to see it listed somewhere.
@arthur-bigeard-gdotv Discussion #2224 does cover that. If yours fits in there, by all means mention it there.
@arthur-bigeard-gdotv I believe the project, and Apache, is fine having users mention where Apache AGE is available. However, these external sources are all unofficial and unsupported. I don't think Apache wants anyone to get the idea that Apache supports those providers, or provide support for them.
Understood - I get that there's a line not to cross there. I believe there's a precedent in Apache projects listing tools and implementations surrounding projects that could be of interest to users, as a way to showcase the ecosystem around the project. It's my own perspective of course but I had no idea until I accidentally found out the Apache AGE was available on Azure Postgres, and this is typically what I would describe as a "member" of the ecosystem. G.V() I think would also fit in that ecosystem. It provides Apache AGE users with a quick reference of what is being delivered on top of or for the project. Cassandra has a good page for that at https://cassandra.apache.org/_/ecosystem.html, it has a mix of open-source and commercial solutions listed.