Shibboleth Developers

["Scott Cantor" <>]

> What's needed is a developer's guide.  Not just "how to" stuff (which
> is important) but a published list of interfaces you consider public. 
> Everything else is "at your own risk".

Right, and since we don't have that yet, you should consider everything to
be at your own risk. That is exactly why I refused to document all the
things that people kept stumbling over, because I knew they would be dumped.
It's not entirely about laziness. Documenting something is a commitment.
Freezing APIs too early puts a huge burden on us to maintain broken
interfaces.

-- Scott