Re: [cross-project-issues-dev] Simultaneous Release participation and the Eclipse IDE packages

[Torkild U. Resheim]

Hi Jesse,

To paraphrase Wayne, in short: the Eclipse Foundation has a responsibility in 
making sure that the community can trust every bundle they consume from the 
simultaneous release.

What we currently do is to sign these bundles with a certificate from the 
Eclipse Foundation. This is a quality mark: Implicitly stating that we have a 
complete history of every commit to every repository producing these bundles; A 
pretty good QA process for these commits, and a very good idea of who these 
committers and contributors are; A rigorous process to ensure safe 
licensing/patent use and provenance of third party bundles. It's pretty much as 
good it as it can get in open source.

I think I understand from your message, is that you believe this signing is 
worthless and that no consumer should require a signed artefact. If I'm right, 
how do you propose we otherwise could do this better? What is impractical  with 
having to deal with signed bundles?

Best regards,
Torkild


> 22. jan. 2021 kl. 20:33 skrev Jesse McConnell :
> 
> 
> All bundles must be signed using the EF's certificate. Obvious exceptions 
> will be made in cases where signing is impossible.
> 
> We will be applying this standard to the next release and for every release 
> thereafter.
> 
> The means by which the simultaneous release participation rules are changed 
> is to engage with the Eclipse Planning Council via your Eclipse Planning 
> Council representative.
> 
> So if I understand correctly everything from above can be changed via the 
> Planning Council. I'm especially interested in the signing as it's becoming 
> harder and harder to keep up with external ecosystem due to way faster pace 
> and being able to use different means of signing as discussed at 
> https://www.eclipse.org/lists/p2-dev/msg05910.html becomes critical. But 
> let's keep this discussion for the next Planning Council meeting.
> 
> Personally, I think the entire concept of this sort of signing should be 
> reviewed.  If the editor wants to release signed artifacts then the onus 
> should be on the editor to trust and sign everything it pushes out with the 
> EF cert, it shouldn't export requirements to projects it consumes to 
> themselves have things signed by the EF cert. That whole service that the EF 
> provides for jar files to show up in some directory and signed artifacts 
> popping out in another is hokey and combined with the concept of p2 
> repositories is a big reason Jetty left the release train.
> 
> cheers,
> Jesse
> 
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



signature.asc
Description: Message signed with OpenPGP
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Bugzilla down

[Torkild U. Resheim]

Yes, it came up working again some time in the last ten minutes. Now we can get 
back to selecting the program :)

Best regards,
Torkild

> 22. jul. 2019 kl. 15:23 skrev Denis Roy :
> 
> Signert PGP del
> I wasn't aware. I just checked, and it's working now.
> 
> Denis
> 
> On 2019-07-22 9:13 a.m., Torkild U. Resheim wrote:
>> https://eclipsecon.org
>>  is still down though
>> 
>> Torkild
>> 
>> 
>>> 22. jul. 2019 kl. 12:51 skrev Denis Roy 
>>> :
>>> 
>>> Our primary database server encountered a kernel bug and crashed. We've 
>>> failed over to a secondary db and will look into the bug before resyncing 
>>> and restoring the primary.
>>> 
>>> Apologies for the service interruption. Everything should be working as 
>>> expected at this time.
>>> 
>>> 
>>> 
>>> Denis
>>> 
>>> 
>>> 
>>> On 2019-07-22 5:41 a.m., Laurent Goubet wrote:
>>> 
>>>> Hi,
>>>> 
>>>> We cannot connect to the bugzilla at
>>>> https://bugs.eclipse.org/bugs/ (long waiting time ultimately leading to 
>>>> 404), trying to access https://www.eclipse.org/
>>>>  ends up in error 502, and we're getting errors from builds looking like 
>>>> some of the connections to download.eclipse.org get dropped as well. 
>>>> Anyone else encountering this issue?
>>>> 
>>>> Regards,
>>>> 
>>>> --
>>>> Laurent Goubet
>>>> CONSULTANT
>>>> +33 2 51 13 51 42
>>>> 
>>>> 
>>>> 7 Boulevard Ampère - Carquefou - France
>>>> obeo.fr | twitter | linkedin
>>>> 
>>>> 
>>>> 
>>>> ___
>>>> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>> --
>>> Denis Roy
>>> Director, IT Services | Eclipse Foundation, Inc.
>>> Eclipse Foundation: The Platform for Open Innovation and Collaboration
>>> Twitter: @droy_eclipse
>>> ___
>>> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>> 
>> 
>> ___
>> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> 
> 



signature.asc
Description: Message signed with OpenPGP
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Bugzilla down

[Torkild U. Resheim]

https://eclipsecon.org is still down though

Torkild

> 22. jul. 2019 kl. 12:51 skrev Denis Roy :
> 
> Our primary database server encountered a kernel bug and crashed. We've 
> failed over to a secondary db and will look into the bug before resyncing and 
> restoring the primary.
> 
> Apologies for the service interruption. Everything should be working as 
> expected at this time.
> 
> 
> 
> Denis
> 
> 
> 
> On 2019-07-22 5:41 a.m., Laurent Goubet wrote:
>> Hi,
>> 
>> We cannot connect to the bugzilla at https://bugs.eclipse.org/bugs/ (long 
>> waiting time ultimately leading to 404), trying to access 
>> https://www.eclipse.org/ ends up in error 502, and we're getting errors from 
>> builds looking like some of the connections to download.eclipse.org get 
>> dropped as well. Anyone else encountering this issue?
>> 
>> Regards,
>> 
>> --
>> Laurent Goubet
>> CONSULTANT
>> +33 2 51 13 51 42
>> 
>> 
>> 7 Boulevard Ampère - Carquefou - France
>> obeo.fr | twitter | linkedin
>> 
>> 
>> 
>> ___
>> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
> --
> Denis Roy
> Director, IT Services | Eclipse Foundation, Inc.
> Eclipse Foundation: The Platform for Open Innovation and Collaboration
> Twitter: @droy_eclipse
> ___
> 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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



signature.asc
Description: Message signed with OpenPGP
___
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://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Can DTP join EGit in Oxygen.2 respin?

[Torkild U. Resheim]

Yes, I think that’s a good idea Stephan. One could possibly set up the build to 
fail when using deprecated API, in order to get an early warning. I’m not aware 
of a way of making Tycho do so though. I guess having a no-warnings policy and 
set the compiler up to fail on warnings is an option.

Best regards,
Torkild

> 16. des. 2017 kl. 17:54 skrev Stephan Herrmann :
> 
> Another option could be: even "inactive" projects could be required,
> to perform builds against each SimRel milestone, even when contributing
> a previous version. This should ensure that code still works (compiles
> and passes tests) against updated dependencies.
> 
> I don't think this should be much of a burden on "maintainers".
> 
> Stephan



signature.asc
Description: Message signed with OpenPGP
___
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] Eclipse release update sites with versions?

[Torkild U. Resheim]

In that case, maybe it would be a good idea to have 
http://download.eclipse.org/releases/latest 
?

Best regards,
Torkild

> 15. jun. 2017 kl. 15.00 skrev Mickael Istria :
> 
> 
> 
> On Thu, Jun 15, 2017 at 2:51 PM, Lars Vogel  > wrote:
> But for users like me, who cannot remember more than two release
> names
> 
> Isn't it a good thing to have users only remembering the last release name 
> and only able to reference the last release? ;)
> Anyway, I think you'd rather open an enhancement request for that. 
> ___
> 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 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] How to provide HDPI icons in your plug-in

[Torkild U. Resheim]

+1

Having a shared repo with SVG icons and tools to generate bitmaps would be 
awesome! I’ve been adjusting Eclipse Platform to my needs for generating @2x 
icons and it’s a bit hard as it is. I can only imagine how long it will take 
for all projects to generate @2x PNGs without such encouragement.

Best regards,
Torkild
-- 
Torkild Ulvøy Resheim
Consultant / Eclipse Committer / Senior Software Developer
Itema AS - http://itema.no

> 21. sep. 2016 kl. 14.09 skrev Antoine THOMAS :
> 
> Question: would it make sense to create a project for a set of vector icons 
> like Font Awesome or Fondation Icon Fonts, that any project/package/plugin 
> could use, and of course, improve?
> 
> It could of course include accessibility and general purpose icons. It would 
> be a good companion to the Polarsys Font.
> 
> Also, if the icons are done by a project team, with style guidelines, it 
> would help to have consistent icons, in Eclipse, in general.
> 
> 
> 
> __
> Antoine THOMAS aka ttoine
> Product Manager
> Eclipse Foundation
> antoine.tho...@eclipse.org
> +33663137906
> @ttoine
> 
> On 21 September 2016 at 10:58, Lars Vogel  wrote:
> Hi,
> 
> the buildship project contact me about how to provide HDPI icons for
> there project. As I assume many projects have this question, I post
> here the related info.
> 
> The general support in Platform is explained here:
> https://www.eclipse.org/eclipse/news/4.6/platform_isv.php#high-dpi-icons
> 
> Platform has also a Maven based command line tool to renderer png in
> different sizes from svg images. See
> http://www.vogella.com/tutorials/Eclipse4Notes/article.html#providing_hdpi_icons
> for some info for that.
> 
> Best regards, Lars
> 
> --
> Eclipse Platform UI and e4 project co-lead
> CEO vogella GmbH
> 
> Haindaalwisch 17a, 22395 Hamburg
> Amtsgericht Hamburg: HRB 127058
> Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
> USt-IdNr.: DE284122352
> Fax (040) 5247 6322, Email: lars.vo...@vogella.com, Web: 
> http://www.vogella.com
> ___
> 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 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 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