Stepping down as a Maintainer

[ericwbailey]

This Issue is a companion to 65fc755.

I don't have the time I used to be able to dedicate towards this project to be able to effectively serve as a maintainer. There have been a lot of things slipping as of late and it's time I was honest with myself that I can't continue in this capacity. Mistakenly pushing my change to the main branch just now instead of a PR is evidence of that.

I work in accessibility full time now in a job that is increasingly making more and more demands for all my time. I have also recently had some serious personal issues conspire. I'm exhausted, and need to ruthlessly prioritize what I can realistically give my attention to. Unfortunately, I can't keep things going here.

I'd like to continue to help out where I can here and there, just as a contributor. I will do my best to support this transition, and please feel free to mention me or via email with questions if you have them.

Access transfer and stewardship

• Administration
  • Ensure admin have access to relevant GitHub areas
  • Ensure admin have access to Netlify
  • Ensure admin have access to contact form messages
  • Ensure admin have access to social media accounts (Twitter, Mastodon, and Buttondown)
  • Ensure admin have access to other relevant logins (1Password)
• Financials
  • Ensure admin have access to financials (Bank account, Open Collective)
  • Ensure recurring billings continue (Netlify, Buttondown, our domain registrar)
  • Ensure sponsors are kept listed

Platform and content concerns

• Upgrade the site's build system
  • Use Eleventy 2.0.0 (current stable version at the time this issue was posted).
  • Remove Gulp in favor of Eleventy/package.json scripts (Relevant PR here: Remove Gulp in Favor of NPM CLI #1141)
• Checklist
  • Upgrade links to use WCAG 2.2 once it is released (Relevant Issue here: Link to WCAG 2.1 instead of 2.0? #1460)
  • Update the details/summary to use a more accessible solution (Relevant issue: Investigate if <details>/<summary> is a good choice for our Checklist #1419)
  • Implement group toggle controls (Relevant issue: Feat/toggle checklist groups #1280)
• Blog posts
  • Ensure all open blog posts are edited and published if they are deemed acceptable
  • Ensure blog post authors are compensated for their published work

I wish everyone only the best for this project and its goals, and am proud of what we have accomplished together. The internet, and people's lives are better for it 💜

[esjay]

understandable. thank you for your work on this to date.

I just want to add that I'm still willing to complete work on the Gulp to NPM ticket since I contributed to that in the past.

[davatron5000]

Thanks @ericwbailey for all your work. a11yproject has become something great under your guidance and maintainership. 💜

I'm happy to step in as interim maintainer. I'll follow up here as we hatch plans for the next season of this lil' resource.

[nchan0154]

Big thanks and hugs to @ericwbailey for being such a welcoming presence, I doubt I would have felt comfortable contributing without your warm reception and stewardship. I might not be able to make a meeting due to timezones*~ but I can take charge issues relating to the technical details like upgrading 11ty and migrating WCAG links.,