Github user afs commented on the issue:
https://github.com/apache/jena/pull/299
Every chance if the Jena committers and PMC agree.
Developing as a separate module, outside Jena, to start with helps the work
by not getting entangled in timing and release issues of Jena releases. It
also helps creates the community focused on the work.
The Jena project releases all modules in a single release process every 3
or 4 months. Users tend to expect continuity across releases. While getting
started, a module `rdfstar` may want to release as and when contributors and
code are ready, have flexibility to release new version rapidly, change
designs, and put API around RDF*graphs (RDF*-merge for example). Relying on PRs
to Jena is going to be a burden for that community initially.
If there are Jena changes needed (adding a new RDF term type `Node_Triple`
for example), PRs to get them in focused on the needs can be done.
(Do note - the Jena project is not a source of maintenance and support for
contributions. Depending on complexity, that might be something to discuss
nearer the time).
---
