[cross-project-issues-dev] Added Mylyn to Commons Build Share

[Kunz Daniel (CR/AEY1)]

Hello @all,
in the technology.app4mc project we are using Mylyn Wikitext standalone for 
generating out our help.
As we are currently migrating our codebase and build jobs, Mikael Barbero added 
for us the relevant jar files under 
http://build.eclipse.org/common/mylyn-wikitext/2.9.0.v20160513-1433/, so they 
are available at the Eclipse Build Services for usage.

Best Regards
Daniel Kunz




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] New UUID in Eclipse Platform

[Ian Skerrett]

Fyi, I have just published a blog post about removing the UUID.

 

https://ianskerrett.wordpress.com/2016/06/14/uuid-removal-from-neon/

 

Thank you again for everyone’s feedback. 

 

 

 

From: cross-project-issues-dev-boun...@eclipse.org 
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Markus Knauer
Sent: Sunday, June 5, 2016 11:34 AM
To: Cross project issues 
Subject: Re: [cross-project-issues-dev] New UUID in Eclipse Platform

 

Thank you, Ian, that decision is very much appreciated!

Regards,

Markus

 

On 5 June 2016 at 15:48, Ian Skerrett  > wrote:

Markus and everyone else,

 

I hear you and agree we need to remove the UUID in Neon. I will put a statement 
to this effect on the bug you opened. It is obvious there is a lot more 
discussion needed around this issue.

 

My apologies to Pascal and the Eclipse Platform project for requesting the 
change and for requiring a re-spin of Neon.

 

Ian

 

From: cross-project-issues-dev-boun...@eclipse.org 
  
[mailto:cross-project-issues-dev-boun...@eclipse.org] On Behalf Of Markus Knauer
Sent: Sunday, June 5, 2016 7:41 AM
To: Cross project issues  >
Subject: Re: [cross-project-issues-dev] New UUID in Eclipse Platform

 

Ian,

you are right in your assumption that all this won't change my opinion in any 
way, in fact, the opposite is true.

The implementation of AERI (the error reporter) and the former EPP Usage Data 
Collector are both opt-in implementations. Both have been carefully designed to 
be as transparent as possible, no user is forced to send any data, there is no 
hidden feature or side-channel, the data is anonymised, and the mail address 
that you were referring to in your response is only optional. AERI has been 
implemented in an open way as it is appropriate for an Open Source community, 
integrated early enough in the release cycle, and based on feedback by and with 
review from the community.

This is clearly a major difference to the way the Eclipse Foundation introduced 
the implementation of the UUID and its use in Platform, p2, MPC, and as a last 
minute change in AERI. (I just want to point out that I am thankful that the 
AERI team pushed on making the UUID introduction public, otherwise some doubts 
are admissible that it would have been communicated at all.)

 

Yes, you are right, I could live with it if it was an opt-in instead of this 
hidden opt-out. I called it a 'theoretical' opt-out for a number of reasons:

- There is no user interface within Eclipse, no preference page it's just 
nothing. A void.

- The user isn't told about the existence or about the creation of the UUID.

- The user needs to leave the program ("Eclipse") that he or she is using to 
edit an external file.

- And it is an after-the-fact thing. Under normal circumstances the file can 
only be edited after its creation by Eclipse. Kind of a short-circuit.

Rethinking, no, that is not even something that can be called opt-out.

 

The introduction of such IDs is often justified by possible future 
improvements, but so far I have not seen any plan what to learn from this 
additional information. What is the concrete question that we hope to answer by 
introducing the UUID? If most (closed source) organisations are moving into the 
data-driven decision direction, this is no reason that the (open source) 
Eclipse organisation should move into the same direction. I think we can do 
better!

 

In Europe (I cannot speak for other areas), there are regulations in place 
regarding e.g. cookies ('devices') and IMO this per-user UUID is no different. 
The European Legislation is very clear about the usage of those IDs - you may 
read (24), (25) of [1]. I have serious doubts that the usage of the UUID which 
is bound to a single user is in accordance with European law, and I guess that 
there is no question that it has to be an opt-in. I hope that Eclipse Legal has 
been involved in its development, and that it did a thorough background check, 
but so far I haven't seen any indication that this has been done.

I strongly believe that this UUID is the worst thing that can happen in an Open 
Source community like Eclipse, and that the Eclipse Foundation looses a lot of 
trust and reputation with this.


Eclipse Neon cannot be released with the current implementations in Platform, 
p2, MPC, and AERI in Neon, there are too many open issues that need to be 
solved before introducing anything like that.

 

Markus




[1] http://eur-lex.europa.eu/legal-content/EN/LSU/?uri=CELEX:32002L0058





 

On 4 June 2016 at 17:11, Ian Skerrett  > wrote:

Markus

 

I think you have captured many of the key concerns so I would like to try to 
respond. I don’t 

Re: [cross-project-issues-dev] Loading issues with some of our websites

[Webmaster(Matt Ward)]

Hi Folks,

  the source of this mornings outage appears to be that our network
logging server fell down and this resulted in the web servers building
up log requests and eventually grinding to a near halt.  We've got the
log server back up, and are looking into our options to mitigate this in
future.

-Matt.
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Respin of SimRel Repository required

[David M Williams]

Extended team, 

I am beginning a re-spin of the Sim. Release repository. 

Two major changes: SOA-BPN2 modeler removed and Window Builder removed. 

The former removed because they didn't finish the normal release 
requirements. The later was removed because it has not been tested with 
the Neon candidate release. (It did recently, after RC4, get a build which 
"removed one line of code" which prevented it from running on Neon ... 
but, our goal is not for projects to "join at the last minute" but to be 
part of the train for many milestones so it can be adequately tested). 

It is my understanding both projects plan to "rejoin the train" in the 
September release. 

A minor change: Linux Tools found a major memory leak which would normally 
not be "respin worthy", but I told them if we had to respin for other 
reasons they could include a fix for that. 

The EPP packages will need to be rebuilt of course -- first because they 
always are if the repository changes, but more so this time because Window 
Builder was included in two EPP packages and of course will have to be 
removed from those packages. 

I will update this list once both steps are complete. 

Thanks, 




___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Loading issues with some of our websites

[Christopher Guindon]

Good morning everyone,

*Quick status update*:
We are experiencing some issues with a few of our websites this morning 
and we are currently working to rectify the issue.


Services that are currently affected:

 * marketplace.eclipse.org
 * wiki.eclipse.org
 * projects.eclipse.org

We will have an update once the websites are up and running again.

Thanks,
-Chris,

--
Christopher Guindon
Lead Web Developer
Eclipse Foundation
Twitter: @chrisguindon

EclipseCon NA 2016 
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To change your delivery options, retrieve your password, or unsubscribe from 
this list, visit
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev