Attendees:

Regrets

Agenda

  1. Administrivia
    1. August meeting?
    2. Reminder: new #schema slack channel
  2. Vote: eduPersonDisplayPronouns / eduPerson v4.4.0 (See GitHub PR)
    1. Old open PRs
  3. Subcommittee status
    1. voPerson - 2.0 ftw!
  4. AOB

Notes

  1. Administrivia
    1. August meeting?
      1. meeting attendees ok with an August call; will determine based on how many responses we get to votes, etc on email
    2. Reminder: new #schema slack channel
    3. SCHAC 1.6.0 posted on the wiki and associated LDAP, LDIF files updated; Heather to add a landing page (e.g., refeds.org/schac)
  2. Vote: eduPersonDisplayPronouns / eduPerson v4.4.0 (See GitHub PR) (need at least 5 board members (quorum) on the call, and consensus of all those board members; see ToR)
    1. Old open PRs
      1. KEITH D HAZELTON to review https://github.com/REFEDS/eduperson/pull/1
        1. So .schema is an OpenLDAP extension. They make them available for OpenLDAP admins to include in their config files. See https://www.openldap.org/doc/admin26/guide.html#Schema%20Specification; I'll propose text for the PR response.
      2. Alan Buxey to review https://github.com/REFEDS/eduperson/pull/15 and 11 (duplicate)
    2. request for new LDAP/LDIF files for eduPerson - volunteers?
      1. Heather will draft, Terry will test
    3. updated all version numbers to semantic versions - ok, or revert to the original numbering scheme until 4.4.0?
      1. Suggest instead do a transition of having both the date and the semantic version until version 5, then having a clean break
      2. mixed feelings (but no strong ones) regarding using semantic versioning; it's a useful signal, but often not applied well or consistently
  3. Subcommittee status
    1. voPerson - 2.0 ftw!
    2. DNS transfer to GEANT in progress
  4. AOB
  • No labels

1 Comment

  1. Note, that while the .schema files are an OpenLDAP-specific file, so are the LDIF that is there to modify cn=schema,cn=config (olcAttributeTypes and olcObjectClasses are specific to OpenLDAP, on Oracle/Sun directories it's attributetypes and objectClasses on cn=schema) ... might be wise to produce just the RFC4512 formatted (section 4.1) attribute/objectclass definitions and the others are possibly generated from that? 

    IMO it's probably better to import the eduPerson.schema file so that it can be updated as a whole too?