Versions Compared

Key

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

Shibboleth Developer's Meeting, 2019-04-19

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 2019-05-03. 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 see ZoomGU for access info.


AGENDA

  • Ian Young: We have moved the Jenkins site jobs to use Slack channels for notifications. Is this working? Do we want to either move notifications for the other jobs to Slack as well, or combine Slack and e-mail for them?
  • Rod Widdowson : Who remembers 
    Jira Legacy
    serverShibboleth JIRA
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyIDP-691
    ?
  • Ian Young : Javapocalypse and in particular the last couple of comments on 
    Jira Legacy
    serverShibboleth JIRA
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyJPAR-129
  • 3.4.4 schedule

Attendees:


Brent

  • Work on low-hanging fruit issues targeted to 4.0: Interface promotion, metadata filter and resolver enhancements.


Daniel


Henri

  • On holiday last week
  • OIDC metadata work will be continued next week with Phil

Ian


Marvin


Phil

...

  • IAM Online - sounds like people are starting to wake up to the Java mess
  • Confluence patching
  • Jira Legacy
    serverShibboleth JIRA
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyIDP-1434

    • Progressing slowly of late, but just about ready to get back into the meat.
    • Follow on work includes some tire-kicking on use of filter engine in the "reverse" SP mode for inbound rules
  • Jira Legacy
    serverShibboleth JIRA
    serverId180d847f-bce4-36b2-9964-771bff586829
    keyJSPT-87
    • Proposing we address "vault" services like AWS or Hashicorp with scripting glue for now

Tom

  • Likely un-fixable local Windows VM network issues ...
    • Azure ?
    • Re-work Jenkins multi jobs to run one-at-a-time (by passing slave/node param to some sort of trigger) ?

Other