On 4 July 2016 at 17:23, A. Soroka <[email protected]> wrote:
> This seems a bit problematic to me. What about the cases (which are really > the cases of interest) for which there is no horizon in time at which the > work is to "catch up" in any particular sense, for which the extension > modules have an independent future? That is indeed the danger.. that approach works well for what aims to be integrated additions. But that said, Fuseki 2 has managed to become integrated. > This seems intriguing-- are you suggesting that the new folks would be able > to make releases out of the special "sidecar" code-base? What relationship > would this proposal have with the formal incubation process? This is kind of > asking for Jena to have multiple repositories under the Apache org, which > seems reasonable to me, but then, I don't understand the implications for > Infra and the work they would have to do for this. Yes, obviously practically the actual release would have to be done by an existing committer, but there is nothing stopping a PMC to own multiple git repositories, see for instance: http://git.apache.org/ It's just a few clicks in Jira to ask Infra to make a new repository - with a few checks later that say the GitHub Pull Request integrations are working. > I think this makes sense for a lot of possible projects (larger ones, > mostly). But the example in hand (a Commons RDF impl) is one where the size > of project doesn't seem to merit a new Apache incubation, right? No, that's the kind of thing a PMC can just bootstrap on its own. BTW - I've now added https://github.com/apache/incubator-commonsrdf/tree/jena/jena so I guess that particular example is now moot :) > I like this, in many ways. It's low-cost, simple, and flexible. But I don't > know enough about Apache methods to understand what the implications are for > "ownership". Is it possible for a project (Jena) to "lay claim" to a GitHub > org like that without some kind of formal arrangement with GitHub, and if > not, is that formalization difficult or costly? Such a GitHub group would not be formally associated with ASF or Jena PMC (and that would have to be made clear) - just with particular individuals who happen to also be part of Jena. See the bottom of https://taverna.incubator.apache.org/download/code/#taverna-extras for how we did this - note that we used it more of a 'dumping ground' for license incompatible stuff - that kind of thing would earlier have been done at "Apache Extras" at Google Code https://code.google.com/a/apache-extras.org/hosting/ - but as Google Code now is in Read-only that is no longer an option. -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons http://orcid.org/0000-0001-9842-9718
