Hi Matt,

The website already sounds like something that I could help out. Not an
expert at all, but could definitely think of a couple of things. I noticed
that it's a default website, which of course hurts us already in terms of
accessibility because it's not dealing with things like A11Y. We could
consider switching to another documentation system that would already offer
us some of these capabilities out of the box [1]. I'll do some
investigation on that.

Thanks,

Martijn

[1]
https://dev.to/eevajonnapanula/results-of-quick-testing-of-documentation-tools-accessibility-3808

On Wed, Oct 5, 2022 at 2:02 PM Matt Sicker <boa...@gmail.com> wrote:

> Managing our website would certainly be a great starting point! Generally
> speaking, we’ve got a few things going on including a community survey
> (analysis of which is being done by consultants), the Outreachy program
> (including getting sponsors to donate to Outreachy to support Apache
> projects being able to get interns through the program as well as
> mentoring), publishing more on previous survey results (kind of needs an
> updated website first), and then some things we haven’t been able to do so
> much yet like social media, blogging, etc.
>
> Let us know what kind of things you’d be interested in working on!
> —
> Matt Sicker
>
> > On Oct 5, 2022, at 11:06, Martijn Visser <martijnvis...@apache.org>
> wrote:
> >
> > Hi all,
> >
> > Following today's keynote by Demetris Cheatham at Apachecon I got
> triggered
> > to volunteer for helping out improve Diversity, Equity and Inclusion at
> > Apachecon. I would love to understand what's currently going on and see
> > what I can do to help. Is there anyone who can provide me some insights
> on
> > this?
> >
> > Note: the website at https://diversity.apache.org contains links to an
> old
> > email address and archive, so I've opened
> > https://github.com/apache/diversity-site/pull/2 to get that fixed.
> >
> > Thanks,
> >
> > Martijn
> > https://twitter.com/MartijnVisser82
> > https://github.com/MartijnVisser
>
>

Reply via email to