bitflicker64 commented on issue #376: URL: https://github.com/apache/hugegraph-ai/issues/376#issuecomment-5866571193
Had a few questions on how this would fit in the repo. Would KINA go in as its own top-level module, like hugegraph-mcp did? Own pyproject, its own CI, not part of the `all` extra. That way the existing modules aren't affected while it's still at v0.3 ? One more idea, not sure if it fits the plans: could bigger features like this be done as plugins? Core stays stable, community plugins live outside and get merged in once they're mature. hugegraph-ai would need some kind of extension mechanism for that (Python entry points maybe), a few stable interfaces, somewhere to list plugins (a docs page or a repo under the `hugegraph` org), and some rule for when a plugin moves into the main repo. Could also help with the integrations KINA lists as gaps, like graph engines, LLMs and BI/ERP connectors. Happy to help with in anyway possible ! -- 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
