rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / code / Atom feed
* [ANN] Rack, Change of Maintainer & Status
@ 2014-08-18 20:28 jftucker
  2014-08-18 21:45 ` Eric Wong
  2014-08-19  0:04 ` Aaron Patterson
  0 siblings, 2 replies; 4+ messages in thread
From: jftucker @ 2014-08-18 20:28 UTC (permalink / raw)
  To: ruby-talk, rack-devel, rack-core, rubyonrails-talk

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Dearest Rack Community, Ruby Community, and passionate onlookers,

There is a time when transitions must be realized by a point of impact, when a torch must go out, and it's replacement brightens the darkness. We've arrived at such a point in the history of Rack. To cut the following story short, I (raggi) will be stepping down from any "maintainer" role in Rack. Aaron (tenderlove) will continue to maintain point releases henceforth. Additionally, as it stands today, the "Rack Core Team" are formally announcing that we do not expect that this team will release Rack 2.0. The rest of this missive will explain some history, and provide overdue gratitudes.

As many have seen, in the last year Rack has seen little to no maintenance. This is both a good and a bad thing. It is good in that the product is quite stable now, for what it is. It is bad in that the product is, like all software, not yet bug free. More than bug related challenges, Rack is now starting to fall behind the times at the architecture level. The reasons for non-maintenance are largely personal reasons, related to the lives of the core team. In most cases, a large part of the reason is that the team has moved on, using alternative technologies, if doing any software engineering at all. Some members have kids, some have jobs too busy to make time for Rack.

After some discussion by partially-laden swallow and internet telepathy, the original core team are in agreement that "holding the torch" - Rack as the sole middle-tier specification for the Ruby community - is at this point no longer appropriate. The world is changing, with Websockets, Server-Sent Events, SPDY, HTTP2, quic, and many Ruby implementations having usable multi-threading among many many other things. The next generation of middleware specification for Ruby should address these changes, and we wish to encourage the community to take ownership and do this.

It is quite likely that some battles will ensue, but it is our "dying" hope that by announcing the completion of Rack, the community will rally to the cries of its many members. Users will place their fire and brimstone under cauldrons and once again cook up a popular new abstraction that will spread even across foreign lands as Rack once did.

When Rack was first introduced to the community, there were many specifications for server and application interfaces. Chris did an amazing job at providing an abstraction so simple that it would be hard to argue it could be any simpler. In addition to providing a much needed specification for the connection between servers and applications, Rack also included many helpers to reduce common duplication - with great success. Eventually even Rails joined the party, and once at critical mass, Chris created the Rack Core Team. This was a fruitful period in the history of Rack. A great deal of middleware was produced, and it was good.

Fast forward to a couple of years ago, and Rack was in a similar place to where it is now. Many of the core team were busy with other responsibilities, and Rack was behind in maintenance. I (raggi) saw this and saw members of the community suffering as a result. I decided to put in the effort to clear our backlog and roll some releases. Little did I know at the time, but performing such an effort can inadvertently transmute oneself into a maintainer. In the time that followed, I did my best to ensure that critical security releases were timely, and that at other times, as few regressions were released as possible. For some in the community, this attention to detail was too much, they would prefer more speed. Rack has a very large API surface, that stretches deep into the servers, and deep into the applications. The API is very simple, which also means that it's subtleties are actually critical semantics for many users. In light of this, there is some advice available in this gist[1], that was once unfortunately made public before it's time. I hope that it provides some food for thought in future endeavours, but it is in no way a map to fame and riches (or a recipe for brewing what the next tier should be!).

A final note for those that may now be hearing the rattle of their chainmail. Rack will still be maintained for some time. The community needs it, and there are many that depend on it. There are many people who can still look after it, and additionally I will still assist those that kindly request it. No one is leaving you unsupported, this announcement is for your benefit, and it is best to see it as a chapter for the community, not an epitaph. Aaron will provide more details in due time.

Thank you everyone for your contributions, code, comments, support, discussions and even arguments. Without your input, Rack would not have been so successful. Never underestimate your value, we love you all, and we wish you the best of times!

Happy hacking,

 - raggi, in association with rack-core.

[1] https://gist.github.com/raggi/11c3491561802e573a47


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJT8mH6AAoJELphsezQxofDFTwH/1Gu1yF5paia7IvI6ciCNutD
cd422lkbEubT0RwZEEZjKG/4ah3THcvjJwgRk6v74ggA0GKrXmMsgSeQSC59L1GH
BCw+FdMj8DwEoCfVGo9ID42SmHGuj+6W7MNpTPVW5u/Ck4k1uJ14gcSdoaS4ut0V
Wqr623uhYcIPEgQir6jvVjRCHclnjphR7cVmeueV7Lpnh15Tw1ttoRPZgsHsYqat
vTwYz2x4XC8jNfGLbejEoxSNnCc8UZC6SfVnMazOuqN6RnR0p7qBXSCtTD72H8l7
Fk+cAivJxjss+rnorYjxsS7a4XUsspYaaLd+IdYcNDRGLhPbltdOpLcG6U005TU=
=Qwuf
-----END PGP SIGNATURE-----

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Core team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-core+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ANN] Rack, Change of Maintainer & Status
  2014-08-18 20:28 [ANN] Rack, Change of Maintainer & Status jftucker
@ 2014-08-18 21:45 ` Eric Wong
  2014-08-19  0:04 ` Aaron Patterson
  1 sibling, 0 replies; 4+ messages in thread
From: Eric Wong @ 2014-08-18 21:45 UTC (permalink / raw)
  To: rack-devel; +Cc: ruby-talk, rack-core, rubyonrails-talk

James, Chris: thank you for all the leadership and work over the years!
Rack has inspired a lot of my work over the years (including servers
outside of Ruby).

To Aaron and new maintainers:
For the old-fashioned Rack apps, my services remain _always_ available
via old-fashioned email.  Consider me obsolete when it comes to features
requiring new-fangled GUI browsers, though.  curl is my co-pilot :)

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Core team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-core+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ANN] Rack, Change of Maintainer & Status
  2014-08-18 20:28 [ANN] Rack, Change of Maintainer & Status jftucker
  2014-08-18 21:45 ` Eric Wong
@ 2014-08-19  0:04 ` Aaron Patterson
  2014-08-19 11:53   ` Christian Neukirchen
  1 sibling, 1 reply; 4+ messages in thread
From: Aaron Patterson @ 2014-08-19  0:04 UTC (permalink / raw)
  To: rack-core; +Cc: ruby-talk, rack-devel, rubyonrails-talk

[-- Attachment #1: Type: text/plain, Size: 7239 bytes --]

Thanks for the hard work through the years raggi!

I'm actually really excited to take over.  First I want to say that I'll be
taking over maintenance (including bug fixes, etc).  I do expect to release
a Rack 2.0, but as a gem version, maybe not a SPEC version.  I *do* want to
push forward the rack SPEC, but I think that's a different thread.  Maybe
the next generation Rack won't be called "Rack", but I don't see why not
(although, again that's a different thread).

Anyway, thank you all so much for the hard work through the years, and I
can't wait to go to the next chapter.  I've released a 1.6.0-beta so please
try it out.  We'll ship another beta with a better announcement email.

I'm on vacation right now, but I've got some ideas for where we should go
and I'll start a new thread with that when I get back.

<3<3<3<3



On Mon, Aug 18, 2014 at 1:28 PM, <jftucker@gmail.com> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Dearest Rack Community, Ruby Community, and passionate onlookers,
>
> There is a time when transitions must be realized by a point of impact,
> when a torch must go out, and it's replacement brightens the darkness.
> We've arrived at such a point in the history of Rack. To cut the following
> story short, I (raggi) will be stepping down from any "maintainer" role in
> Rack. Aaron (tenderlove) will continue to maintain point releases
> henceforth. Additionally, as it stands today, the "Rack Core Team" are
> formally announcing that we do not expect that this team will release Rack
> 2.0. The rest of this missive will explain some history, and provide
> overdue gratitudes.
>
> As many have seen, in the last year Rack has seen little to no
> maintenance. This is both a good and a bad thing. It is good in that the
> product is quite stable now, for what it is. It is bad in that the product
> is, like all software, not yet bug free. More than bug related challenges,
> Rack is now starting to fall behind the times at the architecture level.
> The reasons for non-maintenance are largely personal reasons, related to
> the lives of the core team. In most cases, a large part of the reason is
> that the team has moved on, using alternative technologies, if doing any
> software engineering at all. Some members have kids, some have jobs too
> busy to make time for Rack.
>
> After some discussion by partially-laden swallow and internet telepathy,
> the original core team are in agreement that "holding the torch" - Rack as
> the sole middle-tier specification for the Ruby community - is at this
> point no longer appropriate. The world is changing, with Websockets,
> Server-Sent Events, SPDY, HTTP2, quic, and many Ruby implementations having
> usable multi-threading among many many other things. The next generation of
> middleware specification for Ruby should address these changes, and we wish
> to encourage the community to take ownership and do this.
>
> It is quite likely that some battles will ensue, but it is our "dying"
> hope that by announcing the completion of Rack, the community will rally to
> the cries of its many members. Users will place their fire and brimstone
> under cauldrons and once again cook up a popular new abstraction that will
> spread even across foreign lands as Rack once did.
>
> When Rack was first introduced to the community, there were many
> specifications for server and application interfaces. Chris did an amazing
> job at providing an abstraction so simple that it would be hard to argue it
> could be any simpler. In addition to providing a much needed specification
> for the connection between servers and applications, Rack also included
> many helpers to reduce common duplication - with great success. Eventually
> even Rails joined the party, and once at critical mass, Chris created the
> Rack Core Team. This was a fruitful period in the history of Rack. A great
> deal of middleware was produced, and it was good.
>
> Fast forward to a couple of years ago, and Rack was in a similar place to
> where it is now. Many of the core team were busy with other
> responsibilities, and Rack was behind in maintenance. I (raggi) saw this
> and saw members of the community suffering as a result. I decided to put in
> the effort to clear our backlog and roll some releases. Little did I know
> at the time, but performing such an effort can inadvertently transmute
> oneself into a maintainer. In the time that followed, I did my best to
> ensure that critical security releases were timely, and that at other
> times, as few regressions were released as possible. For some in the
> community, this attention to detail was too much, they would prefer more
> speed. Rack has a very large API surface, that stretches deep into the
> servers, and deep into the applications. The API is very simple, which also
> means that it's subtleties are actually critical semantics for many users.
> In light of this, there is some advice available in this gist[1], that was
> once unfortunately made public before it's time. I hope that it provides
> some food for thought in future endeavours, but it is in no way a map to
> fame and riches (or a recipe for brewing what the next tier should be!).
>
> A final note for those that may now be hearing the rattle of their
> chainmail. Rack will still be maintained for some time. The community needs
> it, and there are many that depend on it. There are many people who can
> still look after it, and additionally I will still assist those that kindly
> request it. No one is leaving you unsupported, this announcement is for
> your benefit, and it is best to see it as a chapter for the community, not
> an epitaph. Aaron will provide more details in due time.
>
> Thank you everyone for your contributions, code, comments, support,
> discussions and even arguments. Without your input, Rack would not have
> been so successful. Never underestimate your value, we love you all, and we
> wish you the best of times!
>
> Happy hacking,
>
>  - raggi, in association with rack-core.
>
> [1] https://gist.github.com/raggi/11c3491561802e573a47
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1
>
> iQEcBAEBAgAGBQJT8mH6AAoJELphsezQxofDFTwH/1Gu1yF5paia7IvI6ciCNutD
> cd422lkbEubT0RwZEEZjKG/4ah3THcvjJwgRk6v74ggA0GKrXmMsgSeQSC59L1GH
> BCw+FdMj8DwEoCfVGo9ID42SmHGuj+6W7MNpTPVW5u/Ck4k1uJ14gcSdoaS4ut0V
> Wqr623uhYcIPEgQir6jvVjRCHclnjphR7cVmeueV7Lpnh15Tw1ttoRPZgsHsYqat
> vTwYz2x4XC8jNfGLbejEoxSNnCc8UZC6SfVnMazOuqN6RnR0p7qBXSCtTD72H8l7
> Fk+cAivJxjss+rnorYjxsS7a4XUsspYaaLd+IdYcNDRGLhPbltdOpLcG6U005TU=
> =Qwuf
> -----END PGP SIGNATURE-----
>
> --
>
> ---
> You received this message because you are subscribed to the Google Groups
> "Rack Core team" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to rack-core+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Aaron Patterson
http://tenderlovemaking.com/

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Core team" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-core+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #2: Type: text/html, Size: 8356 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: [ANN] Rack, Change of Maintainer & Status
  2014-08-19  0:04 ` Aaron Patterson
@ 2014-08-19 11:53   ` Christian Neukirchen
  0 siblings, 0 replies; 4+ messages in thread
From: Christian Neukirchen @ 2014-08-19 11:53 UTC (permalink / raw)
  To: Aaron Patterson

Aaron Patterson <aaron.patterson@gmail.com> writes:

> Thanks for the hard work through the years raggi!
>
> I'm actually really excited to take over.  First I want to say that I'll be
> taking over maintenance (including bug fixes, etc).  I do expect to release
> a Rack 2.0, but as a gem version, maybe not a SPEC version.  I *do* want to
> push forward the rack SPEC, but I think that's a different thread.  Maybe
> the next generation Rack won't be called "Rack", but I don't see why not
> (although, again that's a different thread).

Ping me if you have time, then I'll tell you a few notes on the release process.

-- 
Christian Neukirchen  <chneukirchen@gmail.com>  http://chneukirchen.org

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2014-08-19 11:53 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2014-08-18 20:28 [ANN] Rack, Change of Maintainer & Status jftucker
2014-08-18 21:45 ` Eric Wong
2014-08-19  0:04 ` Aaron Patterson
2014-08-19 11:53   ` Christian Neukirchen

Code repositories for project(s) associated with this inbox:

	https://80x24.org/mirrors/rack.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).