On Thu, Mar 23, 2017 at 9:24 AM, Justin W. Flory <[email protected]> wrote:

> On 03/23/2017 04:12 AM, InvalidPath wrote:
> > While looking for SOP's to inspect I've stumbled across
> >
> >
> > It seems the correct url
> > is: https://infrastructure.fedoraproject.org/infra/docs/
> docs/sysadmin-guide/sops/
> >
> > The link
> > from https://fedoraproject.org/wiki/Category:Infrastructure_SOPs might
> > be incorrect as: https://infrastructure.fedoraproject.org/infra/docs/
> >
> > i.e.:
> > https://fedoraproject.org/wiki/Content_Hosting_Infrastructure_SOP
> > fails
> > here: https://infrastructure.fedoraproject.org/infra/docs/
> contenthosting.rst
> >
> > https://fedoraproject.org/wiki/SELinux_Infrastructure_SOP
> > fails here: https://infrastructure.fedoraproject.org/infra/docs/
> selinux.rst
> >
> > https://fedoraproject.org/wiki/Outage_Infrastructure_SOP
> > fails here: https://infrastructure.fedoraproject.org/infra/docs/
> outage.rst
> >
> >
> > I'm thinking either someone typo'd teh path to add a second 'doc' or
> > possibly the site side didn't get the url updated.  In either case,
> > things be broken :)
> >
>
> Hello,
>
> The links changed at the beginning of this month when FedoraHosted
> services retired. I asked the same question this week in IRC and nirik
> gave me the new location. The new home and URL for the SOPs can be found
> here:
>
>     https://docs.pagure.org/infra-docs/sysadmin-guide/sops/<sop name>.html
>
> For example:
>
>
> https://docs.pagure.org/infra-docs/sysadmin-guide/sops/
> freenode-irc-channel.html
>
> Hope this helps.
>
> --
> Cheers,
> Justin W. Flory
> [email protected]
>
>
> _______________________________________________
> infrastructure mailing list -- [email protected]
> To unsubscribe send an email to infrastructure-leave@lists.
> fedoraproject.org
>
>
Thanks Justin.. I did find the new location by accident last night.  But
seems the old page should maybe go away.
_______________________________________________
infrastructure mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to