Non-code contributions workflow

[twentysixmoons]

I've been wondering what has been holding me up from uploading slides, but I want to make sure I do "things right."

I noticed we have a code-contributing section for our contributor's guideline, but I want to check in to see if we want to do the same process for non-code contributions.

Reference:
https://github.com/arachne-threat-intel/community/blob/main/CONTRIBUTING.md#coding-standards

https://github.com/arachne-threat-intel/community/blob/main/CONTRIBUTING.md#code-contribution-workflow

[KadeMorton]

This is something I'd be keen to have your input on. We have the standards and workflow that you linked based on the fact that code is very structured and its easy to put processes around that. Non-code contributions are a lot more open and harder to define. We don't have any standards or workflows for this reason, but it doesn't mean we shouldn't. I'm fine with not having them as it leaves things open for the many and varied forms that non-code contributions can take, but I'm open to having a discussion around them.

If we want to have standards and workflows, I think we will need to start enumerating the different forms of contributions that people can make. Here are some off the top of my head but this is not an exhaustive list:

• Documentation: Standards for structure, clarity, tone, and formatting.
• Translations: Guidelines for supported languages, tools, and processes.
• Community Engagement: Standards for moderating discussions, triaging issues, and responding to queries.
• Marketing and Outreach: Contribution ideas for blog posts, social media content, and promotional materials.
• Design: Standards for logos, UX/UI elements, and other visuals.