Shibboleth Developers

[Nate Klingenstein <>]

Thanks for taking the time to respond thoroughly.  This is very useful.

> - Where's the FAQ?

Living dinosaur(s) on the Shibboleth main site, I'm afraid.  Trying to 
figure out just how to do this has plagued us for years, and I guess 
flu season's not that far away, so we can have another go at it.  I'd 
like to see this raised in a broader discussion asking precisely that 
question, and then we can make something good that lives somewhere good 
and hopefully be done with it for awhile.  Bear in mind with this and 
the glossary we want some information to be thoroughly vetted and 
authoritative.  I'm not fully familiar with the Wiki environment to 
know how well that can be done, but if change moderation is easy this 
may be a good place.

> - I'm really glad to see topic ShibbolethDevelopment (which is long
> overdue).  How to set up a dev environment should go here (Howard has
> a ton of good stuff).  Also, a page on each of the major extension
> points might be useful (name mapping, resolver, protocol, etc.).

Agreed, this information will live one layer down, but this is great 
grist.

> - What about Installation > Requirements?

Covered thoroughly in the deployment guides.

> - Bibliography (standards, specifications, etc.)

I'm not sure whether the Bibliography should be part of the main 
Shibboleth pages or the Wiki.  I'd lean Wiki, but it's fragmented 
throughout the former presently.  I might bump the eAuth information 
down a layer and replace that with a bibliography.

> - FeatureRequests (or WishList)

This can live beneath the RoadMap.

> - Deployment > Profiles

I've got this listed under ShibbolethDevelopment.  Where do you think 
it should live?

> What about Testing, Troubleshooting, and Hardening (i.e.,
> SecurityConsiderations)?

Considered aspects of ProductionDeployment.