2015-05-03 16:09 GMT+02:00 Sergio Fernández <[email protected]>: > Hi Benedikt, > > I though the groupId was discussed (and agreed) more than one month ago, > see http://markmail.org/thread/65dh2n2ppbfwnoj4 > > Implicitly I think that decision means we all agree on continuing towards > the initial path of graduating as a Apache Commons component. Is there any > new concern now? >
No new concerns, just the old "incubating releases published under org.apache.commons group Id and then decide to go TLP with a different group Id" concerns ;-) I think that would really cause confusion. > > But I do agree to get [email protected] involved to get them know about that > at the same time we ask abut permissions to deploy artifacts to it. I'll > take care. > Thanks! Benedikt > > Cheers, > > > > On Sun, May 3, 2015 at 10:36 AM, Benedikt Ritter <[email protected]> > wrote: > > > I'm about to get [email protected] involved. My last information > > about > > whether or not Commons RDF is going to join the Apache Commons project > was, > > that this has not been decided by the preference was to join Apache > Commons > > in the long term. > > Since Commons RDF is planning to publish artifacts under the Apache > Commons > > GroupId, has the project officially decided to become a component of > Apache > > Commons after incubation? If not, I think it's time to resolve this > (with a > > [VOTE]?!) before any artifacts have been published to MC. > > > > br, > > Benedikt > > > > > > > > > > > > >> > > >> I know Jenkins takes care of such deployments, but I was just > verifying > > >> some things towards the release. > > > > > > > > >> Cheers, > > >> > > >> > > >> On Thu, Apr 30, 2015 at 9:01 AM, Sergio Fernández <[email protected]> > > >> wrote: > > >> > > >> > OK, now that COMMONSRDF-6 looks closer to its resolution, our > backlog > > >> > looks clean for proceeding with our first release: > > >> > > > >> > > > >> > > > >> > > > https://issues.apache.org/jira/issues/?jql=project%20%3D%20COMMONSRDF%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20DESC > > >> > > > >> > Due Peter's timezone I'd still await to the (European) afternoon to > > >> > resolve COMMONSRDF-6, and then I'll prepare the release from the > > current > > >> > HEAD (48dc067806e627d4871a2aee09bec5b27f84e3e7) and cast the vote. > > >> > > > >> > In the meantime all comments are welcomed ;-) > > >> > > > >> > > > >> > > > >> > > > >> > On Wed, Apr 29, 2015 at 9:01 AM, Sergio Fernández < > > >> > [email protected]> wrote: > > >> > > > >> >> As I've just commented on COMMONSRDF-6, I'm fine with the two > changes > > >> >> Peter proposed. I think they do not change the essence behind the > > >> patch, > > >> >> but just make less strong some wording. So should be fine to update > > be > > >> PR > > >> >> with those minor changes before merging into master for starting to > > >> work on > > >> >> 0.1.0-incubating release. > > >> >> > > >> >> On Tue, Apr 28, 2015 at 10:20 AM, Stian Soiland-Reyes < > > >> [email protected]> > > >> >> wrote: > > >> >> > > >> >>> at least some kind of *reference seems to be what we're settling > on > > :) > > >> >>> > > >> >>> On 27 April 2015 at 16:27, Sergio Fernández <[email protected]> > > >> wrote: > > >> >>> > ups... > > >> >>> > > > >> >>> > On Mon, Apr 27, 2015 at 4:31 PM, Sergio Fernández < > > >> >>> > [email protected]> wrote: > > >> >>> > > > >> >>> >> I'd prefer internalIdentifier(), but uniqueReference() should > be > > >> also > > >> >>> fine > > >> >>> >> > > >> >>> > > > >> >>> > I actually wanted to say "I'd prefer internalReference(), but > > >> >>> > uniqueReference() should be also fine". > > >> >>> > > > >> >>> > Sorry for the (big) mistake. I guess this discussion is taking > too > > >> long > > >> >>> > that I can get confused when thinking about solutions. > > >> >>> > > > >> >>> > -- > > >> >>> > Sergio Fernández > > >> >>> > Partner Technology Manager > > >> >>> > Redlink GmbH > > >> >>> > m: +43 6602747925 > > >> >>> > e: [email protected] > > >> >>> > w: http://redlink.co > > >> >>> > > >> >>> > > >> >>> > > >> >>> -- > > >> >>> Stian Soiland-Reyes > > >> >>> Apache Taverna (incubating), Apache Commons RDF (incubating) > > >> >>> http://orcid.org/0000-0001-9842-9718 > > >> >>> > > >> >> > > >> >> > > >> >> > > >> >> -- > > >> >> Sergio Fernández > > >> >> Partner Technology Manager > > >> >> Redlink GmbH > > >> >> m: +43 6602747925 > > >> >> e: [email protected] > > >> >> w: http://redlink.co > > >> >> > > >> > > > >> > > > >> > > > >> > -- > > >> > Sergio Fernández > > >> > Partner Technology Manager > > >> > Redlink GmbH > > >> > m: +43 6602747925 > > >> > e: [email protected] > > >> > w: http://redlink.co > > >> > > > >> > > >> > > >> > > >> -- > > >> Sergio Fernández > > >> Partner Technology Manager > > >> Redlink GmbH > > >> m: +43 6602747925 > > >> e: [email protected] > > >> w: http://redlink.co > > >> > > > > > > > > > > > > -- > > > http://people.apache.org/~britter/ > > > http://www.systemoutprintln.de/ > > > http://twitter.com/BenediktRitter > > > http://github.com/britter > > > > > > > > > > > -- > > http://people.apache.org/~britter/ > > http://www.systemoutprintln.de/ > > http://twitter.com/BenediktRitter > > http://github.com/britter > > > > > > -- > Sergio Fernández > Partner Technology Manager > Redlink GmbH > m: +43 6602747925 > e: [email protected] > w: http://redlink.co > -- http://people.apache.org/~britter/ http://www.systemoutprintln.de/ http://twitter.com/BenediktRitter http://github.com/britter
