Re: Anonymous IP Blocking Flowchart
+1, I think the wiki is good for WIP and then once you submit a PR for the feature, put it in the docs. We probably should take some time to re-organize our docs. On Fri, Oct 20, 2017 at 9:20 AM, Durfey, Ryan <ryan_dur...@comcast.com> wrote: > I would say if it is work in progress it would go in the wiki. Once > formally released to open source it would go here: > http://trafficcontrol.apache.org/docs/latest/index.html . > > Ryan DurfeyM | 303-524-5099 > CDN Support (24x7): 866-405-2993 or cdn_supp...@comcast.com cdn_supp...@comcast.com> > > > From: "Eric Friedrich (efriedri)" <efrie...@cisco.com> > Reply-To: "dev@trafficcontrol.incubator.apache.org" < > dev@trafficcontrol.incubator.apache.org> > Date: Friday, October 20, 2017 at 8:58 AM > To: "dev@trafficcontrol.incubator.apache.org" < > dev@trafficcontrol.incubator.apache.org> > Subject: Re: Anonymous IP Blocking Flowchart > > Where do we think our “design docs” (diagrams and text) belong? > > One option is the Wiki, but that can get stale so I’d toss it out there > that PRs should include the obvious user facing docs, but also a design doc > section as well > > -Eric > > > On Oct 20, 2017, at 10:23 AM, Jeff Elsloo <els...@apache.org<mailto:elsl > o...@apache.org>> wrote: > Hey Eric, > Thanks for sending this out. Hopefully we can build more of these > diagrams in the future to include in the docs. I'll try to put > something similar together for the stuff I've been working on. > -- > Thanks, > Jeff > On Thu, Oct 19, 2017 at 1:55 PM, Eric Friedrich (efriedri) > <efrie...@cisco.com<mailto:efrie...@cisco.com>> wrote: > Just realized the first diagram I put up was outdated > The response to anonymous IP blocking is actually configurable between a > slate (302 redirect to a new URL) and a 403 > —Eric > On Oct 19, 2017, at 10:53 AM, Eric Friedrich (efriedri) < > efrie...@cisco.com<mailto:efrie...@cisco.com>> wrote: > Here is flowchart requested at the summit. I’ll put this diagram along > with the rest of the slides up soon > Its a link to a PNG despite the horribly formatted URL > https://cisco.box.com/s/4rwd6kk069vdmzxpp2ak0vt2elds0ufc > —Eric > > >
Re: Anonymous IP Blocking Flowchart
I would say if it is work in progress it would go in the wiki. Once formally released to open source it would go here: http://trafficcontrol.apache.org/docs/latest/index.html . Ryan DurfeyM | 303-524-5099 CDN Support (24x7): 866-405-2993 or cdn_supp...@comcast.com<mailto:cdn_supp...@comcast.com> From: "Eric Friedrich (efriedri)" <efrie...@cisco.com> Reply-To: "dev@trafficcontrol.incubator.apache.org" <dev@trafficcontrol.incubator.apache.org> Date: Friday, October 20, 2017 at 8:58 AM To: "dev@trafficcontrol.incubator.apache.org" <dev@trafficcontrol.incubator.apache.org> Subject: Re: Anonymous IP Blocking Flowchart Where do we think our “design docs” (diagrams and text) belong? One option is the Wiki, but that can get stale so I’d toss it out there that PRs should include the obvious user facing docs, but also a design doc section as well -Eric On Oct 20, 2017, at 10:23 AM, Jeff Elsloo <els...@apache.org<mailto:els...@apache.org>> wrote: Hey Eric, Thanks for sending this out. Hopefully we can build more of these diagrams in the future to include in the docs. I'll try to put something similar together for the stuff I've been working on. -- Thanks, Jeff On Thu, Oct 19, 2017 at 1:55 PM, Eric Friedrich (efriedri) <efrie...@cisco.com<mailto:efrie...@cisco.com>> wrote: Just realized the first diagram I put up was outdated The response to anonymous IP blocking is actually configurable between a slate (302 redirect to a new URL) and a 403 —Eric On Oct 19, 2017, at 10:53 AM, Eric Friedrich (efriedri) <efrie...@cisco.com<mailto:efrie...@cisco.com>> wrote: Here is flowchart requested at the summit. I’ll put this diagram along with the rest of the slides up soon Its a link to a PNG despite the horribly formatted URL https://cisco.box.com/s/4rwd6kk069vdmzxpp2ak0vt2elds0ufc —Eric
Re: Anonymous IP Blocking Flowchart
Where do we think our “design docs” (diagrams and text) belong? One option is the Wiki, but that can get stale so I’d toss it out there that PRs should include the obvious user facing docs, but also a design doc section as well -Eric > On Oct 20, 2017, at 10:23 AM, Jeff Elsloowrote: > > Hey Eric, > > Thanks for sending this out. Hopefully we can build more of these > diagrams in the future to include in the docs. I'll try to put > something similar together for the stuff I've been working on. > -- > Thanks, > Jeff > > > On Thu, Oct 19, 2017 at 1:55 PM, Eric Friedrich (efriedri) > wrote: >> Just realized the first diagram I put up was outdated >> >> The response to anonymous IP blocking is actually configurable between a >> slate (302 redirect to a new URL) and a 403 >> >> —Eric >> >>> On Oct 19, 2017, at 10:53 AM, Eric Friedrich (efriedri) >>> wrote: >>> >>> Here is flowchart requested at the summit. I’ll put this diagram along with >>> the rest of the slides up soon >>> >>> Its a link to a PNG despite the horribly formatted URL >>> https://cisco.box.com/s/4rwd6kk069vdmzxpp2ak0vt2elds0ufc >>> >>> —Eric >>> >>> >>
Re: Anonymous IP Blocking Flowchart
Hey Eric, Thanks for sending this out. Hopefully we can build more of these diagrams in the future to include in the docs. I'll try to put something similar together for the stuff I've been working on. -- Thanks, Jeff On Thu, Oct 19, 2017 at 1:55 PM, Eric Friedrich (efriedri)wrote: > Just realized the first diagram I put up was outdated > > The response to anonymous IP blocking is actually configurable between a > slate (302 redirect to a new URL) and a 403 > > —Eric > >> On Oct 19, 2017, at 10:53 AM, Eric Friedrich (efriedri) >> wrote: >> >> Here is flowchart requested at the summit. I’ll put this diagram along with >> the rest of the slides up soon >> >> Its a link to a PNG despite the horribly formatted URL >> https://cisco.box.com/s/4rwd6kk069vdmzxpp2ak0vt2elds0ufc >> >> —Eric >> >> >
Anonymous IP Blocking Flowchart
Here is flowchart requested at the summit. I’ll put this diagram along with the rest of the slides up soon Its a link to a PNG despite the horribly formatted URL https://cisco.box.com/s/4rwd6kk069vdmzxpp2ak0vt2elds0ufc —Eric