Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Planning Council/2021-11-03

< Planning Council
Revision as of 14:16, 4 November 2021 by Wayne.beaton.eclipse-foundation.org (Talk | contribs) (Related Technologies Discussion)

Notes

Membership

Welcome Leif Geiger to the planning council meeting.

Johannes Matheis (representative from Vector) has joined the council and is expected at the next meeting

Actions from last meeting

  • SimRel improvements list distributed to IDE WG Steering Committee
  • EclipseCon Community Day presentation completed and delivered
  • 2022-03/06 schedule created, voted on and approved
  • JarSigning replacement proposal circulated on mailing list

Related Technologies Discussion

  • Wayne provided an overview based on his email
  • The Marketplace client is an Eclipse Project
  • The Marketplace server is software run and maintained by the EF
  • There is a new Marketplace client + server in development
  • The Marketplace falls under the Planning Council, from the IDE WG Charter "Setting, evolving, and enforcing policies and procedures governing supporting products (e.g., marketplaces, statistics gathering and data collection services, ...);"
  • Decided that the Planning Council should request the Steering Committee spend some specific amount of money to in the short term address a key problem. e.g. "pay 30 day contract to do X"
  • A high priority item would be to clean up the marketplace of uninstallable content, see https://www.eclipse.org/setups/marketplace/?style=all
  • Action: Martin will provide a first draft
  • Goal: Provide this to the IDE WG Steering Committee by their next meeting (16 Nov)

PGP Signing

  • RedHat rpm team did a review of PGP signing plan
  • The earliest that PGP only signed content can be delivered is after a full release with the Eclipse Platform / p2 having it implemented to ensure users who are upgrading are not presented with an unsigned warning. This means that (for e.g.) if the Eclipse Platform has a complete implementation in 2021-12 (4.22) the earliest PGP only signed content can be delivered is 2022-03.

CVEs / vulnerabilities

Back to the top