When the Content + UX community started requiring salary disclosure in job postings shared to our #job-openings channel, we also automated the posting process. This gist captures the process we use, which can be adapted to any Slack community. It's easy to set up and requires almost no maintenance.
Only the free tier is needed for each of these:
Include a project description that explains what your project is and why it exists. Aim for no more than 3-5 concise sentences. For example, you might say:
{Project Name} is a project of {Your Brigade}. {Your Brigade} is a brigade of a Code for America that exists to {your mission}. {Project Name} helps {target users} accomplish {goal of project}. The {app/site/thing you're building}'s main features include {very brief feature descriptions}.
Civic projects often exist within a larger context that may include multiple stakeholders, historic relationships, associated research, or other details that are relevant but not required for direct contributions. Gathering these details in one place is useful, but the ReadMe isn't that place. Use this section to link to a Google Doc or other documentation repository where contributors can dig in if they so choose. This is also a good place to link to your Code of Conduct.
This version of the Code of Conduct is now out of date. Please see https://contentandux.org/code-of-conduct for the most up-to-date version.
Last updated: June 11, 2019
The Content + UX Slack Group is dedicated to providing a harassment-free experience for everyone. We do not tolerate harassment of participants in any form.
This code of conduct applies to every member of the Content + UX Slack Group. Anyone who violates this code of conduct may be sanctioned or expelled from the Content + UX Slack Group at the discretion of the ADMIN TEAM.