Hi, Apologies if I'm not posting to the right list, feel free to redirect me to dev@ if that is more appropriate.
Sitting in a couple of sessions at ApacheCon NA I notice that one dimension of diversity is non-code contributions. I've observed that the advice to people that want to get involved is, paraphrased: - find a project that interests you - find something to do, like bug triage, or documentation, or organizing meetups, or... whatever the project needs - engage and do that Seeing that advice makes me realize we are now dealing with potential contributors with very different motivations. While before contributions came in because someone had an itch to scratch (a bug to fix, a feature to add, ...) there are now also people that come in looking for something to do, where a project is not necessarily a starting point. There is a different motivator, and these contributors are looking to apply their skillset in practice. If this is the case, I wonder if we can look at this more as a problem of supply and demand. That is, by doing inventory of what projects need (bug triaging, documentation, user support, ...), making it much easier for people to find an area where they can apply their particular skills. In other words a nice Community Insights project. I don't have the cycles to actually execute on such a project, but I thought it useful enough to share. Cheers, Sander
