WOO HOO!!!!!!
Congrats to the working group and thanks for the leadership of Keith Wessel. It’s been something like a three year process to get to having this approved by the Kantara membership.
Best,
Nick
Forwarded message:
From: be...@kantarainitiative.org
To: membe...@kantarainitiative.org
Subject: [Kantara - Members] All Member Ballot Passed with Success!
Date: Tue, 25 Feb 2020 11:51:06 -0500
Dear Kantara Members,
Thank you to all of those who voted in the All Member Ballot to approve the SAML V2.0 Deployment Profile for Federation Interoperability as a Kantara Initiative Recommendation. I am emailing you to announce that the All Member Ballot has passed with success! We appreciate your dedication to Kantara Initiative, Inc.
Sincerely,
The Kantara Staff
Kantara Initiative, Inc.Receive Kantara News & Updates
Kantara Initiative, Kantara Educational Foundation & Kantara Europe
_______________________________________________
Membership mailing list
Membe...@kantarainitiative.org
https://kantarainitiative.org/mailman/listinfo/membership
All,
Passing along the exciting news of the very, very big milestone that we have to celebrate today. Thank you to all of you who contributed with writing, edits, discussion, suggestions, and moral support.
Now, we begin the hardest part of all of this: trying to get people to use this profile.
Thanks again to everyone, it has been and continues to be a pleasure working with each of you.
Keith
_______________________________________________
WG-FI mailing list
WG...@kantarainitiative.org
https://kantarainitiative.org/mailman/listinfo/wg-fi
We should probably snapshot it in some way now…
And yes, I get that git is versioned, I just mean that now I’m not sure we want the page auto updating if people start submitting errata.
--- Eric
Yeah - we should probably do a few things:
1) Tag the release in GitHub so we have a stable identifier for it long-term.
2) Manually generate HTML and PDF versions of it using asciidoctor and asciidoctor-PDF and put them in a different publishing location, so that they don’t get overwritten by the autobuilder. Those are the versions that should get published on the main Kantara web site/behind the PII-wall.
I think we had an arrangement with Colin last time around to allow us to bypass the PII-wall, and I think we should ask for that on this one, too, since we need to be able to directly reference this profile in our federation documentation/etc, without our participants having to give Kantara their email addresses.
Best,
Nick
congrats to all
>
> Yeah - we should probably do a few things:
>
> 1) Tag the release in GitHub so we have a stable identifier for it long-term.
> 2) Manually generate HTML and PDF versions of it using asciidoctor and asciidoctor-PDF and put them in a different publishing location, so that they don’t get overwritten by the autobuilder. Those are the versions that should get published on the main Kantara web site/behind the PII-wall.
+1 to those suggestions
alan
These are all good suggestions.
Nick, would you be willing to tag the release, please?
Who’s willing to generate the HTML and PDF versions?
And Colin, I think you at least sort of answered the question, but how do we address the PII issue for publishing that Nick mentions below?
Keith
Hi Keith,
My sincerest apologies, somehow this message fell through the cracks in my inbox. Was Kantara staff able to do this, since the profile is in their github space? If not, I can work on this.
Thank you,
Nick