Le 2/13/12 3:01 PM, Francesco Chicchiriccò a écrit :
On 13/02/2012 11:43, Emmanuel Lécharny wrote:
Le 2/13/12 11:11 AM, Colm O hEigeartaigh a écrit :
Hi Francesco,

1. Move source code from http://syncope.googlecode.com/svn/ to
http://svn.apache.org/repos/asf/incubator/syncope/
Is there any best practice about this? I'd think that we should import
everything, not only the latest revision: how?
We will need to sort out IP issues first I think:

http://incubator.apache.org/ip-clearance/index.html

Once the IP issues are sorted out, the best way to transfer the source
is to use an svndump. Infra can import that directly and not lose any
history.
The links that apply to a poddling is :
http://incubator.apache.org/guides/mentor.html#poding-ip-clearance

and

http://incubator.apache.org/guides/mentor.html#initial-ip-clearance

What is important is that the authors have signed the ICLAs - all of
them -, and that means the poddling have identified all the contributors.
Fabio Martelli and I, as GoogleCode Syncope project owners sent over a
signed software grant to [email protected]: Craig Russel then sent
back an acknowledgement with [email protected] in CC.

We can safely import the code in our repo as soon as :

" Initial Code Dump

For corporate contributions, the SGA or CCLA MUST be completed,
submitted and received before the code is imported.

For contributions composed of patches from individual contributors, it
is safe to import the code once the major contributors (by volume)
have completed ICLAs or SGAs.

In either case, the code to be imported should be attached to a JIRA
and then imported. It is recommended that the previous version control
system is tagged so that the imported version is precisely known.

A public record MUST be made of the code imported. If the import is
not attached to JIRA then it MUST be committed to version control."


That means we can complete the IP clearance after the import.
How does it sound?

1. create an SVN tag on syncope.googlecode.com/svn (as required)
2. use svnsync to duplicate GoogleCode SVN repository, compress and put
this archive somewhere (say people.apache.org)
3. file a ticket to INFRA asking for importing such repository

Waiting for everything set up at ASF SVN, we'll continue working on
GoogleCode SVN repository: as soon as import is complete at ASF, we will
submit a patch for the diff between GoogleCode's trunk and the tag
created at (1).
This is needed because there are currently many things under ongoing
development.
sounds good to me. As the svn import in Apache will require a temporary Subversion shutdown, it may be delayed a bit. Be prepared for such a delay.

So +1 for the proposed action (unless another mentor has a better process to propose)

--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Reply via email to