You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sis.apache.org by Suresh Marru <sm...@apache.org> on 2013/07/18 14:36:59 UTC
GSoC sandbox in SVN
Hi All,
It will be good to have the google summer of code and any other student project codes directly in the SIS repository. We need to make sure they do not hamper with the main code base until they are properly integrated. So how about creating a sandbox area and commit all student projects there?
If there are no objections, I will create a https://svn.apache.org/repos/asf/sis/sandbox/gsoc2013 and have Nadeem submit patches to this repo.
Suresh
Re: GSoC sandbox in SVN
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
+1!
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: Adam Estrada <es...@gmail.com>
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Sunday, July 21, 2013 1:52 PM
To: "dev@sis.apache.org" <de...@sis.apache.org>
Subject: Re: GSoC sandbox in SVN
>Thanks Suresh!
>
>
>On Sun, Jul 21, 2013 at 4:51 PM, Suresh Marru <sm...@apache.org> wrote:
>
>> Hearing no objections, I created this directory.
>>
>> Thanks,
>> Suresh
>> On Jul 18, 2013, at 8:36 AM, Suresh Marru <sm...@apache.org> wrote:
>>
>> > Hi All,
>> >
>> > It will be good to have the google summer of code and any other
>>student
>> project codes directly in the SIS repository. We need to make sure they
>>do
>> not hamper with the main code base until they are properly integrated.
>>So
>> how about creating a sandbox area and commit all student projects there?
>> >
>> > If there are no objections, I will create a
>> https://svn.apache.org/repos/asf/sis/sandbox/gsoc2013 and have Nadeem
>> submit patches to this repo.
>> >
>> > Suresh
>>
>>
Re: GSoC sandbox in SVN
Posted by Adam Estrada <es...@gmail.com>.
Thanks Suresh!
On Sun, Jul 21, 2013 at 4:51 PM, Suresh Marru <sm...@apache.org> wrote:
> Hearing no objections, I created this directory.
>
> Thanks,
> Suresh
> On Jul 18, 2013, at 8:36 AM, Suresh Marru <sm...@apache.org> wrote:
>
> > Hi All,
> >
> > It will be good to have the google summer of code and any other student
> project codes directly in the SIS repository. We need to make sure they do
> not hamper with the main code base until they are properly integrated. So
> how about creating a sandbox area and commit all student projects there?
> >
> > If there are no objections, I will create a
> https://svn.apache.org/repos/asf/sis/sandbox/gsoc2013 and have Nadeem
> submit patches to this repo.
> >
> > Suresh
>
>
Re: GSoC sandbox in SVN
Posted by Suresh Marru <sm...@apache.org>.
Hearing no objections, I created this directory.
Thanks,
Suresh
On Jul 18, 2013, at 8:36 AM, Suresh Marru <sm...@apache.org> wrote:
> Hi All,
>
> It will be good to have the google summer of code and any other student project codes directly in the SIS repository. We need to make sure they do not hamper with the main code base until they are properly integrated. So how about creating a sandbox area and commit all student projects there?
>
> If there are no objections, I will create a https://svn.apache.org/repos/asf/sis/sandbox/gsoc2013 and have Nadeem submit patches to this repo.
>
> Suresh
Re: Learning release steps
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Le 18/07/13 16:08, Martin Desruisseaux a écrit :
> According [1], we need to create a JIRA ticket for Nexus authorization
> to deploy artefacts in the "org.apache.sis" namespace. Do we already
> have this authorization, or should I create a ticket?
For the record, I found INFRA-3177. I have been able to login to the
Nexus application, so this part seems to work.
Martin
[1] https://issues.apache.org/jira/browse/INFRA-3177
Re: Learning release steps (was: GSoC sandbox in SVN)
Posted by "Mattmann, Chris A (398J)" <ch...@jpl.nasa.gov>.
I think you may need this auth, Martin.
Cheers,
Chris
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Senior Computer Scientist
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 171-266B, Mailstop: 171-246
Email: chris.a.mattmann@nasa.gov
WWW: http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Assistant Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----Original Message-----
From: Martin Desruisseaux <ma...@geomatys.fr>
Organization: Geomatys
Reply-To: "dev@sis.apache.org" <de...@sis.apache.org>
Date: Thursday, July 18, 2013 7:08 AM
To: "dev@sis.apache.org" <de...@sis.apache.org>
Subject: Learning release steps (was: GSoC sandbox in SVN)
>Le 18/07/13 14:52, Suresh Marru a écrit :
>> A good question. A key certainly can be renewed and extended the expiry
>>time. But I never thought of this and makes me wonder. As you can read
>>here - http://www.gnupg.org/gph/en/manual.html#AEN329 the key expiry is
>>associated with the key's self sign. So I am not sure how will the
>>integrity be preserved. I am sure there will be a way and ASF has
>>experts who can answer this question. But to start with, I would not
>>worry about it but will poke around at leisure.
>
>Thanks a lot for the information. Looking at Apache documentation, the
>examples that I saw seem to create keys with unlimited validity time.
>
>According [1], we need to create a JIRA ticket for Nexus authorization
>to deploy artefacts in the "org.apache.sis" namespace. Do we already
>have this authorization, or should I create a ticket?
>
>
>[1] http://www.apache.org/dev/publishing-maven-artifacts.html#signing-up
>
Learning release steps (was: GSoC sandbox in SVN)
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Le 18/07/13 14:52, Suresh Marru a écrit :
> A good question. A key certainly can be renewed and extended the expiry time. But I never thought of this and makes me wonder. As you can read here - http://www.gnupg.org/gph/en/manual.html#AEN329 the key expiry is associated with the key's self sign. So I am not sure how will the integrity be preserved. I am sure there will be a way and ASF has experts who can answer this question. But to start with, I would not worry about it but will poke around at leisure.
Thanks a lot for the information. Looking at Apache documentation, the
examples that I saw seem to create keys with unlimited validity time.
According [1], we need to create a JIRA ticket for Nexus authorization
to deploy artefacts in the "org.apache.sis" namespace. Do we already
have this authorization, or should I create a ticket?
[1] http://www.apache.org/dev/publishing-maven-artifacts.html#signing-up
Re: GSoC sandbox in SVN
Posted by Suresh Marru <sm...@apache.org>.
On Jul 18, 2013, at 8:41 AM, Martin Desruisseaux <ma...@geomatys.fr> wrote:
> Hello Suresh
>
>
> Le 18/07/13 14:36, Suresh Marru a écrit :
>> If there are no objections, I will create a https://svn.apache.org/repos/asf/sis/sandbox/gsoc2013 and have Nadeem submit patches to this repo.
>
> Cool, thanks :-). On my side I had a look at the Shapefile new code and will post some proposals later. In the main time, I'm trying to find my way in the Apache release instructions, especially regarding PGP keys... I may post some questions later.
Yes, I will be happy to help if I can. My only constraints are I am traveling from July 21st to 26th, but otherwise available to assist with the release.
>
> Well, one question I have right now: if we create a key with limited validity time (e.g. 5 years), does anyone know what happen to softwares signed with that key after the validity time expired?
A good question. A key certainly can be renewed and extended the expiry time. But I never thought of this and makes me wonder. As you can read here - http://www.gnupg.org/gph/en/manual.html#AEN329 the key expiry is associated with the key's self sign. So I am not sure how will the integrity be preserved. I am sure there will be a way and ASF has experts who can answer this question. But to start with, I would not worry about it but will poke around at leisure.
Suresh
>
> Martin
>
Re: GSoC sandbox in SVN
Posted by Martin Desruisseaux <ma...@geomatys.fr>.
Hello Suresh
Le 18/07/13 14:36, Suresh Marru a écrit :
> If there are no objections, I will create a https://svn.apache.org/repos/asf/sis/sandbox/gsoc2013 and have Nadeem submit patches to this repo.
Cool, thanks :-). On my side I had a look at the Shapefile new code and
will post some proposals later. In the main time, I'm trying to find my
way in the Apache release instructions, especially regarding PGP keys...
I may post some questions later.
Well, one question I have right now: if we create a key with limited
validity time (e.g. 5 years), does anyone know what happen to softwares
signed with that key after the validity time expired?
Martin