Re: [IVY] setup of infrastructure

[Brett Porter <br...@gmail.com>]

On 31/10/06, Xavier Hanin <xa...@gmail.com> wrote:
> > Does Ivy want to import history, or just the latest code?
>
>
> An history import would be nice, but isn't there a problem with legal
> issues, since old code was not under Apache License? And maybe the easier is
> just to import latest code (well, I should release a new version next week -
> maybe the last pre apache version, so it may be a good time to import just
> after the release). What do other think?

If it were me, I'd rather import the history than having to maintain
it myself. There are no legal issues (BSD is compatible with the
Apache License).

Cheers,
Brett

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [IVY] setup of infrastructure

[Jim Jagielski <ji...@jaguNET.com>]

Could it have been sent from 0557530080 on
Oct 31 at '10:27' ??

If so, then yes, please resend. We rec'd an unreadable
fax (very, very light) and the only thing clear
was the "header" lines added by the sending FAX
machine.

On Nov 2, 2006, at 9:17 AM, Xavier Hanin wrote:

> On 11/2/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
>>
>> On 11/2/06, Xavier Hanin <xa...@gmail.com> wrote:
>>
>> > How can I know that the paperwork is ok? I've already sent my  
>> ICLA and
>> the
>> > software grant, but I don't know if they were properly received and
>> > processed.
>>
>> One of your mentors should be able to watch the files in the private
>> repos where those get recorded.  It sometimes takes the ASF secretary
>> a few days to get around to processing them, but if they don't get
>> recorded fairly soon it's often a good idea to resend.
>
>
> Ok, thanks. I sent my ICLA last week and the software grant last  
> tuesday,
> and Antoine told me he can't see them, so maybe I should resend  
> them. I'll
> also try to send them by postal mail to be sure there's no problem  
> with the
> fax.
>
> Xavier
>
> -garrett
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [IVY] setup of infrastructure

[Xavier Hanin <xa...@gmail.com>]

On 11/2/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
>
> On 11/2/06, Xavier Hanin <xa...@gmail.com> wrote:
>
> > How can I know that the paperwork is ok? I've already sent my ICLA and
> the
> > software grant, but I don't know if they were properly received and
> > processed.
>
> One of your mentors should be able to watch the files in the private
> repos where those get recorded.  It sometimes takes the ASF secretary
> a few days to get around to processing them, but if they don't get
> recorded fairly soon it's often a good idea to resend.


Ok, thanks. I sent my ICLA last week and the software grant last tuesday,
and Antoine told me he can't see them, so maybe I should resend them. I'll
also try to send them by postal mail to be sure there's no problem with the
fax.

Xavier

-garrett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [IVY] setup of infrastructure

[Garrett Rooney <ro...@electricjellyfish.net>]

On 11/2/06, Xavier Hanin <xa...@gmail.com> wrote:

> How can I know that the paperwork is ok? I've already sent my ICLA and the
> software grant, but I don't know if they were properly received and
> processed.

One of your mentors should be able to watch the files in the private
repos where those get recorded.  It sometimes takes the ASF secretary
a few days to get around to processing them, but if they don't get
recorded fairly soon it's often a good idea to resend.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [IVY] setup of infrastructure

[Xavier Hanin <xa...@gmail.com>]

On 11/1/06, Garrett Rooney <ro...@electricjellyfish.net> wrote:
>
> On 11/1/06, Brett Porter <br...@gmail.com> wrote:
> > Usually, a dumpfile is used rather than a zipped up repository, I think.
> >
> > I would suggest locating an svn admin who can work with you to do a
> > test now - so you'd dump the repository without locking it out, load
> > it up into the test repository, check it works, so that you know what
> > to do and minimise downtime of your commit access when you are ready
> > to do the real thing.
> >
> > I'm not an svn admin either, though - so best to get in touch with
> > them and see how they usually do it :)
>
> A zipped up repository (assuming it's in fsfs format, not bdb) is just
> as easy for us to work with as a dumpfile, just means there's one more
> step for the infra person doing the job (usually me).


In our case using a dump file may be easier, because our svn repository
wasn't properly setup: a unique repository for several projects, and no
branches / tags / trunk / releases directories. So I will have to use svn
admin tools on a dump file to get a clean repository with standard
directories. So if a dumpfile is as easy to use for you as a zipped
repository, I think I will send a dumpfile.

The other thing we need is a list of the committers who have committed
> to the repos in question and the mapping from their old username to
> their ASF username so we can convert the old svn:author revprops to
> match the new ASF usernames, for consistency.


OK, I'll send this list too when we'll be ready.

Once both of those are available, and all the paperwork (CLAs,
> software grants, etc) are sent in and acknowledged by the ASF
> secretary just file an INFRA Jira ticket to schedule things and we'll
> get it moving.


How can I know that the paperwork is ok? I've already sent my ICLA and the
software grant, but I don't know if they were properly received and
processed.

Thanks for your time,
- Xavier

-garrett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [IVY] setup of infrastructure

[Garrett Rooney <ro...@electricjellyfish.net>]

On 11/1/06, Brett Porter <br...@gmail.com> wrote:
> Usually, a dumpfile is used rather than a zipped up repository, I think.
>
> I would suggest locating an svn admin who can work with you to do a
> test now - so you'd dump the repository without locking it out, load
> it up into the test repository, check it works, so that you know what
> to do and minimise downtime of your commit access when you are ready
> to do the real thing.
>
> I'm not an svn admin either, though - so best to get in touch with
> them and see how they usually do it :)

A zipped up repository (assuming it's in fsfs format, not bdb) is just
as easy for us to work with as a dumpfile, just means there's one more
step for the infra person doing the job (usually me).

The other thing we need is a list of the committers who have committed
to the repos in question and the mapping from their old username to
their ASF username so we can convert the old svn:author revprops to
match the new ASF usernames, for consistency.

Once both of those are available, and all the paperwork (CLAs,
software grants, etc) are sent in and acknowledged by the ASF
secretary just file an INFRA Jira ticket to schedule things and we'll
get it moving.

-garrett

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [IVY] setup of infrastructure

[Brett Porter <br...@gmail.com>]

Usually, a dumpfile is used rather than a zipped up repository, I think.

I would suggest locating an svn admin who can work with you to do a
test now - so you'd dump the repository without locking it out, load
it up into the test repository, check it works, so that you know what
to do and minimise downtime of your commit access when you are ready
to do the real thing.

I'm not an svn admin either, though - so best to get in touch with
them and see how they usually do it :)

Cheers,
Brett

On 02/11/06, Upayavira <uv...@odoko.co.uk> wrote:
> Xavier Hanin wrote:
> > On 11/1/06, Upayavira <uv...@odoko.co.uk> wrote:
> >>
> >> Xavier Hanin wrote:
> >> > On 11/1/06, Brett Porter <br...@gmail.com> wrote:
> >> >>
> >> >> On 31/10/06, Xavier Hanin <xa...@gmail.com> wrote:
> >> >> > > Does Ivy want to import history, or just the latest code?
> >> >> >
> >> >> >
> >> >> > An history import would be nice, but isn't there a problem with
> >> legal
> >> >> > issues, since old code was not under Apache License? And maybe the
> >> >> easier is
> >> >> > just to import latest code (well, I should release a new version
> >> next
> >> >> week -
> >> >> > maybe the last pre apache version, so it may be a good time to
> >> import
> >> >> just
> >> >> > after the release). What do other think?
> >> >>
> >> >> If it were me, I'd rather import the history than having to maintain
> >> >> it myself. There are no legal issues (BSD is compatible with the
> >> >> Apache License).
> >> >
> >> >
> >> > Thanks for your advice Brett. I'll go with history import if it's not
> >> too
> >> > complex to import into apache infrastructure. Can someone tell me what
> >> you
> >> > expect from our svn repository to do the import?
> >>
> >> If you can block all commit access to the repository, then a simple zip
> >> should do the job, If I understand correctly.
> >
> >
> > I can block access to the repository. So the only thing is to zip the
> > directory on my svn server containing the db directory, is that it? This
> > means that the hook directory will be part of the zip, I currently have a
> > hook for sending mail on commit, but I think there's already something like
> > this on apache usual svn install, no? So maybe the db directory is enough?
> > We use a filesystem based svn repository, is that ok? It's a lot of
> > question
> > I'm sorry, but I'm not familiar with ASF infrastructure.
>
> No, the hooks directory won't be needed. However, I'm not as
> knowledgeable as you might think, and would suggest you just zip up the
> lot, including hooks directory, just to be safe, unless someone else
> more knowledgeable tells you otherwise.
>
> Regards, Upayavira
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>


-- 
Apache Maven - http://maven.apache.org
"Better Builds with Maven" book - http://library.mergere.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [IVY] setup of infrastructure

[Upayavira <uv...@odoko.co.uk>]

Xavier Hanin wrote:
> On 11/1/06, Upayavira <uv...@odoko.co.uk> wrote:
>>
>> Xavier Hanin wrote:
>> > On 11/1/06, Brett Porter <br...@gmail.com> wrote:
>> >>
>> >> On 31/10/06, Xavier Hanin <xa...@gmail.com> wrote:
>> >> > > Does Ivy want to import history, or just the latest code?
>> >> >
>> >> >
>> >> > An history import would be nice, but isn't there a problem with 
>> legal
>> >> > issues, since old code was not under Apache License? And maybe the
>> >> easier is
>> >> > just to import latest code (well, I should release a new version 
>> next
>> >> week -
>> >> > maybe the last pre apache version, so it may be a good time to 
>> import
>> >> just
>> >> > after the release). What do other think?
>> >>
>> >> If it were me, I'd rather import the history than having to maintain
>> >> it myself. There are no legal issues (BSD is compatible with the
>> >> Apache License).
>> >
>> >
>> > Thanks for your advice Brett. I'll go with history import if it's not
>> too
>> > complex to import into apache infrastructure. Can someone tell me what
>> you
>> > expect from our svn repository to do the import?
>>
>> If you can block all commit access to the repository, then a simple zip
>> should do the job, If I understand correctly.
> 
> 
> I can block access to the repository. So the only thing is to zip the
> directory on my svn server containing the db directory, is that it? This
> means that the hook directory will be part of the zip, I currently have a
> hook for sending mail on commit, but I think there's already something like
> this on apache usual svn install, no? So maybe the db directory is enough?
> We use a filesystem based svn repository, is that ok? It's a lot of 
> question
> I'm sorry, but I'm not familiar with ASF infrastructure.

No, the hooks directory won't be needed. However, I'm not as 
knowledgeable as you might think, and would suggest you just zip up the 
lot, including hooks directory, just to be safe, unless someone else 
more knowledgeable tells you otherwise.

Regards, Upayavira

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [IVY] setup of infrastructure

[Xavier Hanin <xa...@gmail.com>]

On 11/1/06, Upayavira <uv...@odoko.co.uk> wrote:
>
> Xavier Hanin wrote:
> > On 11/1/06, Brett Porter <br...@gmail.com> wrote:
> >>
> >> On 31/10/06, Xavier Hanin <xa...@gmail.com> wrote:
> >> > > Does Ivy want to import history, or just the latest code?
> >> >
> >> >
> >> > An history import would be nice, but isn't there a problem with legal
> >> > issues, since old code was not under Apache License? And maybe the
> >> easier is
> >> > just to import latest code (well, I should release a new version next
> >> week -
> >> > maybe the last pre apache version, so it may be a good time to import
> >> just
> >> > after the release). What do other think?
> >>
> >> If it were me, I'd rather import the history than having to maintain
> >> it myself. There are no legal issues (BSD is compatible with the
> >> Apache License).
> >
> >
> > Thanks for your advice Brett. I'll go with history import if it's not
> too
> > complex to import into apache infrastructure. Can someone tell me what
> you
> > expect from our svn repository to do the import?
>
> If you can block all commit access to the repository, then a simple zip
> should do the job, If I understand correctly.


I can block access to the repository. So the only thing is to zip the
directory on my svn server containing the db directory, is that it? This
means that the hook directory will be part of the zip, I currently have a
hook for sending mail on commit, but I think there's already something like
this on apache usual svn install, no? So maybe the db directory is enough?
We use a filesystem based svn repository, is that ok? It's a lot of question
I'm sorry, but I'm not familiar with ASF infrastructure.

- Xavier

Regards, Upayavira
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>

Re: [IVY] setup of infrastructure

[Upayavira <uv...@odoko.co.uk>]

Xavier Hanin wrote:
> On 11/1/06, Brett Porter <br...@gmail.com> wrote:
>>
>> On 31/10/06, Xavier Hanin <xa...@gmail.com> wrote:
>> > > Does Ivy want to import history, or just the latest code?
>> >
>> >
>> > An history import would be nice, but isn't there a problem with legal
>> > issues, since old code was not under Apache License? And maybe the
>> easier is
>> > just to import latest code (well, I should release a new version next
>> week -
>> > maybe the last pre apache version, so it may be a good time to import
>> just
>> > after the release). What do other think?
>>
>> If it were me, I'd rather import the history than having to maintain
>> it myself. There are no legal issues (BSD is compatible with the
>> Apache License).
> 
> 
> Thanks for your advice Brett. I'll go with history import if it's not too
> complex to import into apache infrastructure. Can someone tell me what you
> expect from our svn repository to do the import?

If you can block all commit access to the repository, then a simple zip 
should do the job, If I understand correctly.

Regards, Upayavira

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org

Re: [IVY] setup of infrastructure

[Xavier Hanin <xa...@gmail.com>]

On 11/1/06, Brett Porter <br...@gmail.com> wrote:
>
> On 31/10/06, Xavier Hanin <xa...@gmail.com> wrote:
> > > Does Ivy want to import history, or just the latest code?
> >
> >
> > An history import would be nice, but isn't there a problem with legal
> > issues, since old code was not under Apache License? And maybe the
> easier is
> > just to import latest code (well, I should release a new version next
> week -
> > maybe the last pre apache version, so it may be a good time to import
> just
> > after the release). What do other think?
>
> If it were me, I'd rather import the history than having to maintain
> it myself. There are no legal issues (BSD is compatible with the
> Apache License).


Thanks for your advice Brett. I'll go with history import if it's not too
complex to import into apache infrastructure. Can someone tell me what you
expect from our svn repository to do the import?

Xavier

Cheers,
> Brett
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>