microsoft / microsoft/semantic-kernel-java
Feature Parity Inquiry: Multi-Agent Orchestration and Roadmap Alignment with Python/.NET Versions
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 276
- Forks
- 56
- Avg merge
- 17h 45m
- Merged PRs (30d)
- 4
Description
Description:
Currently observing significant functional gaps between semantic-kernel-java and its Python/.NET counterparts (e.g., Python/.NET already support multi-agent orchestration, while Java version remains at LLM+Tool level).
Key Questions:
- Roadmap Alignment
Are there plans to bring Java version to full feature parity with Python/.NET (especially multi-agent workflows.)?
If yes, what is the estimated timeline for major milestones?
- Divergence Policy
Will Java remain a functionally reduced version due to technical constraints, or is the disparity temporary?
Interop Possibilities
For features not natively implemented in Java (e.g., Dapr integration in .NET), will there be workarounds like interop with Python services?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points to investigate. Start by reviewing the Java project's current feature scope against the referenced Python and .NET versions; done means a clear roadmap, divergence policy, timeline, and interop position are documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, java, python
- Domain
- ai
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100