Hey folks. With Jody's help, I've joined the list.
A piece of my response got clipped (I think that I "undid" it myself
by accident).
With regard to the "about" files, I suggest that we engage the IP
Team on it. Let's just submit the Initial Contribution and ask them
as part of that process how the about files need to change. The key
part is to just get that Initial Contribution in. All the other
goodness will follow from that.
Wayne
-------- Original Message
--------
Wayne has responded (but was unable to get through to the
list so I am forwarding):
Subject: Re: Create the uDig project
Hi Jody.
I'm not a member of the mailing list and my attempts at
guessing the sign up URL failed; you'll can copy my
response to the list if you'd like.
My responses in line.
Wayne
On 03/17/2013 07:31 PM, Jody Garnett wrote:
Morning Wayne, digging up an old email as we
seem to have gotten stuck
As I understand it the team is now filling in
all the paper work and should gradually get access
to LocationTech facilities. We know we are the
first team in and expect a rough ride :-)
Sorry about that. We've been doing the Eclipse thing for
a while, so we have that down to a fine art. Much of our
infrastructure has made assumptions that everything is
Eclipse, but we're working hard to make sure that
everything is adapted for LocationTech. Sorry about the
PolarSys/OPEES mixup (this is related some other work
that we're doing in parallel). We appreciate your
patience.
Just going to focus on this last task for a
moment Wayne, and ensure we get organised on the
email list.
3) When the project gets created,
the webmaster will provision the necessary
resources. Before anything can be checked
in, the project's code is going to have to
be reviewed by the IP team. We can start
that process now so that we can hit the
ground running when the provisioning
happens.
To review the initial contribution code, the
IP team needs it zipped up in an archive.
The archive should contain project code only
(i.e. the code that you intend to maintain
at locationtech.org
with no nested archives).
Third party libraries used by the project
need to be captured as well. Again, we can
start this in parallel. Do you have a
listing of third-party libraries required by
uDig? (note that we don't consider eclipse.org
code to be third-party in this context).
We'll need to have the names and versions of
each library (we do IP due diligence on a
version-by-version basis), along with
licenses, source, and links to the
providers. I can help you hunt this
information down.
So we can zip up our code at any point in
time, indeed there is a "ZIP" button in github
which can be used right now.
2. Click on "Zip" to download
Right. Then, go to the Developer portal ( http://portal.eclipse.org),
click on your project, and select "[contribution] of
code to be maintained at eclipse.org" and follow
the steps to create an "Initial contribution". This will
create a record in our "IPZilla" (which is a modified
version of Bugzilla); you will be prompted to attach the
actual contribution to the record via email.
By the same token the list of
third-party-libraries is captured:
Let's start by having you send me the output from the
dependency computation. I'll review the dependencies and
break them down into different categories and step you
through it from there. I think that that will be more
useful than any abstract discussion.
Let's engage the IP Team on this one
How can we best engage the IP team on this
one? Do we have a contact name, use the location
tech email list, raise an issue pointing to the
above instructions?
Subject:
Re: Create the uDig project |
From:
The Eclipse Foundation <emo@xxxxxxxxxxx> |
Date:
03/18/2013 10:12 PM |
Hi Jody.
I'm not a member of the mailing list; you'll have to
copy my response there.
My responses in line.
Wayne
On 03/17/2013 07:31 PM, Jody Garnett wrote:
Morning Wayne, digging up an old email as we
seem to have gotten stuck
As I understand it the team is now filling in
all the paper work and should gradually get
access to LocationTech facilities. We know we
are the first team in and expect a rough ride
:-)
Sorry about that. We've been doing the Eclipse thing
for a while, so we have that down to a fine art. Much
of our infrastructure has made assumptions that
everything is Eclipse, but we're working hard to make
sure that everything is adapted for LocationTech.
Sorry about the PolarSys/OPEES mixup (this is related
some other work that we're doing in parallel). We
appreciate your patience.
Just going to focus on this last task for a
moment Wayne, and ensure we get organised on the
email list.
3) When the project gets created,
the webmaster will provision the necessary
resources. Before anything can be checked
in, the project's code is going to have to
be reviewed by the IP team. We can start
that process now so that we can hit the
ground running when the provisioning
happens.
To review the initial contribution code,
the IP team needs it zipped up in an
archive. The archive should contain
project code only (i.e. the code that you
intend to maintain at locationtech.org
with no nested archives).
Third party libraries used by the project
need to be captured as well. Again, we can
start this in parallel. Do you have a
listing of third-party libraries required
by uDig? (note that we don't consider eclipse.org
code to be third-party in this context).
We'll need to have the names and versions
of each library (we do IP due diligence on
a version-by-version basis), along with
licenses, source, and links to the
providers. I can help you hunt this
information down.
So we can zip up our code at any point in
time, indeed there is a "ZIP" button in github
which can be used right now.
2. Click on "Zip" to download
Right. Then, go to the Developer portal ( http://portal.eclipse.org),
click on your project, and select "[contribution] of
code to be maintained at eclipse.org" and
follow the steps to create an "Initial contribution".
This will create a record in our "IPZilla" (which is a
modified version of Bugzilla); you will be prompted to
attach the actual contribution to the record via
email.
By the same token the list of
third-party-libraries is captured:
Let's start by having you send me the output from the
dependency computation. I'll review the dependencies
and break them down into different categories and step
you through it from there. I think that that will be
more useful than any abstract discussion.
Let's engage the IP Team on this one. Submit the
initial contribution; we can ask for their assistance
during the due diligence process.
How can we best engage the IP team on this
one? Do we have a contact name, use the
location tech email list, raise an issue
pointing to the above instructions?
|