rack-devel archive mirror (unofficial) https://groups.google.com/group/rack-devel
 help / color / mirror / Atom feed
From: Corey Farwell <coreyf@rwell.org>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Offer to move the rack-attack project to the rack GitHub organization
Date: Thu, 30 Jul 2020 07:33:43 -0700 (PDT)	[thread overview]
Message-ID: <f1ab3420-df93-4f8c-8c72-920a163490d4n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1742 bytes --]

Hey everyone, my name is Corey Farwell and I'm an engineer at Kickstarter.

Years back in 2012, some Kickstarter engineers created the rack-attack 
<https://github.com/kickstarter/rack-attack>project, which is a Rack 
middleware for blocking and throttling abusive requests. We still utilize 
and rely on rack-attack, but due to staffing changes and reductions, we 
have not made any significant contributions to the project over the past 
few years. We are fortunate to have a volunteer in the community, Gonzalo 
Rodriguez <https://github.com/grzuy>, who has stepped up to maintain the 
project in our absence. At this point, I personally consider rack-attack to 
be a community-driven project, despite living within the Kickstarter GitHub 
organization.

Fast forward to February of this year, Samuel Williams in Gitter 
<https://gitter.im/rack-attack/rack-attack?at=5e3f4e8919597421f3b97414>suggested 
moving the project to the rack GitHub organization. I ran this idea past 
the Engineering and Legal teams at Kickstarter and got the green light! Is 
this something y'all are interested in? Related– my last day at Kickstarter 
is in two weeks, so if we want this to happen, we might need to move a 
little fast :)

Hope you all are doing okay during this tumultuous time

Corey Farwell
coreyf@rwell.org
https://rwell.org/

-- 

--- 
You received this message because you are subscribed to the Google Groups "Rack Development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rack-devel+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/rack-devel/f1ab3420-df93-4f8c-8c72-920a163490d4n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 2185 bytes --]

                 reply	other threads:[~2020-07-30 14:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-list from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://groups.google.com/group/rack-devel

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f1ab3420-df93-4f8c-8c72-920a163490d4n@googlegroups.com \
    --to=rack-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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).