Page Comparison

Versions Compared

Key

This line was added.
This line was removed.
Formatting was changed.

Shibboleth Developer's Meeting, 2020-06-05

Call Administrivia

09:00 Central US / 10:00 Eastern US / 15:00 UK / 17:00 FI

Calls are normally the 1st and 3rd Fridays of each month. Next call would be Friday 2020-06-19. Any reason to deviate from this?

60 to 90 minute call window.

Call Details

This week's call will use the Zoom system at GU, see ZoomGU for access info.

AGENDA

PKIX root behavior
Opening up master branches

Attendees:

Brent

Daniel

Henri

Ian

Thread safety is hard:
- Arises through
  Jira Legacy
  server Shibboleth JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key MDA-242
  ; full discussion there.
- A lot of things we say are @ThreadSafe really aren't, although they are mostly @ThreadSafeAfterInit and other things probably conspire to mean we're probably OK in practice. This makes me uncomfortable.
- It's not possible even in principle to make most things truly @ThreadSafe because of
  Jira Legacy
  server Shibboleth JIRA
  columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
  serverId 180d847f-bce4-36b2-9964-771bff586829
  key JSPT-97
  .
- We could fix that (and I think we should, see this commit) but that wouldn't address all the issues, just make it possible to do so for cases we care most about.
- Beyond that, I don't think really nailing this down is going to be felt to be worthwhile, but we might want to document some assumptions and change some annotations anyway.
Building from Docker containers: iay/shibboleth-build-docker seems to work

...

Documentation
Minor 4.1 work
Web site, moving community content into WEB wiki space
EC2 instance running PrivacyIdea
Would like to start steering "roadmap" content into Jira

Tom

Other