Skip to Content.
Sympa Menu

shibboleth-dev - RE: Moved New Deployment Guides

Subject: Shibboleth Developers

List archive

RE: Moved New Deployment Guides


Chronological Thread 
  • From: "Wilcox, Mark" <>
  • To: "Nate Klingenstein" <>, "Tom Scavo" <>
  • Cc: "Shibboleth Development" <>
  • Subject: RE: Moved New Deployment Guides
  • Date: Wed, 1 Jun 2005 11:33:57 -0400

Title: Re: Moved New Deployment Guides
Hmm,
I'm not sure how Wiki is more inflexible than a document you can't easily update and distibute? :) And while I would describe Wiki many ways, inflexible is not one of them :).
 
Not throw gas on a fire - but I'm just curious can you explain how that consenus was reached?
 
Mark


From: Nate Klingenstein [mailto:]
Sent: Wed 6/1/2005 10:57 AM
To: Tom Scavo
Cc: Shibboleth Development
Subject: Re: Moved New Deployment Guides

Tom,

We've been bludgeoning each other over this for the last several months
solid and I think the consensus we've come to is that the deployment
guides need to be able to and are capable of presenting information in
a way that the rigid structure of a Wiki just can't.  These are also
fairly monolithic documents which won't require much modification,
ideally.  Other information which is more malleable and provides a
cross-reference into the deployment information, such as a FAQ-style
material covering common scenarios, will live in the Wiki and point
into the deployment guides.  Does that sound reasonable?

If you have individual comments I would be happy to incorporate them. 
I don't foresee this as being a frequent occurrence.

Thanks,
Nate.

On Jun 1, 2005, at 11:31, Tom Scavo wrote:

> Nate, could this documentation be put in the wiki?  I have a marked up
> hardcopy of idp/prepinfo.html, for instance, but no easy way of
> communicating or incorporating the changes.
>
> Thanks,
> Tom
>
> On 5/31/05, Nate Klingenstein <> wrote:
>> ... to:
>>
>> http://shibboleth.internet2.edu/guides/idp/
>> http://shibboleth.internet2.edu/guides/sp/
>>
>>
>




Archive powered by MHonArc 2.6.16.

Top of Page