The contents of this e-mail are intended for the named addressee only. It contains information that may be confidential. Unless you are the named addressee or an authorized designee, you may not copy or use it, or disclose it to anyone else. If you received it in error please notify us immediately and then destroy it.
From: equinox-dev-bounces@xxxxxxxxxxx [mailto:equinox-dev-bounces@xxxxxxxxxxx] On
Behalf Of Peter Kriens
Sent: Monday, April 21, 2008 3:20 AM
To: Equinox development mailing list
Subject: Re: [equinox-dev] Equinox IP log
Is it possible to get all the Orbit bundles in the OBR repository?
Kind regards,
Peter Kriens
On 19 apr 2008, at 11:53, DJ Houghton wrote:
> John, looks good!
>
> Here is the discussion on the Orbit mailing list about hiding
the
> email
> addresses:
>
http://dev.eclipse.org/mhonarc/lists/orbit-dev/msg00732.html
>
> In Orbit everything is a third-party bundle. When people commit a
new
> bundle to the repository, they are required to create an IP log
XML
> file:
> http://wiki.eclipse.org/Orbit_IP_Log
> and then during the build we parse this information and build a
web
> page
> for that build. For example:
>
>
http://download.eclipse.org/tools/orbit/downloads/drops/I20080411183252/iplog-I20080411183252.html
>
> If you want to use this story going forward with the Equinox
> project, I can
> work with you to get it going.
>
>
>
>
>
>
>
"Jeff McAffer"
>
<jeff@xxxxxxxxx>
>
Sent
>
by:
To
>
equinox-dev-bounc
"'Equinox development mailing
>
es@xxxxxxxxxxx
list'" <equinox-dev@xxxxxxxxxxx>
>
cc
>
>
04/18/2008
10:49
> Subject
>
PM
RE: [equinox-dev] Equinox IP log
>
>
>
Please respond to
>
Equinox
>
development
>
mailing list
> <equinox-dev@ecli
>
pse.org>
>
>
>
>
>
>
> Thanks John, this is a good start. I wonder if there is
something
> we can
> harvest from the Orbit IP log structure. DJ? Thoughts?
>
> It would be generally useful to have the CQ numbers associated
with
> the
> third party code.
>
> One important not is that I believe we have a policy about
> protecting email
> addresses. We went through this in Orbit where the decision
was to
> not
> include them. DJ, do you recall anything about this?
Either way,
> unless
> there is a compelling reason to include them they should be
removed.
>
> Jeff
>
> From: equinox-dev-bounces@xxxxxxxxxxx
> [mailto:equinox-dev-bounces@xxxxxxxxxxx] On Behalf Of John
Arthorne
> Sent: Friday, April 18, 2008 4:00 PM
> To: equinox-dev@xxxxxxxxxxx
> Subject: [equinox-dev] Equinox IP log
>
>
> FYI, I have committed an initial Equinox IP log:
>
> http://www.eclipse.org/equinox/documents/iplogs/EquinoxIPlog.html
>
> We had initially started with a separate IP log per component,
but
> as I
> started to update them I found it painful to track the committer
lists
> separately so I combined them. Also there is only one IP log
URL
> that can
> be linked from http://eclipse.org/projects/listofprojects.php.
The
> third
> party software list is not yet complete, and I have not
processed
> all the
> p2 contributions since p2 graduation. Can all committers
quickly
> scan the
> committer list and ensure they are listed, and their login,
> organization,
> and email addresses are correct? I believe we only need to record
> committers who contributed to the 3.4 release - this excludes
people
> who
> committed only to the incubator project, and those who only
> committed prior
> to the 3.3 release (someone please correct me if this is wrong).
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
>
>
> _______________________________________________
> equinox-dev mailing list
> equinox-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/equinox-dev
_______________________________________________
equinox-dev mailing list
equinox-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/equinox-dev