crprashant commented on issue #1783: URL: https://github.com/apache/age/issues/1783#issuecomment-4625785963
**Update — and a placement/governance question before I open a PR** I've been implementing this as a first-party LlamaIndex `PropertyGraphStore` for AGE — i.e. the modern property-graph API that the Neo4j/Memgraph/Kuzu integrations use, rather than the legacy triplet `GraphStore`. It's a graph-only **v0.1**, built as a thin adapter over `psycopg3`, with a unit test suite plus a live PostgreSQL + Apache AGE integration suite (both passing). Vector support is planned for a later v0.2. Before I send a PR, I'd appreciate the PMC's guidance on two things so it lands in the right place: 1. **Where should the integration live?** The two options I see are (a) in-tree in `apache/age` under an `integrations/` directory, or (b) a separate repository (an `apache/age-…` repo or a community-maintained one). Is there a preference or precedent for where AGE integrations should be hosted? 2. **PyPI publishing / ownership.** To be `pip install`-able (the whole point of a first-party integration), the package would be published to PyPI as `llama-index-graph-stores-age`. Should that release be owned/published under the ASF, or maintained externally? This affects the `age` naming (Apache trademark) and the release cadence, so I'd rather confirm it up front than reserve the name in the wrong place. Once I know the preferred home, I'm happy to open the PR and walk through the design, tests, and CI. Thanks! -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
