Difference between revisions of "Architecture Council/Meetings/April 20 2017"

Latest revision as of 10:11, 25 April 2017

Meeting Title:	Architecture Council Monthly Meeting
Date & Time:	Thursday April 20, 2017 at 1100 Ottawa HTML | iCal

Attendees

• In attendance: Mikael Barbero, Wayne Beaton, Marcel Bruch, Maximilian Kögel, Alex Kurtakov, Dani Megert, Ed Merks, Tracy Miranda, Martin O, Denis Roy, Doug Schaefer, Michael Scharf, Lars Vogel

• Regrets: Jay Jay Billings, Mickael Istria, Martin Lippert, Alexander Nyßen, Torkild Resheim, Matthias Sohn, Eike Stepper, Krum Tsvetkov,

• No-Show: Carl Anderson, Max Andersen, Chris Aniszczyk, John Arthorne, Nick Boldt, Cédric Brun, Ian Bull, Benjamin Cabé, Christian Campo, Linda Chan, Naci Dai, Sebastien Gerard, Neil Hauge, Jonas Helming, Jim Hughes, Kenn Hussey, Tyler Jewell, Markus Knauer, Konstantin Kommissarchik, Benoit Langlois, Mike Milinkovich, Adrian Mos, Steffen Pingel, Pascal Rapicault, Tom Schindl, Julien Vermillard, Gunnar Wagenknecht, Tom Watson, Mike Wilson

#PMC_Rep_Attendees see also below.

Agenda / Notes

• Last meeting: Architecture Council/Meetings/March 9 2017 -- open actions see #Action_Items

Welcome Tracy Miranda

• Been with Eclipse for quite long, Eclipse CDT initially, but also Eclipse Sience and IoT recently
  • Based just outside London - Kichwa Coders

Wayne: Updating Legal Docs

• Started revising the Guide to Legal Docs with the IP Advisory Committee
• Thinking about an alternative for file headers, for project who don't want to put company names there
  • Meant as an alternative, not a replacement
• Generalizing some docs to be less specific for Eclipse Plugins (example: about.html -> notices file)
• Revising the SUA - Eclipse is the only OSS Community that has such a thing, is it still useful?
  • Currently it is very technology specific for Platform (Plugins, Features) - When generalizing it, found that there is not too much it actually says when there's nested licenses in the downloads anyways
• Been investigating SPDX for tracking licenses

Marcel: Neon.3a - How to get the process rolling

• Neon.3 issues were discovered on March 30, why is the problem still out there?
• The fix seems to be in progress (again) now - are we good or is there still work to be done?
• AC and Project Leads should probably be more active to avoid broken software - today, we get 2-3 bug reports daily
  • Ed: Packages contain a subset of things, and the packages didn't show the problem - it only occurred after installing add-ons - so it wasn't that screamingly obvious
    • JEE confimed - no errorlog entries
    • Martin: Reported bug 514257 against Oxygen M6 committers package, but haven't seen the issue in Neon packages
  • To-date, we are unsure whether anything we try today would actually fix the issue!
  • Ed: We don't know exactly what people installed / updated; Unmodified Neon.3 packages are probably good
    • Marcel has some reproducable cases from people who tried to install add-ons. Error reporting could include the list of installed bundles (and probably install history) to error reports, would that help?
    • Martin used similar collected logs in the past:
  • Unsure whether Errorlog entries really print an unresolvable state, or just that the resolver didn't come up with a resolution; having fewer choices of bundles to wire against certainly simplifies the problem; adding constraints probably makes it harder.
    • Either way, it could still show up somewhere else if people install add-ons
    • Ideally, the resolver would wire things correctly - or assert that it has an unresolvable problem.
    • If we could get back to the state we had in Neon.2, that would perhaps be good enough for Neon (hoping that the Oxygen resolver really improves things)
    • Which project actually brought in the new httpcomponents?
      • Alex: Docker tooling updated docker client, which relied on the new version. Does p2 eagerly install things from the release train repo?
      • An obvious solution would be reverting to the Neon.2 version of docker, to avoid getting the additional httpcomponents into the release train repo.
• SUMMARY: AC recommends getting back to the Neon.2 state of httpcomponents, then get input from Fred Bricon.
  • Document a couple scenarios for testing (Ed: EGit has a couple similar wiring issues related to logging)
  • Will discuss next steps on the mailing list.
  • Would it help removing Neon.3 from the composite? - Stop-shipping is a very drastic measure, and would need to be decided by the Planning Council
  • In the future, we should be more concerned about quality before shipping things

Infrastructure Updates

• Infrastructure: Recent improvements + Transparent mirroring - haven't seen things get worse, but haven't seen too much improvements either ... Bugzilla was again out-of-sync just yesterday
  • Issue had also been discussed at the Board level
  • Ed also had download / update site problems yesterday (Wednesday)
  • Still more resources being put on the problem but may take longer to get really stable
  • Denis - overview of recent improvements:
    • One of the biggest pain point on Build was the proxy on build servers; this was finally removed 2 weeks ago
    • Yesterday, new storage was provisioned for download.eclipse.org - 4TB up to 22TB and much faster
    • Transparent mirroring was enabled - forcing some systems who didn't use mirrors to use them now; this SIGNIFICANTLY reduced bandwidth, so after years we finally have some bandwidth to spare!! - AI Ed please forward details on download timeouts (seemed like a transient thing for about an hour or so)
      • OSUOSL monitors eclipse.org for performance and availability, will keep an eye on this
      • Anything above 2MB can selectively redirect to mirrors now - anything gzipped is a candidate, including p2 metadata now!!
        • If a large xml.xz is redirected to a slow mirror, that could cause timeouts?
          • Mirrors are polled for availability every 2 hours - has to have 100% success for 2 weeks before being added to redirect pool
        • Mirrors could now fake metadata to serve malicious jars ? - Metadata (artifacts.jar, content.jar) is not digitally signed; but artifacts are digitally signed, and user has to accept the Cert or agree to installing unsigned things.

General Topics

• Board minutes were approved yesterday, will be published soon

PMC Rep Attendees

All AC Members are invited.

• PMC Reps please confirm attendance or list your delegate below. Every PMC is required to name a primary and backup delegate, and to ensure that one delegate attends the meeting.

Next Meeting

• Architecture Council/Meetings/May 11 2017