From mboxrd@z Thu Jan 1 00:00:00 1970 Delivered-To: chneukirchen@gmail.com Received: by 10.76.159.200 with SMTP id xe8csp152711oab; Mon, 18 Aug 2014 13:28:46 -0700 (PDT) Return-Path: Received-SPF: pass (google.com: domain of rack-core+bncBD75LW742ECRB7ODZGPQKGQECKXHKHY@googlegroups.com designates 10.50.2.6 as permitted sender) client-ip=10.50.2.6 Authentication-Results: mr.google.com; spf=pass (google.com: domain of rack-core+bncBD75LW742ECRB7ODZGPQKGQECKXHKHY@googlegroups.com designates 10.50.2.6 as permitted sender) smtp.mail=rack-core+bncBD75LW742ECRB7ODZGPQKGQECKXHKHY@googlegroups.com; dkim=pass header.i=@googlegroups.com X-Received: from mr.google.com ([10.50.2.6]) by 10.50.2.6 with SMTP id 6mr38672igq.10.1408393725901 (num_hops = 1); Mon, 18 Aug 2014 13:28:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlegroups.com; s=20120806; h=mime-version:message-id:date:from:to:subject:x-original-sender :x-original-authentication-results:reply-to:precedence:mailing-list :list-id:list-post:list-help:list-archive:sender:list-unsubscribe :content-type:content-transfer-encoding; bh=w/GwgmfZICe3Ufc8X8c6z8BGHwocs7OAZnOTUZkPW3E=; b=m4HGjmCA8m8mCmdYoi3Tjosbf+YTLB5Ltg77jlsoaNQtj5swac3XWog2H2MHStGN1Q zBIYhZUqJjJsknjmfjuVl9TkpLazoLQlwmwG8jAoUSz4lnqBs5iFxeW65zYG4Dvj2d6w 7beiI5IgY/yTGGKepWmokmLPZJRJeNE38cmnIx1BoOUiV3bhxXrHX6xR9znfshkBamex CyF+ykg9IFCMJE94fx8HNid3pfPkiTLxlC34Znaz4iILk3mx3d5AGUW1rvoJrufU5Lkh F6AO5qW/JOL9B3wz6AvSGJcEehYQGF0WRaD0mQz9wzawcpygb/3PxqZVpwoIv42mWovm Ju3A== X-Received: by 10.50.2.6 with SMTP id 6mr38672igq.10.1408393725895; Mon, 18 Aug 2014 13:28:45 -0700 (PDT) MIME-Version: 1.0 X-BeenThere: rack-core@googlegroups.com Received: by 10.50.79.226 with SMTP id m2ls1929229igx.17.gmail; Mon, 18 Aug 2014 13:28:45 -0700 (PDT) X-Received: by 10.50.153.98 with SMTP id vf2mr819991igb.5.1408393725641; Mon, 18 Aug 2014 13:28:45 -0700 (PDT) Received: from mail-qa0-x22e.google.com (mail-qa0-x22e.google.com [2607:f8b0:400d:c00::22e]) by gmr-mx.google.com with ESMTPS id r5si2991958qcl.0.2014.08.18.13.28.45 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 18 Aug 2014 13:28:45 -0700 (PDT) Received-SPF: pass (google.com: domain of jftucker@gmail.com designates 2607:f8b0:400d:c00::22e as permitted sender) client-ip=2607:f8b0:400d:c00::22e; Received: by mail-qa0-f46.google.com with SMTP id v10so4799941qac.5 for ; Mon, 18 Aug 2014 13:28:45 -0700 (PDT) X-Received: by 10.140.47.129 with SMTP id m1mr56982279qga.95.1408393725484; Mon, 18 Aug 2014 13:28:45 -0700 (PDT) Received: from localhost ([199.172.233.252]) by mx.google.com with ESMTPSA id b15sm31376848qac.36.2014.08.18.13.28.44 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 18 Aug 2014 13:28:44 -0700 (PDT) Message-ID: <53f261fc.0f1ae00a.7148.7a49@mx.google.com> Date: Mon, 18 Aug 2014 13:28:44 -0700 (PDT) From: jftucker@gmail.com To: ruby-talk@ruby-lang.org, rack-devel@googlegroups.com, rack-core@googlegroups.com, rubyonrails-talk@googlegroups.com Subject: [ANN] Rack, Change of Maintainer & Status X-Original-Sender: jftucker@gmail.com X-Original-Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jftucker@gmail.com designates 2607:f8b0:400d:c00::22e as permitted sender) smtp.mail=jftucker@gmail.com; dkim=pass header.i=@gmail.com; dmarc=pass (p=NONE dis=NONE) header.from=gmail.com Reply-To: rack-core@googlegroups.com Precedence: list Mailing-list: list rack-core@googlegroups.com; contact rack-core+owners@googlegroups.com List-ID: X-Google-Group-Id: 504757074975 List-Post: , List-Help: , List-Archive: , Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable -----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, whe= n a torch must go out, and it's replacement brightens the darkness. We've a= rrived at such a point in the history of Rack. To cut the following story s= hort, I (raggi) will be stepping down from any "maintainer" role in Rack. A= aron (tenderlove) will continue to maintain point releases henceforth. Addi= tionally, 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 thi= s 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 qui= te stable now, for what it is. It is bad in that the product is, like all s= oftware, not yet bug free. More than bug related challenges, Rack is now st= arting to fall behind the times at the architecture level. The reasons for = non-maintenance are largely personal reasons, related to the lives of the c= ore team. In most cases, a large part of the reason is that the team has mo= ved on, using alternative technologies, if doing any software engineering a= t all. Some members have kids, some have jobs too busy to make time for Rac= k. After some discussion by partially-laden swallow and internet telepathy, th= e original core team are in agreement that "holding the torch" - Rack as th= e 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 mult= i-threading among many many other things. The next generation of middleware= specification for Ruby should address these changes, and we wish to encour= age 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 sprea= d even across foreign lands as Rack once did. When Rack was first introduced to the community, there were many specificat= ions for server and application interfaces. Chris did an amazing job at pro= viding 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 c= onnection between servers and applications, Rack also included many helpers= to reduce common duplication - with great success. Eventually even Rails j= oined the party, and once at critical mass, Chris created the Rack Core Tea= m. This was a fruitful period in the history of Rack. A great deal of middl= eware was produced, and it was good. Fast forward to a couple of years ago, and Rack was in a similar place to w= here 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 cle= ar our backlog and roll some releases. Little did I know at the time, but p= erforming such an effort can inadvertently transmute oneself into a maintai= ner. In the time that followed, I did my best to ensure that critical secur= ity releases were timely, and that at other times, as few regressions were = released as possible. For some in the community, this attention to detail w= as too much, they would prefer more speed. Rack has a very large API surfac= e, that stretches deep into the servers, and deep into the applications. Th= e API is very simple, which also means that it's subtleties are actually cr= itical semantics for many users. In light of this, there is some advice ava= ilable 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 chainmai= l. 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 i= t. 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, discuss= ions and even arguments. Without your input, Rack would not have been so su= ccessful. 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=3D =3DQwuf -----END PGP SIGNATURE----- --=20 ---=20 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 e= mail to rack-core+unsubscribe@googlegroups.com. For more options, visit https://groups.google.com/d/optout.