> On Feb 14, 2017, at 7:26 AM, Andy Seaborne <[email protected]> wrote: > > Nowadays, I think it is better to develop new capabilities through clones and > dynamic PRs and better to keep the main code repository as focused on the > main line of development so I propose deleting branches and closing JIRA as > noted above.
+1 I have just rebased ThreadPerGraphDataset (sorry about the slew of commit msgs!). I would like to land that branch, but we did not come to a conclusion here: https://github.com/apache/jena/pull/204 that I could find about how to do that. Andy remarked: > • "Small things" being curated go into a general > jena-extras/jena-wip/jena-labs/jena-optional module with the idea that that > is just while they mature, Downside: things go into that module and don't > progress. > • At the other end of the spectrum, this is a step for jena-ldp so to > get attention on that, use that name. Downside: over selling. > • Specific for this one thing: jena-writer-dsg, a name for the > write-centric dataset. Downside: does not connect to LDP usage. Thoughts? Is anyone else interested in bring an optional LDP component to Fuseki (or perhaps independently of Fuseki, a la jena-ldp)? --- A. Soroka The University of Virginia Library
