The following is an unordered, unprioritized list of high-level tasks that various ComDev people are working on. If you wish to take responsibility for one of these, please speak up on dev@community.apache.org so that we don't have duplication of effort. Thanks.

Wider ASF-focused or project-focused Tasks

• Review project mission statements. Mission statements appear on project websites, on projects.apache.org, in board reports, and other places.  In particular, some of these places end up getting aggregated to projects.apache.org and other places, which can be useful to bring in new contributors. Talk to projects that have terrible/confusing/meaningless ones. Help projects explain what the project is, what it does, who should care, and why they should care.
• Get project websites to comply with sitecheck criteria. Communicate better why this matters. https://whimsy.apache.org/site/ The policy/rationale for the checks is here: https://www.apache.org/foundation/marks/pmcs#navigation
• Research and implement a replacement for Redbubble (See How To: Add Project Logos to Redbubble Store) - Many projects or individual speakers want to bring stickers when they attend events, meetups, and the like.  ComDev PMC has a budget to pay for some stickers, however we no longer have a regular vendor to order from.  Finding a new vendor that the PMC could vet and chose would be neat!

Community.apache.org Website Improvement Tasks

• Write Doc: Why would a project want to come to the ASF (ie, our value proposition to an existing project - what benefits will they get that justify the costs?). See also: the Incubator: why would someone want to bring their community here?
• Define simple style/layout guides for new content on the website.  Very simple best practices for any style, document structure, or the like guides are helpful for people creating new content (or taking the time to migrate/update existing content).  In particular: past complaints are often "it's a wall of text", so when should writers include images/etc. in content, and what's the simplest way to do so consistently?  See also: https://photos.apachecon.com/ for imagery.
• Draft ideas for navigation/pathing: the current website serves multiple audiences and topics.  Starting to define how an overall navigation structure will help lead people to where they want to go is useful.

• Onboarding documents for major audiences (Contributor, Committer, PMC member, ASF Member, Director). Some of these exist, but can be improved. Some do not exist in an organized fashion. All need to be made more consistent in scope and format, and more discoverable in the usual places.  START HERE: Proposal: Improving Onboarding Experiences

• Explain the why of quarterly project reporting. Who should you report to? (Board vs Stakeholders are separate reports, with different tones and purposes, for example.). See also the official policy/guidance: https://apache.org/foundation/board/reporting See also the PMC guide: https://community.apache.org/pmc/reporting and See also the report wizard https://reporter.apache.org/

See Also: A list of specific ideas about the ComDev website: Proposal: ComDev Website Improvements