Return-Path: Received: from desis.arachnitech.com ([unix socket]) by desis.arachnitech.com (Cyrus 2.5.15-28-g7d1550bfa-Kolab-2.5.15.28-1.20.el7.kolab_16) with LMTPA; Wed, 10 Mar 2021 09:21:18 -0500 X-Sieve: CMU Sieve 2.4 X-Virus-Scanned: amavisd-new at arachnitech.com X-Spam-Flag: NO X-Spam-Score: -0.092 X-Spam-Level: X-Spam-Status: No, score=-0.092 tagged_above=-10 required=6.2 tests=[DKIMWL_WL_HIGH=-0.243, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: desis.arachnitech.com (amavisd-new); dkim=pass (1024-bit key) header.d=github.com Received: from s214f.ik2.com (s214f.ik2.com [208.77.151.118]) by desis.arachnitech.com (Postfix) with ESMTPS id 7ACBE350 for ; Wed, 10 Mar 2021 09:21:14 -0500 (EST) Received: from s250a.ik2.com by s214f.ik2.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (envelope-from ) id 1lJzi3-0004gV-TG for kellya@arachnitech.com; Wed, 10 Mar 2021 14:21:12 +0000 Received: from 192.30.252.201 by s250a.ik2.com (IK2 SMTP Server); Wed, 10 Mar 2021 14:21:10 +0000 Received: from github.com (hubbernetes-node-4f064af.va3-iad.github.net [10.48.114.44]) by smtp.github.com (Postfix) with ESMTPA id 057843406F2 for ; Wed, 10 Mar 2021 06:21:08 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=github.com; s=pf2014; t=1615386068; bh=wfKjHC8f33f5tPC0r7vNXCoIwc1zGPt//UQubP8I+3Q=; h=Date:From:To:Subject:From; b=x9StawBnq6/L4X4nYAFqh0wbGYumrG5w0kox8qxPJOKLTYpIqu00DPSnKylTDXP5O QI5c581RlP+snBhnlkw/QVv7mnbbEMg/0vjVlh73xa8Fp2oFPPtbyYWUIL1jA7wSsk Ps2+CGwibuQ3i0ASH/K50enPoqaBeC9/9+qCdLN0= Date: Wed, 10 Mar 2021 06:21:08 -0800 From: GitHub To: kellya@arachnitech.com Message-ID: <6048d5d431e4_5ca17d41328f4@lowworker-7f6b9d8d47-rjzbw.mail> Subject: =?UTF-8?Q?You're_in!_Welcome_to_GitHub_Sponsors_=F0=9F=92=96?= Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="--==_mimepart_6048d5d429f9_5ca17d41327fe"; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Auto-Response-Suppress: All X-SF-RX-Return-Path: X-SF-Originating-IP: 192.30.252.201 X-SF-Score: 1.2 X-SF-Alias: alex.kelly@arachnitech.com X-SF-SRS: Sender address rewritten from to X-SF-Domain: ffsuvdhlly ----==_mimepart_6048d5d429f9_5ca17d41327fe Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable # Welcome to GitHub Sponsors!=0D =0D You're just a couple of steps away from receiving your first funds as a s= ponsored=0D developer.=0D =0D ### Step 1: Submit your contact information=0D =0D Before you can start filling out your GitHub Sponsors profile, please sub= mit=0D your contact information.=0D =0D https://github.com/sponsors/kellya/signup=0D =0D ### Step 2: Create your GitHub Sponsors profile=0D =0D After submitting contact details, fill out your profile in your GitHub Sp= onsors=0D dashboard.=0D =0D https://github.com/sponsors/kellya/dashboard=0D =0D Here are some helpful guides:=0D =0D - Learn more about setting up your profile:=0D https://docs.github.com/articles/becoming-a-sponsored-developer#complet= ing-your-sponsored-developer-profile=0D =0D - Check out the Sponsors landing page to see how other developers set up = their=0D own profiles:=0D https://github.com/sponsors=0D =0D ### Step 3: Get your profile approved=0D =0D Once you complete your GitHub Sponsors profile, submit it for identity ve= rification=0D and approval by GitHub staff. We'll follow up by email when your profile = has been approved.=0D =0D ### Step 4: Get paid=0D =0D Once you receive your first sponsorship, you will be paid around the 22= nd of each month!=0D =0D And that's it! Thank you for your contribution to open source =E2=80=94 w= e're excited to see=0D all the ways GitHub Sponsors can support you.=0D ----==_mimepart_6048d5d429f9_5ca17d41327fe Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 7bit Welcome to GitHub Sponsors!
GitHub

Welcome to GitHub Sponsors!

You're just a couple of steps away from receiving your first funds as a sponsored developer.

Step 1: Submit your contact information

Before you can start filling out your GitHub Sponsors profile, please submit your contact information.

Step 2: Create your GitHub Sponsors profile

pending GitHub Sponsors profile

Fill out your profile in your GitHub Sponsors dashboard. Here are some helpful guides:

Step 3: Get your profile approved

Once you complete your GitHub Sponsors profile, submit it for identity verification and approval by GitHub staff. We'll follow up by email when your profile has been approved.

Step 4: Get paid

Once you receive your first sponsorship, you will be paid around the 22nd of each month!

And that's it! Thank you for your contribution to open source — we're excited to see all the ways GitHub Sponsors can support you.

welcometocat

Email preferences · Terms · Privacy · Sign into GitHub

GitHub, Inc.
88 Colin P Kelly Jr St.
San Francisco, CA 94107
----==_mimepart_6048d5d429f9_5ca17d41327fe--