State and Future of repos in the owin organization on GitHub

[Ryan Riley]

The owin organization on GitHub contains a number of repositories about which I know very little in terms of their current state or future plans. These include:

• gate
• owin-hosting
• owin-samples
• owin-sandbox

I recall that many of these eventually found their way into Katana, either in conceptual or concrete form. Do we still want to maintain these projects? Should we decommission them? I don't think anyone expects us to maintain them. Some could be re-purposed to show how OWIN is intended to be used.

Thoughts?

Ryan

[Mark Rendle]

I'd suggest decommissioning everything except samples. Gate became Katana, hosting became the Katana hosting bits, and sandbox was full of broken toys and cat poop.

--
You received this message because you are subscribed to the Google Groups ".NET HTTP Abstractions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstrac...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Mark Rendle

Founder, Zudio

[Sebastien Lambla]

+1

--

Sebastien Lambla

s...@serialseb.com - http://serialseb.com

[Damian Hickey]

+1

On Tuesday, 27 May 2014 15:40:42 UTC+2, SerialSeb wrote:

+1

--

Sebastien Lambla

s...@serialseb.com - http://serialseb.com

On 24 May 2014, at 18:20, Mark Rendle <ma...@markrendle.net> wrote:

I'd suggest decommissioning everything except samples. Gate became Katana, hosting became the Katana hosting bits, and sandbox was full of broken toys and cat poop.

On Saturday, 24 May 2014, Ryan Riley <ryan....@panesofglass.org> wrote:

The owin organization on GitHub contains a number of repositories about which I know very little in terms of their current state or future plans. These include:

• gate
• owin-hosting
• owin-samples
• owin-sandbox

I recall that many of these eventually found their way into Katana, either in conceptual or concrete form. Do we still want to maintain these projects? Should we decommission them? I don't think anyone expects us to maintain them. Some could be re-purposed to show how OWIN is intended to be used.

Thoughts?

Ryan

--
You received this message because you are subscribed to the Google Groups ".NET HTTP Abstractions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstractions+unsub...@googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

--

Mark Rendle

Founder, Zudio

--
You received this message because you are subscribed to the Google Groups ".NET HTTP Abstractions" group.

To unsubscribe from this group and stop receiving emails from it, send an email to net-http-abstractions+unsub...@googlegroups.com.

[scott...@gmail.com]

Ok, cool. We've renamed the old repos and switched the OWIN and OWIN.github.com repos around. The idea being the OWIN repo will hold the spec, extensions, and governance documents and the OWIN.github.io repo holds the site.