Attendees:
Regrets
Agenda
- Administrivia
- August meeting?
- Reminder: new #schema slack channel
- Vote: eduPersonDisplayPronouns / eduPerson v4.4.0 (See GitHub PR)
- Old open PRs
- Subcommittee status
- voPerson - 2.0 ftw!
- AOB
Notes
- Administrivia
- August meeting?
- meeting attendees ok with an August call; will determine based on how many responses we get to votes, etc on email
- Reminder: new #schema slack channel
- 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)
- 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)
- Old open PRs
- KEITH D HAZELTON to review https://github.com/REFEDS/eduperson/pull/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.
- Alan Buxey to review https://github.com/REFEDS/eduperson/pull/15 and 11 (duplicate)
- request for new LDAP/LDIF files for eduPerson - volunteers?
- Heather will draft, Terry will test
- updated all version numbers to semantic versions - ok, or revert to the original numbering scheme until 4.4.0?
- Suggest instead do a transition of having both the date and the semantic version until version 5, then having a clean break
- mixed feelings (but no strong ones) regarding using semantic versioning; it's a useful signal, but often not applied well or consistently
- Subcommittee status
- voPerson - 2.0 ftw!
- DNS transfer to GEANT in progress
- AOB
{"serverDuration": 159, "requestCorrelationId": "0fe69c1da0e69312"}
1 Comment
Jon Miner
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
andolcObjectClasses
are specific to OpenLDAP, on Oracle/Sun directories it'sattributetypes
andobjectClasses
oncn=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?