btihen commented on issue #370:
URL: https://github.com/apache/age/issues/370#issuecomment-2295158486

   > Really nice. Maybe you should get featured in some Ruby/Rails newsletters 
to help gain interest/traction/support, when you feel the project is 'ready' of 
course.
   > 
   > Things that might help new interest:
   > 
   > * a 'state of the project' or a checklist of features implemented and 
features missing...
   > * a brief comparison to 
[activegraph](https://github.com/neo4jrb/activegraph) (ruby neo4jrb, which for 
one doesn't work in Rails 7.1)
   > * abstracting the 'ruby only' stuff to another gem, for those that don't 
use rails
   > * getting featured in the apache/age README as a community driver!
   > 
   > ...I think you can get a lot of help/contributors once the 'stars' start 
rolling in!
   
   Thanks for the feedback and encouragement.  I had a family emergency that 
took up all my time, so I put this aside for a bit.
   
   I haven't really this to activegraph - I know it has a ruby gem and a rails 
engine, but the code looked a bit hard to get into and I didn't see a little 
tutorial explaining how to create a rails app.  So I decided this would start 
with a focus on rails and making it easy to generate and use within the rails 
ecosystem.  Along with what I hope is an easy to use getting started and 
creating a nice quick rails app.
   
   So far I rely heavily on ActiveModel - so I if I do a ruby version at some 
point it might be done in 2 stages first with activemodel included and then 
maybe without.  
   
   At the moment if you are doing standard models and simple relations this is 
complete.  I figure to be useable for complex - real-world apps I need to allow 
cypher queries to be built similar to active record queries.  I think I have a 
nice approach.  Just testing the query aspects.  
   
   I also want to find a way to build simple path queries a lot like a node or 
an edge query and return a path object.  Just playing with that as mind 
experiments.  
   
   I figure when those are done (and hopefully tested by others) that can be a 
1.0 release.  
   
   Any help would be appreciated, however, I am not sure how many people are 
interested.
   
   Maybe it is just visibility, but I am not sure how many are interested in 
graph databases.  
   
   I was planning to introduce this to my local ruby community this fall and 
see what the response is like.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@age.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to